My neck just gave out a crack that sounded like a dry branch snapping in a winter forest, and for a second, I actually thought I’d paralyzed my left arm. It was a mistake, a sudden twist to look at a notification that shouldn’t have mattered, but that’s the state of things now. We are jittery. We are reactive. I sat there, rubbing the base of my skull, while Sarah’s message pulsed on the second monitor. She was blocked. A missing API key for the legacy billing gateway-a classic, 7-year-old hurdle that everyone knows exists but no one actually owns. She’d been waiting for 47 minutes, which in developer time is roughly equivalent to a small eternity spent staring at a wall.

I watched the three dots of Sarah’s typing bubble appear and disappear for a long time. She was likely deleting a series of very creative profanities. That moment, right there, is the terminal illness of modern corporate execution. We have replaced the ‘Problem Solver’ with the ‘Status Reporter.’ We have hired brilliant, expensive people to act as human middleware, translating the reality of technical friction into the fiction of a clean Gantt chart. It is a role that manages nothing but the plan itself, while the project-the actual, breathing, shivering collection of code and logic-is left to fend for itself in the dark.

“

The map is not the territory, but the PM is obsessed with the legend.

“

The Inspector Who Doesn’t Fix

I remember talking to Thomas K.-H., an assembly line optimizer who spent 27 years making sure steel moved through factories without ever touching the floor. Thomas is a man of precise habits; he wears 7 identical shirts to avoid decision fatigue and carries a notebook where he tracks ‘dwell time’ with the ferocity of a hunter. He once told me that the greatest failure of any system is the ‘inspector who doesn’t fix.’ In his world, if a part comes off the line crooked, and the inspector just marks it as ‘crooked’ on a clipboard and lets it pass to the next station, that inspector is actually part of the waste. They are adding cost without adding value.

In software, we’ve institutionalized the ‘inspector who doesn’t fix.’ We call them Project Managers, though the title has been stripped of its verb. To manage is to handle, to direct, to exert control over a situation to achieve an end. But in the 77 meetings I’ve attended this month, I’ve seen very little management and a whole lot of ‘alignment.’ Alignment is what you do to wheels on a car; it doesn’t mean the car is actually moving toward a destination. It just means everyone is pointed in the same direction while we sit in the driveway with an empty gas tank.

This isn’t entirely the PM’s fault. It’s a symptom of a low-trust environment. When leadership doesn’t trust the engineering team to own their outcomes, they install monitors. These monitors are tasked with providing ‘visibility.’ But visibility in a high-pressure environment is often just a polite word for surveillance. If I know that my boss is looking at a dashboard every 7 hours, I’m going to spend a disproportionate amount of my energy making that dashboard look green, even if the servers are literally on fire. The PM becomes the gardener of this digital topiary, clipping the hedges of our Jira boards until everything looks orderly from a distance, while the roots are rotting underneath.

The Absurdity of Tracking

“

Data as a character in a tragedy.

“

When you look at the numbers, the absurdity becomes even clearer. We have teams where the ratio of ‘doers’ to ‘trackers’ is approaching 1:1. Imagine a construction site where for every person swinging a hammer, there is another person standing behind them with a tablet, asking for a status update on the current nail. It sounds like a comedy sketch, yet it’s the standard operating procedure for $777 million enterprises. The trackers generate reports that nobody reads, which are then summarized into slide decks that nobody believes, to satisfy a thirst for certainty that doesn’t exist in a complex system.

This creates a specific kind of friction I call ‘The Update Loop.’ Sarah is blocked. She tells the PM. The PM tells her to update Jira. The PM then takes that Jira update and puts it into a weekly report. The weekly report is discussed in a meeting on Thursday. In that meeting, someone finally says, ‘Oh, we should probably talk to the billing team.’ By then, 7 days have passed. If the PM had simply picked up the phone-or better yet, if the team was structured so that Sarah could just talk to the billing team herself without a mediator-the problem would have been solved in 7 minutes.

Cutting the Middle Layer

Interestingly, some organizations have figured this out by accident or by brutal necessity. They move toward models where the overhead is stripped away, and the people doing the work are empowered to manage the execution themselves. In environments like ElmoSoft, the focus shifts from reporting on the status to actually achieving the result. They integrate deeply, meaning there isn’t a layer of ‘translators’ standing between the problem and the fix. When you reduce the distance between the question and the answer, the need for human middleware evaporates. You don’t need a status update if you are actually part of the process.

For examples of deep integration and results-focused delivery, see the work done at ElmoSoft’s Fintech Integration, where overhead is drastically minimized.

I’ve seen the alternative, and it smells like stale coffee and looks like a 27-column spreadsheet that won’t fit on a single screen. I remember a project where we had 7 different ‘Project Coordinators’ for a team of 14 developers. Each coordinator was responsible for a specific ‘workstream.’ The result was a bureaucratic nightmare where changing a button color required a cross-workstream alignment meeting. We spent more time talking about the work than actually doing it. Thomas K.-H. would have had a heart attack. He would have pointed at the conveyor belt and asked why there were 7 people standing around a single box, all of them holding clipboards and none of them moving the box.