Why We Killed Our Daily Stand-ups (And What We Did Instead)
Productivity4 min read
On this page
We did not kill stand-ups because we hated meetings.
We killed them because we finally admitted what they had become.
Every morning, nine people joined a call. Someone shared their screen. Each person spent two to three minutes describing what they had done yesterday and what they were doing today. The call lasted twenty-five minutes. People nodded. People said sounds good. The call ended and everyone went back to exactly what they had planned to do before it started.
Twenty-five minutes. Every day. Nine people. That is nearly four hours of collective time, daily, producing almost no decisions, no new information, and no change in direction. What it produced was the feeling of alignment without any of the substance of it.
The day we admitted that to ourselves was the day the standup was already over.
What Stand-ups Are Supposed to Do
The original purpose of a daily standup is legitimate. You want the team to be aligned. You want blockers surfaced quickly. You want people to know what their colleagues are working on so work does not get duplicated or fall through gaps.
None of that is wrong. The question is whether a daily synchronous meeting is the best way to achieve it.
For a co-located team shipping fast in a single timezone, it might be. For a distributed team where half the value of the meeting is social and the rest is information that could live in a written update, the cost-benefit calculation looks different.
Our team had not asked that question honestly in years. We ran stand-ups because stand-ups were what teams did. It was inherited practice, not deliberate design.
What We Built Instead
The replacement had three parts.
Async check-ins three times a week replaced the daily call. Each person posted a short written update, what moved forward, what is blocked, what needs attention from someone else, in a shared channel. The updates took five minutes to write and three minutes to read. The information content was higher than the meeting had ever been because writing forces a clarity that speaking often avoids.
A single mid-week sync replaced the daily real-time touch-point. Thirty minutes, Wednesdays, reserved exclusively for blockers and decisions that genuinely required conversation. If something did not require a decision or could not be resolved in thirty minutes, it did not belong on the agenda. The meeting became useful because it became rare.
A standing document replaced the verbal status update. Any decision made, any direction changed, any question resolved got a one-paragraph summary with a named owner and a clear next action. The document became the team’s memory, accessible to anyone, searchable, honest about what had actually been decided rather than what people remembered being said.
The Resistance Was Real
Not everyone on the team wanted to change.
Some people genuinely liked the standup. Not for the information, but for the daily rhythm of seeing each other, even through a screen. That was a real thing worth acknowledging. We were not removing the meeting because connection did not matter. We were removing it because it had become the wrong container for connection.
We replaced the social function with something more intentional. A casual channel where off-topic conversation was actively encouraged. A monthly optional call with no agenda, just time together. The social need did not go away. We just stopped trying to meet it in a format optimized for status updates.
What the Numbers Said
Over the following quarter, we tracked meeting hours, decision latency, and team satisfaction.
Meeting hours dropped by sixty percent. The decisions that had previously emerged slowly from daily calls, because people needed a night to think before they responded, started happening faster because the async format gave people time to think before they spoke rather than having to think and speak simultaneously. Team satisfaction with communication went up, which surprised people who assumed that fewer meetings would mean feeling more disconnected.
The thing about synchronous communication is that more of it does not automatically mean better connection. Better connection comes from the right kind of communication at the right frequency. We had more of both by doing less of the wrong thing.
The Question Worth Asking Your Team
Not every team should kill their stand-ups. Some teams run them well and get genuine value from them. The format is not the problem. Inherited habit is the problem.
The question worth asking is not should we have stand-ups? It is what do we actually need from daily communication, and is what we are doing now the best way to get it?
If you answer that honestly, you will know what to do.
SaneHQ keeps your team aligned without the meeting overhead. Start today
Continue reading
The Hidden Cost of Context Switching (And How to Minimize It)
We did not remove urgency. Urgent things still got handled urgently. We did not make the team less responsive. We made the team more deliberately responsive, which turned out to be more useful than reflexively responsive had ever been.
The Art of Saying No: How We Shipped 40% Faster
We made our roadmap visible to everyone inside and outside the company. Not just what we were building but why, what outcome each initiative was aimed at, what evidence supported the decision, and what would change our minds. That transparency did something unexpected: it reduced the pressure to say yes to things. When people could see our reasoning, they stopped lobbying as hard. They understood the constraints. Sometimes they even helped us refine the criteria.
From Burnout to Balance: Our Engineering Team’s Transformation
What our team had been living through was not a crisis. It was a slow erosion. We had been making the same reasonable compromises for long enough that the foundation had quietly worn thin, and nobody had noticed because everyone was too busy making the next reasonable compromise to look at the whole picture.