Day 2: Automations - Why this is PM Territory
7-Day email course, workbook and ultimate guide
Yesterday we covered what an automated workflow actually is.
Trigger → Steps → Output.
Simple enough right?
Today, I want to talk about why you’re better positioned to lead this stuff than you probably think.
You already think in workflows.
Every time you map out a project, you’re designing a workflow. Every time you spot a bottleneck in an approval process, you’re diagnosing a workflow problem. Everytime you figure out how to get work from one team to another without things falling through the cracks, you’re solving a workflow challenge.
That’s 80% of automation thinking right there.
The other 20%? That’s the technical bit. And here’s the thing: you don’t need to do the technical bit yourself.
What clients and colleagues actually need from you
They don’t need you to code. They don’t need you to configure platforms. They don’t even need you to understand how APIs work (although knowing the basics will help).
They need you to:
Identify which processes are worth automating
Define what the workflow should do (clearly enough that someone can build it)
Manage the project from idea to implementation
Make sure what gets delivered actually solves the problem
That’s rock-solid PM work right there.
And the PM’s secret weapon?
You know where the pain is.
You’re the one chasing approvals. You’re the one copying data between spreadsheets. You’re the one sending the same status update every Friday. You’re the one who knows which tasks eat uptime without adding much value.
Developers don’t know this. Neither do most senior leaders. They see the outputs, not the messy middle.
You LIVE in the messy middle, and that makes you the best person to spot what should be automated.
Building vs managing automation projects
There’s a difference between building an automation and managing an automation project.
Building requires technical skills. Configuring platforms, connecting systems, writing logic.
Managing requires PM skills. Scoping, planning, communicating, testing, delivering.
Some people do both. But plenty of successful automation projects have a PM who doesn’t touch the build at all. They define what’s needed, work with someone technical to build it, and make sure it actually works.
The mindset shift
Stop thinking, “I’m not technical enough for this.”
Start thinking, “I understand processes better than almost anyone in this agency.”
That’s your edge. Use it.
Tomorrow, we’ll break down the anatomy of a workflow. Once you see the structure, you’ll start spotting workflows everywhere.
Speak then,
Tim
Your course workbook
I’ve built a guide (in Notion) to go alongside these emails.
Inside you’ll find:
- Daily AI prompts to reinforce each lesson.
- Exercises to spot opportunities in your own work.
- Space to capture automation ideas as they come to you.
Complete the exercises, and you’ll be ready for the full guide on Day 7.
Sign up for Notion (it’s free and it’s awesome).
Go and grab your course workbook if you haven’t already.