The case for automating the admin that's eating your evenings
Let me paint a picture you might recognise.
It's Thursday evening. You're still at your desk, or you're at home with your laptop open, writing the weekly update that needs to go out tomorrow morning. You're pulling together notes from three different meetings, trying to remember what that blocker was from Tuesday, reformatting the same information you've reformatted seventeen times in slightly different ways for slightly different audiences.
And somewhere in the back of your head, there's a thought that doesn't quite form into words: this is not what I thought management would look like.
The admin tax on managers
There's a kind of creeping administrative weight that settles on managers that nobody really prepares you for. You get promoted because you were excellent at the actual work. Then the role expands to include: writing the meeting notes, distributing the meeting notes, writing the status update, having a slightly different version of that update for your manager, running the Monday sync, summarising the Monday sync, responding to the emails that arrived during the Monday sync, and somewhere in there, doing the work you were actually promoted to do.
Research on manager time consistently finds that somewhere between a third and half of working hours go to administrative tasks. Not strategic thinking, not team development, not the actual decisions that need a senior person's brain. Admin.
This is a systems problem. And systems problems have systems solutions.
What automation actually means here
When people hear "automation," they often picture something technical and complicated, like something that requires a developer or an IT ticket or learning a programming language. That's not what I'm talking about.
What I'm talking about is connecting two apps together so that information flows between them without you in the middle. Your meeting gets transcribed automatically, the transcript goes through an AI that summarises it into decisions and action items, and the result lands in your team's Slack channel. You didn't write a single word of those notes. You just had the meeting.
Or your project management tool syncs with a weekly report generator on a schedule. Every Friday at 3pm, the status update drafts itself from the live task data, you spend five minutes reviewing it, and it goes out. Not because you cleared your Friday afternoon for it, but because the system handled it while you were doing something that actually needed your attention.
What you still need to do
Automation isn't about removing humans from the loop. It's about removing humans from the parts of the loop where human judgment isn't actually needed. You still need to decide the strategy. You still need to have the hard conversations. You still need to build the relationships and make the calls that require experience and nuance.
What you don't need to do is manually transcribe what was said in your standup. That's not a judgment call. That's just transcription.
A realistic starting point
If you've never built an automation before, start with one. Pick the most repetitive, lowest-stakes documentation task in your week, and build a simple workflow around it. See if it holds for a month. If it does, add another.
The The 4-Hour Workday walks through three complete automations with step-by-step instructions: meeting notes, weekly status reports, and email triage. All built using Zapier and ChatGPT. No coding, no technical background required. Just a few hours to set it up, and then a lot of hours back every week after that.
Because the meetings aren't going away. But the notes don't have to be your problem anymore.