Take a hard look at your calendar for the last sprint. Count the hours you spent on actual coaching: conversations that shifted how someone thinks, one-on-ones that unlocked a decision, retrospectives where real problems got surfaced. Now count everything else. Metrics spreadsheets. Status compilations. Scheduling retros. Tracking action items. Chasing down velocity numbers. Writing up sprint summaries. You know what you'll find? You spent more time on admin than coaching.
The numbers are worse than you think
Deloitte research on knowledge worker productivity shows that developers spend only 30-40% of their time on actual feature development. The rest goes to meetings, communication, context switching, and process. The pattern is even more extreme for coaches. We're running ceremonies (not coaching), compiling metrics (not coaching), tracking actions (not coaching), and managing calendars (definitely not coaching). By the time we sit down for a real conversation, we're exhausted.
"Developers spend only 30-40% time on feature development. Coaches spend 30-40% on actual coaching. The gap is process, not incompetence."Deloitte · Knowledge Worker Productivity Study
Worse, the admin work doesn't scale. Add a second team and your admin doubles. Add a third and you're barely coaching anymore. You're managing a portfolio of spreadsheets.
Why we accept the admin tax
Coaches accept the admin work because it feels necessary. Someone has to run the retrospective. Someone has to track the metrics. Someone has to write the status update. These things are real. They matter. So we do them. And then we tell ourselves that the time we have left is coaching.
But here's the trap: the admin work is always visible, always urgent, always something you can point to. "Look, I ran five retrospectives this week." The actual coaching — the thinking partnership, the difficult conversation, the moment someone changes their mind — that's invisible. It doesn't show up on a timesheet. So we prioritize the visible and squeeze the valuable into the gaps.
The automation opportunity
The good news is that most admin work is automatable. Not hard. Not expensive. Just systematically automatable. Metrics collection can be automated. Action item tracking can be automated. Sprint summaries can be synthesized automatically. Sprint scheduling can be done asynchronously. Retrospective note-taking can be standardized. None of this requires human attention.
When you automate the admin, something strange happens. Your calendar opens up. You have four hours a week back. Then eight. Then maybe 15-20. And you can finally do the thing you became a coach to do: help people think better.
The immediate reclaim
Start this week. Pick one admin task that consumes 3-4 hours a week. Just one. Metrics spreadsheet? Automate it or delegate it. Status compilation? Template it and make it async. Sprint scheduling? Move to calendar links. Action tracking? Get a tool that does it automatically from retro notes. Don't do all of them. Do one. Get those hours back. Then do another next week.
The goal isn't to eliminate admin entirely. It's to bring it down from 60% of your week to maybe 15-20%. That leaves you with real time to coach. Real time to think with your teams. Real time to notice the things that matter.
The courage to say no
Here's the hard part: you'll need to stop doing some things. Maybe your sprint summaries won't be as polished. Maybe metrics will come from a dashboard instead of a manually constructed narrative. Maybe the retrospective will be shorter or async. That's okay. Those things weren't serving coaching. They were serving the appearance of process. And you don't need that anymore.
Your teams didn't hire you to run perfect ceremonies. They hired you to help them get better. Everything you do that doesn't serve that goal is wasting the time you could spend on it.