There’s a particular kind of meeting that happens in every large organisation, usually on a Tuesday, usually at 9am, and it has a name nobody uses out loud: the theatre of control. A project manager stands at a dashboard. The dashboard is green. Nobody in the room believes it’s green. The project manager knows it isn’t green. Everyone nods anyway, because the alternative is a conversation nobody scheduled time for.
This is what the job became. It is not what the job was for.
Go back far enough and the project manager was something closer to a fixer. Not glamorous, not certified, not templated. Someone who could walk into a room full of people who disagreed with each other and leave with a decision made. The value wasn’t in the paperwork. It was in the nerve to make the call and the relationships to make it stick. Nobody hired that person to build a Gantt chart. They hired them because the project was stuck and somebody needed to get it moving again.
Somewhere in the last two decades, the industry made a trade it never openly admitted to. Reporting is safe. A status report can be wrong for months and nobody gets fired for it, because everyone in the room signed off on the same wrong colour. Solving the actual problem is risky. It means telling a sponsor their timeline was always fiction, or telling a steering committee that the plan they approved will not survive contact with reality. So the profession, gradually and without much resistance, promoted the safe work over the risky work. We didn’t lose the fixer. We retired him quietly and replaced him with someone who is very good at PowerPoint.
I don’t say this as an outsider looking in with disapproval. I’ve built the deck. I’ve sat in the room where a green status protected everyone from the conversation the project actually needed to have that week. It works, in the narrow sense that nobody gets blamed for it. It has never once, in my experience, made a project land.
Here’s the part that’s harder to admit. Most of the admin didn’t get imposed on project managers from above. A lot of us reached for it ourselves. Status reports are controllable. You sit down, you fill the fields, you send the email, and by five o’clock you have something finished. Problems are not controllable in that way. Given the choice between a task you can complete by the end of the day and a conversation that might go badly and won’t resolve in one sitting, most people, on most days, will take the task. That isn’t a character flaw in individuals. It’s what happens when an entire profession quietly agrees, over years, that looking organised is an acceptable substitute for being effective.
The data backs up what most of us already suspected about how our weeks actually go. Asana’s global work index put the average knowledge worker’s time at something like sixty percent spent on “work about work,” coordination, status updates, chasing information, and only a sliver left over for the strategic thinking they were actually hired to do. Project-specific research tells the same story from a different angle: nearly half the organisations surveyed by Wellingtone in their most recent report don’t have access to real-time project data, and a large share of project managers spend a full day or more each week just collating reports by hand. That’s not a rounding error. That’s a working week with one day permanently reserved for describing the work instead of doing it.
None of this happened because anyone sat down and designed a bad system on purpose. It happened because reporting scales in a way that judgment doesn’t. You can mandate a weekly status template across an entire portfolio. You cannot mandate good judgement, and organisations that get nervous about variability tend to reach for the thing they can standardise, even when the thing they can standardise isn’t the thing that actually delivers outcomes. Governance grew because it was legible. Problem-solving stayed illegible, personal, and hard to defend in an audit, so it got squeezed to the margins of the job description without anyone deciding that on purpose.
The job is overdue for a correction, and for once it isn’t going to arrive via a new methodology or a two-day certification course. It’s arriving because software can now write the status report, chase the update, and build the dashboard faster and more accurately than any of us ever could by hand. Tools that generate a status summary from raw project data in seconds, that sit in a meeting and produce the minutes and the action items before anyone’s finished their coffee, that build a live dashboard nobody has to manually update again. The tedious half of the job, the half that ate the calendar and left problem-solving for whatever hours were left, is being automated out from under us. Which leaves a genuinely uncomfortable question sitting in the space where the admin used to live: if the reporting is no longer yours to do, what exactly are you being paid for?
The honest answer is the same one the job started with, before it got buried under templates. Getting the right people in a room. Making the call nobody else wants to make. Being the person whose judgement is worth more than the meeting’s momentum, worth more than the safety of a green status nobody believes. That was always the job. We just spent twenty years getting very good at avoiding it, and calling the avoidance professionalism.
I don’t think the tools are going to hand that back to us as a gift. I think they’re going to strip away the excuse we’ve been hiding behind for two decades, and what’s left after that is entirely up to us.
Leave a Reply