Latest / Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations / How One CTO Replaced Standups With a Status Board
Transcript
- Lucas: So, the daily standup. Almost every engineering team does them — but a lot of teams secretly hate them, and the data actually backs that up. Luna: I've definitely been on teams where the standup felt like a performance review of your yesterday, not a way to actually unblock today. Lucas: Right. And there's this growing movement — not just in tech, but especially in engineering — to replace that synchronous ritual with something asynchronous. A status board. Luna: Like a shared document? Or a Trello board? What does that actually look like? Lucas: Yeah, good question. So the specific case I want to look at today is a CTO at a 40-person SaaS company — I'll call him Dan — who decided to kill the daily standup cold turkey. No hybrid, no twice a week compromise. Just gone. Luna: Wow. That's bold. What drove that decision? Lucas: He tracked it. He measured that the average standup was scheduled for 15 minutes but actually took 45 when you accounted for people trickling in, side conversations, and the post-standup hallway debriefs. And that was just the direct time. The real cost was context switching — people losing flow before and after. Luna: Forty-five minutes of meeting for a team of 40 — that's thirty person-hours per week just on standups. Lucas: Exactly. And that's not even counting the cognitive load. So Dan implemented what he called a 'status board' — a single shared document, updated asynchronously by each engineer before 10 a.m. Luna: So what went on this board? Just the classic three questions? Lucas: Close, but with a twist. Each person wrote: what they worked on yesterday, what they're working on today, and — crucially — what's blocking them. But they also had to include an 'ask' — a specific thing they needed from someone else. Not just 'I'm blocked on the API' but 'I need Sarah to review my pull request by end of day.' Luna: That makes it actionable. Otherwise it's just status as theatre. Lucas: Right. And the board was not a free-for-all. Dan set a few rules: each entry was max three bullet points. No rambling. And there was a 'blockers' section at the top that got highlighted in red. Anyone could add to it, but the expectation was that the team lead would triage blockers within two hours. Luna: So the lead role shifts from meeting facilitator to blocker-removal coordinator. That's a big change. Lucas: It is. And Dan said the first two weeks were rocky. Some people missed the social ritual — the 'how was your weekend' chat. Other people just forgot to update the board. They had to set up a Slack reminder and a culture of, 'Hey, did you update the board?' Luna: What about the juniors? I've heard that standups can be a safe space for junior engineers to ask for help out loud. Lucas: That's a really good point. And counterintuitively, Dan found that juniors actually became more vocal on the board. In verbal standups, they tended to say 'everything's fine' even when it wasn't, because they didn't want to hold up the meeting. On the board, they could write a detailed blocker without feeling the social pressure of 39 people staring at them. Luna: So it lowered the barrier to surfacing problems. That's huge. Lucas: Yeah. And the numbers backed it up. After the first month, Dan measured that the team saved about 90 minutes per person per week — that's 60 person-hours saved across the team. And incident response time actually improved by 15 percent, because blockers were getting surfaced and resolved faster than in the old system. Luna: Wait — incident response improved? That's not what you'd expect from removing a daily sync. You'd think less communication would slow things down. Lucas: That's the counterintuitive part. Dan's theory is that the old standups created a kind of 'false sync' — everyone felt informed, but nobody was actually acting on the information until after the meeting. With the board, blockers got flagged and addressed immediately, often within an hour, instead of waiting until the next morning. Luna: So it's not less communication — it's faster, more targeted communication. Lucas: Exactly. And the async format also meant that people who worked in different time zones — Dan's team had folks in East Coast and West Coast — could participate without waking up at 7 a.m. for a standup. Luna: What about the teams that tried this and abandoned it? Because I've heard stories where the board just becomes a ghost town. Lucas: Yeah, Dan was honest about that. He said about 20 percent of the teams in his company eventually went back to some form of synchronous standup. Usually because the board wasn't being enforced — the team lead stopped checking it, so people stopped updating it. Or the team was so tightly coupled that they really needed a daily huddle to coordinate handoffs. Luna: So it's not a silver bullet. It works best for teams with relatively independent workstreams and a culture of written communication. Lucas: Right. Dan's advice was: don't force it on every team. Let individual teams decide. But for the ones that did adopt it, the satisfaction scores went up significantly. People reported feeling less stressed and more in control of their time. Luna: And the productivity gain — 90 minutes per person per week — that's real. That's time that can go into actual development. Lucas: Yeah. And if you extrapolate that across a 40-person team for a year, you're talking about over 3,000 person-hours saved. That's the equivalent of hiring one and a half extra engineers without adding headcount. Luna: Honestly, if this episode gave you one concrete idea you can try on Monday, that's pretty valuable. Lucas: And if it was worth a coffee to you, the link is buy me a coffee dot com slash fexingo. No pressure — just a way to keep the show ad-free and focused on real cases like this one. Luna: Yeah, listener support makes a difference. It means we can keep digging into the specifics without chasing clickbait. Lucas: So, to wrap up: the status board isn't for every team, but if your standups feel stale or wasteful, it's a low-risk experiment. One document, three bullet points, and a commitment to actually read each other's updates. That's it. Luna: And maybe the biggest lesson is that the ritual exists to serve the team, not the other way around. If a 15-year-old practice isn't working, you can change it. Lucas: Exactly. Next episode, I want to talk about something that sounds boring but is actually fascinating: how one team redesigned their code review process and cut review cycle time by half. Luna: I'm in. See you then.