You know the moment. Nine people on a call. One person is talking. The other eight are on mute, cameras half-off, waiting for their turn to recite what they did yesterday. Nobody is listening. Nobody is unblocked. You, the engineering manager, are nodding along and quietly wondering when standup stopped being useful.
Here's the thing: standup didn't fail. It drifted. It started as a fast sync to surface blockers and quietly became a status report performed out loud, once a day, for an audience of one. And the person it's performed for is you.
This post is about pulling it back. Two moves: a 3-question reframe that changes what people say, and an async board column that moves the reporting part out of the meeting entirely.
Key takeaways
- Standup drifts into a status report when the questions reward recitation instead of surfacing blockers.
- Swap the classic three questions for three that force signal: what's blocked, what changed, what needs a decision.
- Move the "what I did" part async into a board column, so the live meeting only exists for things that actually need a human in the loop.
- Written updates on the card, not spoken updates in a call, mean the context lives where the work lives.
- You can often skip the synchronous meeting entirely on days when nothing is blocked.
Why standup becomes a status report
The original three questions are famous: What did you do yesterday? What will you do today? Any blockers? Read them again. Two of the three are backward-looking status. Only the last one is about unblocking, and it's the one people rush through because they've already spent 40 seconds narrating their commit history.
So the format trains the wrong behavior. People prepare a recitation. They optimize for sounding busy, not for flagging risk. And because everyone knows the manager is listening, standup becomes a daily performance review that nobody scheduled.
The tell: if a teammate could email their standup answer and lose nothing, it was a status report, not a sync.
The 3-question reframe
Keep the meeting short. Change what it asks. Instead of "what did you do," ask questions that only produce value when spoken to other humans in real time.
1. What's blocked, and who can unblock it?
This is the only question standup ever truly needed. Not "do you have blockers" as a throwaway at the end, but the opening line. If nothing is blocked, that person's standup is one sentence: "Nothing blocked, moving on." That's a feature, not a failure.
2. What changed since yesterday that others need to know?
A shifted estimate. A scope discovery. A production edge case. This is the stuff that email is too slow for and that a written update buries. It's genuinely worth saying out loud because it changes what other people do today.
3. What needs a decision from this group?
Standup is the cheapest place to get five engineers to agree on a small call before it becomes a big one. "Should we ship behind a flag or wait?" takes 30 seconds live and three days in a comment thread. Use the synchronous time for the thing that's actually synchronous: deciding.
Notice what's gone: nobody reports what they did. That part moves to writing.
Move the reporting to an async board column
Here's the mechanical fix. The "what I'm working on" part of standup doesn't belong in a meeting. It belongs on the board, where the work already lives.
Set up a board with your normal flow, then treat the in-progress column as the async standup. Every card in progress already carries its own state: who's assigned, the priority, the due date, the checklist of subtasks, and a comment thread. Instead of narrating that in a call, your team writes the one thing that isn't obvious from the card into a threaded comment with an @mention if someone needs to see it.
Now the update is attached to the work, not floating in a call transcript nobody kept. Someone joining mid-sprint reads the card, not a Slack scroll-back. And you, as the manager, get to review status when you have the attention for it, not in a 9am ritual where you're processing nine updates in twelve minutes.
The best async standup isn't a channel where everyone pastes three bullets. It's the board itself, kept honest, with the one non-obvious thing written on the card.
Automate the nudge, not the meeting
The failure mode of async is that people forget to write anything. So automate the reminder. A scheduled automation can fire on a cron each morning and send a notification prompting people to update their in-progress cards before the team looks at the board. The reminder is automatic. The update stays human.
You can also lean on personal daily planning. A per-person daily task list, with time estimates and notes, carries unfinished work forward day to day. That's the individual's version of "what am I doing today," and it never needed an audience.
What this actually changes for an engineering manager
Three things. First, your live meeting gets shorter and sharper, because it only contains blockers, changes, and decisions. Second, status becomes readable instead of performed, so you can absorb it asynchronously and spend your synchronous time on the humans who need you. Third, on days when the board is clean and nothing is blocked, you can just skip the call. The board already said everything the meeting would have.
You're not killing standup. You're deleting the status-report tax that crept into it and keeping the 10% that only works when people are in a room together.
FAQ
Isn't a written async update just a status report in a different format?
Only if you copy the old questions into a text box. The point isn't the medium, it's what you ask. Async should carry the "what I'm doing" state on the card. The live meeting should carry only blockers, changes, and decisions. Split them by purpose, not by tool.
Won't skipping standup make my team feel disconnected?
Connection doesn't come from reciting task lists. It comes from unblocking each other and making decisions together, which the reframe protects. Keep the meeting for the moments that need it and drop it on the days that don't.
How do I stop the async channel from becoming noise?
Attach updates to the work. A comment on the card with an @mention reaches exactly the person who needs it, and the context lives next to the code, the checklist, and the due date instead of scrolling away in a chat channel.
What if leadership expects a daily status readout?
Give them the board. A read-only view of your in-progress column, with priorities and due dates, is a better status report than anything narrated in a call, and it updates itself.
How often should the team actually meet synchronously then?
As often as there are real blockers and decisions, which for many teams is less than daily. Let the board carry status continuously and let the calendar carry only the conversations that need voices.
Standup was never meant to be a report. Rebuild it around the three questions that need a human in the loop, move the rest onto the board, and let async do the reporting it was always better at.
Photo by Paper Textures on Unsplash