“Done, testing, blocked on legal review.” Our Project Manager, Ken, didn’t look up from his spreadsheet. He was typing the output of human effort into a grid designed to manage concrete pours, not software development.

The air conditioning unit was humming too loudly, competing with the forced optimism in the conference room. Maria just finished reciting her three bullet points. His mechanical tapping was the soundtrack to our collective self-deception. Why are we paying four highly-skilled people $234 an hour to read their Outlook calendar to a guy who just wants to update a Gantt chart?

This isn’t a stand-up. It’s an enforced, daily status report cycle, miniaturized and given a cool, contemporary name. We call it Agile because we use Jira and limit ourselves to two-week increments, but the actual decision-making flow still starts at the top and trickles down, rigid and pre-approved. We’ve adopted the vestments and the chanting, but rejected the soul of true agility: empowerment and rapid adaptation.

It gives executives the comfort of checking a box-“Yes, we do Agile now!”-while eliminating the only inherent benefit of agility: the ability to change direction mid-flight based on new information. When the ritual becomes the goal, results become secondary.

We see this fixation on process perfection everywhere, even in simpler consumer choices. People spend hours researching the most complex gadget or setting up intricate, customized routines when often, the most straightforward, reliable tool is what delivers the actual satisfaction and results. Sometimes you just need clarity and function, not complicated ceremony, whether that involves streamlining your team’s workflow or choosing something simple and effective like checking out the latest selections at พอตใช้แล้วทิ้ง.

Ken, the PM, measures success by a single, terrifying metric: Did we hit the four-point story commitment we arbitrarily set last Monday? It’s not about validated customer value delivered, or learning something new about the market. It’s about velocity, but it’s Velocity Theater. He needs to prove absolute control to his VP, and the VP needs to prove control to the board. The illusion costs us dearly.

The Paralysis of Perfection

We spend 44 minutes debating the definition of “done” for a minor feature when the user just needs the button to work. I remember one planning session-it stretched to six hours, paralyzing everyone. The goal was risk mitigation, but the actual risk was exhaustion leading to terrible decisions made at minute 304. We created a perfectly articulated, immutable plan for a world that changes every Tuesday. And then we broke that plan into tiny two-week chunks, believing the small size made it resilient. It didn’t. It just made the misery manageable.

This issue isn’t restricted to software development. Take Charlie J.-M. He’s a sunscreen formulator, specializing in broad-spectrum physical blocks.

Charlie J.-M. and the Metallic Scent of Failure

They bought a shiny new project management suite and started holding daily stand-ups. Now, Charlie has daily 15-minute stand-ups where he reports the chemical stability testing status to a Lab Coordinator who has never touched a centrifuge. Charlie’s expertise-the nuanced, intuitive sense of when a binder is failing-was replaced by a Jira ticket detailing the temperature curve data point 4.

He knows, instinctively, that the emulsifier sourced from the new supplier smells faintly metallic, which signals a stability issue eight months down the line. But that’s “unquantifiable data” and therefore not a valid blocker in the sprint backlog.

He has to follow the plan. When the product eventually fails stability testing six months late, who takes the takes the hit? Charlie. The team was given the responsibility for delivery (the Agile promise) but had the authority centralized (the Waterfall reality). This is the fatal contradiction that kills morale and quality simultaneously. We criticize the results, but never the structure that generated them.

I realize this frustration is echoing in my own house right now. Last night, I was on a work call-the kind that extends past the scheduled end time because four senior leaders were trying to meticulously define what “MVP” meant for the 44th time-and I forgot I had placed dinner in the oven. Smoke alarms, a ruined roast, a kitchen smelling like burnt ambition.

The Pendulum Swing: From Control to Chaos

The plan was fine (oven at 400 degrees for 40 minutes). The execution failed because my attention, my *autonomy* over my own schedule, was usurped by enforced ceremonial planning. I was distracted, forced to focus on an irrelevant process instead of the real, burning matter.

I have to admit, early in my career, I was Ken. I loved the look of a perfectly green burndown chart. I measured my success by the predictability of the output, not the utility. I failed to challenge the VP who insisted on dictating the architecture before the teams had even defined the user problem. I justified it by saying, “Well, at least we’re doing retrospectives.” But what good is a retrospective where the primary takeaway is: “We need better estimates next time,” when the real problem is: “The person doing the estimating has zero power to change the mandate.”

We are demanding teams tell the truth while actively punishing them for doing so.

The Heart of Agility: Decentralized Power

We must understand this fundamental truth: If the Product Owner (or Project Manager, or Lab Coordinator) functions as a purely administrative status aggregator, you are running Waterfall. If the team is unable to discard 80% of the planned work halfway through the sprint because external stakeholders hold the budget hostage to the original scope document, you are running Waterfall. If the daily meeting is mandatory recitation to a boss, rather than a self-organized sync about dependencies and impediments, you are running Waterfall.

It’s the same old heavy structure, just painted bright new colors and delivered in smaller, faster pieces. The real agility-the soul we rejected-is decentralized power. It’s the uncomfortable vulnerability of trusting the person closest to the problem (Charlie J.-M., the developer, the tester) to make the decision right now, even if it deviates from the four-page documentation signed last quarter.

The Crucial Question

Until organizations prioritize competence and autonomy over compliance and control, we will simply continue building elaborate shrines to efficiency, sacrificing real work on the altar of the perfectly formatted status update. And that, frankly, is a hell of a way to spend $474 million dollars.