We Cut Our Daily Standup from 45 to 15 Minutes, with One Simple Change
We didn't remove any steps. We didn't force people to talk less. Just one fundamental change in how we approach the meeting.
Here's the full breakdown.
Context
I work on a large project for a major French bank a mobile app, a new bank within the bank. We're a team of 7: 6 engineers and 1 PM. A solid team, a good delivery pace. But our daily standup was the BIG negative point.
Standups running 30–45 minutes, constant one-on-ones, ticket-by-ticket rundowns of yesterday and today, people showing up unprepared, people showing up late.
Quick clarification on "one-on-one" in this context: it's when two people start solving a problem together live during the standup. One question, one answer, five minutes gone while the other five people just wait. Everyone checks out.
Why the Daily Standup Actually Matters
I know engineers don't love meetings. I'm an engineer. But I'm convinced that a standup done right is one of the most valuable rituals a team can have.
A standup gives the PM visibility to anticipate delays and surface andons. The andon concept comes from lean manufacturing it's a signal that says "I need help to move forward," without judgment, without shame. It's a powerful idea that most teams underuse.
The goal isn't to justify why you didn't finish your tasks. It's to understand why (not whose fault), analyze it, and learn from it.
A standup shouldn't explain yesterday. It should secure today.
What a Good Standup Looks Like
✅ 15 minutes max
✅ Everyone is clear on their day
✅ The PM/PO is clear on progress
Simple on paper. Harder to execute. Here's how we tried.
How Our Standup Was Structured
We applied what we'd always done with smaller teams: check the visual management board (Kanban or equivalent), do a global check on tracks, blocked tickets, and dependencies especially on the PO/PM side. Then each person would share their "truck".
The truck is the individual speaking format. Each morning, before the standup, everyone prepares their truck in writing. Then it's shared verbally during the meeting. Three sections:
What I did yesterday
Problems I ran into and how I solved them
What I'm doing today
Example:
What I did yesterday
✅ Enable company creation in the referential from the onboarding MS through to validation
✅ Notify the user of that validation via in-app notification
🚧 Display a banner in the app while the account isn't verified
Problems encountered
Didn't know how to call the Referential from the MS
- → Paul helped me, got unblocked
What I'm doing today
🚧 Display the unverified account banner
Fix bug on MS X
Prepare the training session
This looks clean. 2 out of 3 tickets done, 1 in progress. But here's the real problem we hadn't seen.
This format is entirely focused on yesterday. We're reacting to what happened, not preparing for what's ahead. And when someone doesn't finish their tickets, there's an implicit question hanging in the air: why?
To be clear: the goal isn't to question the person's work it's to understand why the system didn't allow them to succeed. Was the ticket unclear? Badly written or empty? Was the person never introduced to the epic? Were dependencies unresolved? Too many meetings? Too many tickets estimated?
That's the right kind of analysis. Not this:
"Why didn't you finish that ticket?"
"Who blocked you?"
"3 tickets is our standard, you need to stick to it..."
From a lean perspective, this format creates invisible WIP: blockers exist during the day but only surface at the next standup. Lead time quietly stretches. We're in push mode everyone works in their own lane until something breaks.
The Change: From Reporting to Planning
If the goal of the standup is to commit to X tickets, then it makes sense to also share the plan for getting there. When I say plan, I don't mean "write this code in this file" I mean andons.
The idea is simple: every morning, each person knows who they need to call or sync with, and each person knows who will be reaching out to them. That's the game changer.
We added a third section to the truck. And verbally, instead of listing tickets one by one, you say what you're working on today the theme, the direction. Tickets if really necessary, but the focus is the day's plan.
The same example, updated:
What I did yesterday
✅ Enable company creation in the referential from the onboarding MS through to validation
✅ Notify the user of that validation via in-app notification
❌ Display a banner in the app while the account isn't verified
- → Paul helped me, still in progress
What I'm doing today
🚧 Finish the unverified account banner
Fix bug on MS X
Prepare the training session
Plan to make my day work
→ Nicolas, I don't know the MS X bug domain well can we jump on a 5-min call this morning?
→ Valentin, the ticket isn't fully written yet can you complete it so I can start?
What this changes concretely: we move from a push standup (everyone reports what they did) to a pull standup (everyone pulls what they need to move forward). Andons are identified before the blocker hits, not after. Hidden WIP surfaces. Lead time decreases.
The Rules That Make It Work
Lateness
In our team, if you're late, you don't join the standup. This isn't a punishment it's simple logic. 15 focused minutes together to set up the day. If someone arrives 4 minutes late into a 15-minute meeting, it's disrespectful to everyone else's time.
I'm not talking about the occasional late arrival that happens to everyone. I'm talking about the same people, every single morning, consistently late. It might sound strict, and it definitely depends on your team's culture, but for us it was necessary.
One-on-Ones
The fix is simple: two enforcers. When a back-and-forth between two people starts stretching out, anyone on the team can say "take it after the standup." Why two and not one? So the responsibility doesn't always fall on the same person.
The Mindset During the Transition
The goal isn't to run the standup like a military drill. At the start of the transition, what matters is that everyone understands this is an important moment for the team. Over time it becomes natural people stop needing to be reminded.
Return on Investment
| Metric | Before | After |
|---|---|---|
| Standup duration | ~40 min | ~15 min |
| Blockers surfaced during the day | frequent | ~43% reduction |
| ( before: 2 weeks = 21, | ||
| after: 2 weeks = 9) | ||
| One-on-ones during standup | regular | 0 |
Beyond the numbers, here's what actually changes:
Everyone talks less, so the standup is shorter, so it's actually interesting. Nobody stares at their phone anymore.
Everyone knows clearly who raised an andon and when they'll be available.
Everyone is aligned on the major tracks and current big topics.
Everyone leaves with a plan for their day and the team starts to enjoy not being in reactive mode.
From a lean perspective: lead time drops because dependencies are visible upfront. Hidden WIP shrinks because andons surface in the morning instead of mid-afternoon. The standup becomes a real system synchronization tool, not just individual reporting.
Because a more performant team isn't a team that works more. It's a team that works better.