Your manager’s face freezes for a half-second, then catches up. The red border around their video feed seems to glow just a little brighter. It’s your turn. You do the dance. Yesterday, I finished the API endpoint refactor, updated the documentation, and reviewed Priya’s pull request. Today, I’m starting on ticket JIRA-789.
Silence. Not the good kind. It’s the silence of nine other people on the call trying to look busy while a two-person conversation is forced upon them. “Okay,” the manager says, drawing the word out. “But what’s the status of the ticket for the analytics dashboard? The one I mentioned last week?”
“This isn’t a stand-up. It’s a status report with a misleading brand name.”
It’s the performance of agility, a ceremony stripped of its soul and repurposed for the comfort of middle management. We adopted the vocabulary-sprints, stand-ups, retros-but we fundamentally rejected the core principles of trust and autonomy that make any of it work.
From Servant Leader to Primary Blocker
I used to be the worst offender. For a period of about two years, I led a team where our stand-ups were a masterclass in this dysfunction.
“I saw myself as a servant leader, but my actions screamed insecure micromanager.”
I’d go down the list, one by one, asking for percentage complete, for ETAs, for justifications on why something took 19 hours instead of the estimated 9. I thought I was keeping the project on track. In reality, I was the primary blocker. I had created a culture of fear where nobody dared to admit they were stuck until it was a raging inferno. We ran 49 sprints like that, and every single one felt like pushing a boulder uphill through sand.
The Urge for Certainty vs. The Thrill of Overcoming
I’m a hypocrite, of course. I’ll sit here and criticize the command-and-control manager, but I still check our team’s Jira board every morning before the call. I count the tickets that moved from ‘In Progress’ to ‘In Review.’ I can’t help it.
“The urge for certainty is a powerful drug, and trust feels like a gamble.”
This whole mess reminds me of my friend, Leo T.-M. He’s an escape room designer. Think about his job for a second. He literally creates blockers for a living. His entire profession is centered around crafting intricate problems designed to halt progress. But his goal is the exact opposite of what happens in our broken stand-ups.
He doesn’t want people to fail; he wants them to have the thrill of overcoming a challenge *together*. He watches teams on his monitors, but he doesn’t interrupt them to ask for a status report on the cryptex puzzle. He waits for them to get truly stuck, to hit a wall, and then he slides a cryptic clue under the door.
“His job isn’t to demand status; it’s to provide the precise piece of information needed to get a team moving again.”
That’s all a stand-up is supposed to be.
It’s a team looking at the puzzle together and someone saying, “I’m stuck on the laser grid,” so someone else can say, “Oh, I found a prism in the other room that might help.”
The Festering Problem: From Toothache to Root Canal
When we ignore small blockers, they don’t go away. They fester. A minor database lock issue that a developer is too intimidated to mention becomes a full-blown outage 39 hours later. An ambiguous requirement that could be clarified in a 9-second conversation turns into two weeks of wasted work. It’s the technical equivalent of ignoring a faint toothache.
You know something is wrong, you know you should get it checked, but the perceived friction of dealing with it feels greater than the immediate pain. So you let it go, until one night you’re awake at 3 AM with a throbbing jaw, frantically searching for emergency help. Any good family dentist will tell you that the cost and pain of prevention are microscopic compared to the cost of a crisis cure. Our stand-ups are supposed to be that preventative check-up, the moment we find the tiny cavity before it requires a root canal.
Performance of Competence
Instead, we’ve created a ceremony that encourages hiding the cavities.
“The meeting becomes a performance of competence. Everyone’s incentive is to signal that they are busy and productive, not that they are blocked and in need of help.”
Admitting a blocker feels like admitting failure, especially when your manager is treating the meeting as a daily audit of your timesheet. The very format designed to foster collaborative problem-solving has been twisted into a tool that punishes the vulnerability required to solve problems.
The Real Problem: Trust
We obsess over the format. Should we use a physical board? Should we pass a token? Should we go in order of who joined the call? It’s all rearranging deck chairs on the Titanic. The problem has never been the format. The problem is trust.
The Problem is Trust.
Do you, as a manager, trust your team to work on the most important thing without you personally inspecting their progress every 24 hours? Do you, as a team member, trust your colleagues and your lead enough to say, “I don’t know how to solve this” or “I made a mistake and need help”?
If the answer is no, then it doesn’t matter what you call the meeting. It’s not Agile. It’s not a stand-up. It’s an anxiety-fueled ritual that generates reports no one reads and solves problems that don’t exist, while the real problems-the real blockers-hide in plain sight, growing larger by the day, waiting for the inevitable 3 AM emergency.