Fordel StudiosThe standup was designed for a self-organising team that needed to coordinate work across the day. Fifteen minutes. Three questions: what did I do, what am I doing, what is in my way. The team speaks to each other. Blockers get unblocked. Coordination happens. Everyone moves faster.
What most companies actually run: an engineer speaks for two minutes while their manager types notes. The manager's boss is also on the call. Nobody admits they are behind schedule. Nobody surfaces the real blocker because the real blocker involves a political conversation about priorities that cannot happen in this forum. Everyone says "no blockers" and returns to being blocked.
The Surveillance Signal
Watch who the engineers look at when they speak in a standup. In a functional self-organising team, they look at each other. They are coordinating. In a dysfunctional standup, they look at the manager. They are reporting. The body language tells you everything about what the meeting has become. It was designed to replace the daily project status email. In many teams, it became the daily project status email with a camera on.
The engineer who is genuinely blocked says "no blockers" because saying "I am blocked waiting for a decision from product" in front of eight people and a manager leads to a conversation that is worse than the block. The meeting design punishes honesty. The team learns to perform progress rather than report it.
“Any meeting where the honest answer would be career-limiting has already failed as a communication mechanism.”
What Actually Works Instead
Async status updates in a shared channel, written when the engineer has something to say, not when the clock says 9:30am. A weekly synchronous team meeting where actual coordination happens — priorities, blockers, architectural decisions. Direct access to anyone who can remove a blocker, without requiring a public forum to surface it.
This requires trust in both directions. Managers need to trust that engineers are working without watching them check in daily. Engineers need to trust that surfacing a blocker directly will not be used as performance evidence against them. If neither of those conditions exists, the standup is not the problem. The culture is. The standup is just the symptom you optimise for instead of fixing the underlying disease.
The Permission You Already Have
If you are an engineering manager: cancel the standup for two weeks. Replace it with a shared async channel where engineers post updates when they have something material to share. Measure what changes. I predict blockers surface faster, not slower, because engineers can write them without an audience.
If you are an engineer: the next time someone asks what your blockers are in front of six people and a manager, tell them the actual blocker. The meeting cannot improve until it gets honest signal. You are the signal.
