Hosting a good morning standup — it’s all about the prep
The meeting is the easy bit
Most team leaders treat the morning standup as a meeting they have to attend. They walk into the room (or the Teams call) with no notes, ask “anything from yesterday?”, get a few shrugs, share whatever happens to be top of mind, run through “today’s targets,” and dismiss the team. Twelve minutes. Forgettable. Repeated 250 times a year.
The team leaders whose huddles are visibly better treat the standup as a meeting to prepare for. They spend 15 minutes before the huddle pulling together what actually matters. The preparation is the work. The meeting is the easy bit. This article is about the preparation.
Why most standups fail
Three failure modes account for most of it.
The status round-robin. “Anything from anyone?” — the question that empties a room. Agents share if they have something polished and ready; everyone else stays quiet. The room learns that silence is safer than contributing.
The unprepared TL. No data ready, no story to tell, no specific question to ask. The energy drains into the absence of leadership. The team has come for direction; they leave with none.
The dump-everything-on-the-team standup. Twenty minutes of new information, all of it serious, none of it actionable. The team has no chance to absorb it and no clear request. The meeting becomes a venting exercise for the team leader and a low point in the day for everyone else.
The 15-minute prep checklist
Good standup prep is short. The discipline isn’t time-consuming; it’s habit-driven. Fifteen minutes before the huddle, work through six things.
1. Yesterday’s shape (3 minutes). Open the dashboard. What was the SL? What was the volume vs forecast? What was the AHT trend? Which agents made the biggest difference, positive or negative? One number you want to recognise; one number you want to ask about. Not a recap of the entire day — the team was there.
2. Today’s ask (3 minutes). What does the forecast say today looks like? Is there a specific hour or skill that will be tight? Is there a known event — a marketing send, a system update, a TV ad, a weather event? What is the one thing you’ll ask the team to do well today? “Today is normal” is a fine answer when it’s true; it stops being credible if every day is “normal.”
3. The one customer story (2 minutes). One specific customer moment from yesterday — a great recovery, a complaint handled brilliantly, a piece of feedback that landed. Real. Recognised. Named (the agent, with their permission if it’s a praise). This is the single most underrated element of standup prep. The team comes for the story.
4. The one issue worth surfacing (2 minutes). One operational issue you want the team to know about — a system glitch, a process change, a returning bug, a known queue. Not a dump of everything. One thing. With a clear ask: what should they do differently because of it?
5. The personal moment (2 minutes). Whose birthday is it? Who came back from leave? Who finished probation yesterday? Who hit a milestone? Standups that recognise people land differently. This is where the team’s sense of being a team is built.
6. The one question you’ll ask (3 minutes). Plan the one question that isn’t “anything from anyone?” — pick something specific. “Who’s seen the new returns flow break this week?” “What’s the most common reason customers are asking for a callback?” “Anyone got a tip for the team on handling the new product enquiries?” A specific question gets specific answers. Open questions get nothing.
The agenda that works
A 12–15 minute standup, run in this order, leaves the team energised and clear.
0:00–0:30 — Open. One sentence. “Morning everyone, three things to share, one question for you, and the day ahead.” Sets the contract for the meeting.
0:30–3:00 — Yesterday in 90 seconds. The one number you want to recognise, the one number you want to flag. Not a recap. Anchored on what changed.
3:00–5:30 — Today. The forecast headline. The one hour or skill that matters. The one specific ask of the team.
5:30–7:30 — The customer story. Named, specific, two minutes. Either a recognition or a learning moment. Often the bit the team remembers.
7:30–9:30 — The issue worth knowing. One thing. What it is, what we know, what to do differently.
9:30–11:30 — The specific question. The one prepared question. Wait through the silence; somebody will answer if the question is specific enough.
11:30–12:30 — The personal moment. Birthdays, milestones, comebacks. Light, real, named.
12:30–13:00 — Close. “That’s us. Good shift.” Don’t let it overrun.
Common pitfalls
Overrunning. A 25-minute standup is a meeting; a 15-minute one is a huddle. Energy drops sharply after 15 minutes. Use the timer.
Defaulting to “anything from anyone?” It empties the room. Plan the one specific question instead.
Reading the dashboard at the team. The team can read numbers. They came for what the numbers mean and what the leader wants them to do about it.
Letting the loud voices dominate. Two agents in any team of fifteen will talk in any standup. The other thirteen go quiet. Direct questions, named, are the only fix.
Skipping the personal moment. When team leaders skip the human bit, the team learns the meeting is purely operational. The relational tone of the team is built or eroded in this 60-second slot.
Using the standup as the venue for performance conversations. Never. Performance conversations are 1:1, never in front of peers. Standup is for recognition, direction, and team mood; nothing else.
The five-day rhythm
Five days a week of standups risks repetition. The teams that handle this well rotate the focus across the week.
Monday — the week ahead. What the forecast says about the week, anything specific scheduled, what to look out for.
Tuesday — a customer-experience focus. A specific case, a piece of feedback, a complaint trend.
Wednesday — a process or product focus. Something the team should know better — a refresh, a new flow, a known issue.
Thursday — the people focus. Recognition. Wins. Milestones. The day to over-index on appreciation.
Friday — the week behind. What worked, what didn’t, what carries to next week. Honest, brief, looking forward.
The rotation isn’t rigid. But knowing roughly what the focus is each day takes the cognitive load off the prep and gives the team a recognisable rhythm.
The hardest part
The hardest part of standup leadership isn’t running the meeting. It’s having the discipline to prepare for it the same way every day, for years. The first week of any new team leader’s tenure has the best prep. The 18-month mark has the worst — the leader knows the team, the team knows the leader, the prep slips, the standup loses its edge.
The team leaders whose teams stay engaged keep the prep cadence anyway. Not because every standup is brilliant — most aren’t, and that’s fine — but because the discipline of preparing every day is the discipline that keeps the meeting honest. Standups that are prepared for are standups the team trusts. Standups that aren’t become a thing to endure.
Conclusion
A good morning standup is the visible 15 minutes that everyone sees. It’s earned by the 15 minutes nobody sees — the team leader pulling the data, writing the story, choosing the question, remembering whose birthday it is. The meeting is the easy bit. It’s all about the prep.
Pair with running the team huddle, real-time management top tips, the schedule review meeting, and coaching from QA results.