The Squeak of the Marker

The dry-erase marker squeaks in a way that sets my teeth on edge. It is a sharp, 72-decibel screech that cuts through the polite, forced murmurs of the 12th-floor conference room. I am standing there, my lower back beginning to ache with that familiar dull throb that comes from 22 minutes of motionless standing on industrial carpeting. We are currently engaged in what the corporate handbook calls a ‘Daily Scrum,’ but what anyone with a shred of honesty would call a police lineup.

Dave is our Scrum Master. In a previous life, or perhaps just 12 months ago, Dave was a Senior Project Manager who lived and died by Gantt charts and the sound of his own voice. Now, he wears a branded hoodie and uses words like ‘blockers’ and ‘impediments,’ but the soul of the micro-manager remains untouched by his wardrobe change.

Taylorism with Better Graphic Design

I recently sat in a boardroom and tried to explain to a group of executives that ‘velocity’ is not ‘speed.’ I told them, with a level of patience I didn’t know I possessed, that velocity is a measure of consistency-a way for the team to gauge their own capacity for future planning. I had the data. I had the case studies from 62 different successful implementations where teams were allowed to self-organize. They ignored me.

The VP of Product looked at me as if I were suggesting we pay the developers in magic beans and asked how we could ‘leverage’ the sprint metrics to ensure 102% utilization of resources. I lost that argument. I felt the heat rise in my neck, the familiar sting of being right in a room full of people who are invested in being wrong. I stopped talking. I just sat there and watched the dust motes dance in the 22-degree light of the projector, realizing that we weren’t doing Agile. We were doing Taylorism with better graphic design.

[The hoodie is just a costume for the ghost of Frederick Taylor.]

The Integrity of the Bead

I think about Yuki S.K. often when I’m in these meetings. She was a precision welder I worked with back in 2012 at a heavy machinery plant. Yuki didn’t care about ‘sprints’ or ‘story points.’ She cared about the integrity of the bead. She would spend 102 minutes prepping a surface that most people would have finished in 22. If you tried to force Yuki into a two-week cycle where her progress was measured by the number of inches she welded per hour, she’d look at you with a level of pity that could melt the very steel she was working on.

Software is the same, yet we treat it like we’re flipping 22 burgers a minute.

The Fear of Being Unknown

This obsession with the ‘rituals’ of Agile-the standups, the retrospectives, the planning poker-is a defensive mechanism. Organizations instinctively resist change by molding new methodologies into old, hierarchical power structures. We crave the branding of innovation because it looks good on a 42-page slide deck for the investors, but we are terrified of the vulnerability that actual trust requires.

To truly implement an Agile framework, a manager has to accept that they don’t know exactly what every person is doing every 12 minutes of the day. They have to trust that if Sarah says the API is broken, she isn’t ‘slacking,’ but is actually solving a problem that could save the company $272,000 in technical debt down the line. But trust is a rare commodity in a building where 82% of the middle management layer is worried about their own relevance.

The Altar of Performative Busyness

We’ve turned the Daily Standup into a surveillance tool. Instead of ‘How can we help each other move faster?’, the underlying question is ‘What have you done for me in the last 22 hours?’ It creates a culture of performative busyness. People start picking smaller, easier tickets just so they can show ‘movement’ on the board. They avoid the deep, difficult architectural problems because those problems don’t fit into a 2-point story that can be closed by Friday.

“

I’ve seen developers spend 42 minutes wording their ‘update’ for the standup just to make sure they sound sufficiently productive. That is 42 minutes of cognitive energy wasted on the altar of Dave’s spreadsheet.

I remember a specific Tuesday, exactly 12 weeks ago, when I tried to suggest we skip the standup for a week and just use a shared Slack channel for blockers. The silence was deafening. You would have thought I’d suggested we set fire to the breakroom. The managers couldn’t conceive of a world where the work itself was the evidence of the effort. They needed the performance.

Results Over Reports

This reveals a deeper pathology in our corporate structures. We are addicted to the illusion of control. We want to believe that if we just have enough Jira tickets and enough story points, we can predict the future with 102% accuracy. But software development-and any creative endeavor, really-is inherently unpredictable. It’s a series of discoveries, not a series of tasks.

True systems of change aren’t about rituals; they are about the uncomfortable work of rebuilding accountability from a place of mutual respect. It’s about a methodology that focuses on the individual’s growth and the actual results, rather than the metrics used to track them. I’ve seen this work in other sectors where the stakes are physical and personal. For instance, the approach at

Built Phoenix Strong

isn’t about the ritual of the workout; it’s a true system focused on genuine accountability and trust in the process of transformation. It’s about the result, not the theater of the effort. In the corporate world, we’ve lost sight of that. We’ve traded the result for the theater.

I’ve spent 152 hours this year alone in meetings discussing why we aren’t meeting our ‘commitments.’ Not once in those 152 hours did we talk about whether the features we were building were actually helping the customers. We only talked about the velocity. We only talked about the burndown chart. It’s a form of corporate gaslighting where the map is treated as more important than the territory.

The Standup Test

If you want to know if your Agile transformation is a sham, look at your standups. Are people talking to each other, or are they talking to the person with the highest salary in the room? Are they discussing how to solve a complex problem, or are they defending their ‘status’? If it’s the latter, you’re not doing Agile. You’re just doing micromanagement with a different vocabulary. You’re paying for the ‘hoodie’ branding while maintaining a 19th-century power dynamic that stifles innovation and breeds resentment.

Yuki S.K. would have quit this job in 12 minutes. She wouldn’t have argued. She would have just packed her tools, adjusted her mask, and walked out the door toward a place where the quality of the weld mattered more than the color of the Post-it note. There is a lesson there for all of us, standing in our circles, waiting for Dave to finish his notes. The question isn’t how we can make the standup better. The question is why we are still standing there in the first place, pretending that surveillance is the same thing as support.