Morning all. Right — let's keep this tight, fifteen minutes max. Same as always: what you did, what you're on today, anything in your way.
"Let's keep this tight, fifteen minutes max" — David sets the clock in the first sentence. That one line gives him permission to cut people off later without it feeling personal. And "same as always: what you did, what you're on, anything in your way" re-states the format. A stand-up only stays short if someone says out loud that it's short.
Sorry, sorry — I'm here. The call dropped.
No drama, we've just started. Priya, want to kick us off?
"No drama, we've just started" — David doesn't stop, doesn't recap, doesn't make Marco explain. Someone joining late is the most ordinary thing in the world; treating it as a non-event keeps the meeting moving. Note "no drama" — very common, very casual, means "that's completely fine."
Sure. Yesterday I finished the mapping for the customer tables. Today I'm on the transaction load — should be done by end of day. No blockers.
Yesterday. Today. Blockers. Three sentences, twelve seconds, done. Notice what's missing: no background, no explanation of why the mapping took time, no apology. "No blockers" is a complete answer — you don't need to fill the silence. This is the model the whole pack is built around.
Still good for Thursday?
Yep, on track.
"Still good for Thursday?" — a yes/no question, answered with one word. In most meetings you'd ask "how's it looking for Thursday?" and get a paragraph. In a stand-up you ask questions that can be answered in a syllable. If the answer had been "no", then it becomes a conversation — offline.
One flag though — the transaction load needs Tom's requirements doc to be final. If that slips, I slip.
"If that slips, I slip" — six words that do a lot of work. Priya isn't complaining or blaming Tom; she's making a chain visible so nobody is surprised later. "One flag though" is the standard way to add a caveat without turning your update into a discussion. Naming dependencies out loud is most of what a stand-up is actually for.
Noted. Tom, that's on your radar?
Yeah, it's my main thing today.
David doesn't discuss the dependency — he just checks the other end of the chain exists ("that's on your radar?") and gets a one-line confirmation. On your radar = something you're aware of and tracking. The dependency is now shared knowledge, and it took eight seconds.
Perfect. Marco?
Two words of acknowledgement, then the next name. David doesn't comment, doesn't ask a follow-up, doesn't say "great, and how's that looking overall?" In a stand-up, the chair's job is traffic control, not conversation.
Okay so, yesterday I was checking the product hierarchy — the one from the legacy system. Today, same. But I'm a bit stuck.
I need someone from the finance side to confirm which version is the right one. And, um, I don't know who to ask.
"I'm a bit stuck" — no apology, no long story, no defensiveness. Then the specific need: who can confirm which version. Being blocked is not a confession; it's information the room needs. What makes a blocker useful is being concrete: not "the hierarchy is confusing" but "I need someone from finance to confirm which version."
That's Elena. I'll intro you after this — two minutes, I'll send a note.
David doesn't discuss it. He doesn't ask why Marco didn't know, doesn't explore the hierarchy question. Name, action, owner, timeframe: "That's Elena. I'll intro you after this." A blocker in a stand-up should get an owner in seconds — the actual work happens afterwards.
And I've got the old mapping doc from phase one — might save you a bit of time. I'll ping it over.
Priya doesn't ask "have you tried X?" or start diagnosing. She names one concrete thing she has and commits to sending it: "I'll ping it over." (Ping = send quickly, very common.) Offering help in a stand-up works when it's an action, not a discussion.
Ah, perfect — that saves me half a morning. Thank you. And the supplier codes are done, by the way. No issues there.
Marco takes the offer without the reflex "oh, don't worry, I'll manage" — he says what it's worth ("saves me half a morning"), which makes the help feel valued rather than pitied. Then he closes a thread the team was tracking: "the supplier codes are done." Finished work deserves one sentence too — not just problems.
Quick one for Priya — is the test environment getting refreshed this week? I keep hitting old data.
Wednesday morning. I'll drop a note when it's done.
Great, thanks — that explains a lot, actually.
Not every question breaks the format. The test is whether the answer fits in one line. "Is the test environment getting refreshed this week?" → "Wednesday morning." Done in ten seconds. "Quick one for X" is the standard signal that you're asking something small — it tells the room "this won't turn into a conversation," and it obliges you to keep that promise.
Tom — before your update, did the access request go through?
Ah — not yet. It's with IT, I'm chasing today.
Cool. Shout if it's still stuck tomorrow.
Three lines, no tension. David asks a factual question; Tom gives a factual answer ("not yet, I'm chasing") with no excuses; David sets a trigger for escalation ("shout if it's still stuck tomorrow") and moves on. Nobody is in trouble. This is what healthy accountability sounds like — the action is tracked, the person isn't judged.
Yeah so — yesterday, I picked up the reporting requirements, which, honestly, has turned into a bit of a can of worms, because when we originally scoped this we assumed the regional split was fixed, but then it turns out marketing have been using a different split since about March, and, um, I think this connects back to what Priya was saying last week about the —
Watch the shape: Tom starts fine, then adds because, then but then, then and I think this connects back to — each clause opens another one. It's not that he's wrong; the content is real. It's the wrong meeting for it. This is the most common stand-up failure, and non-native speakers do it more, because when you're unsure, you add context. (Can of worms = a messy problem that keeps growing once you open it.)
Tom — sorry, can I jump in? This sounds important, but it's bigger than a stand-up. Can we take it offline? You, me and Priya, straight after.
This is the phrase to steal from this pack. Look at the structure: name ("Tom") + soft interrupt ("sorry, can I jump in?") + validate ("this sounds important") + reason ("bigger than a stand-up") + concrete alternative ("you, me and Priya, straight after"). It's not "we don't have time for this" — it's "this deserves its own conversation." Interrupting is not rude when you give the thing somewhere else to go.
Yeah — no, fair. Sorry, I was off. Today I'm on the requirements doc, and that's my only blocker really — needing that split confirmed.
Tom doesn't get defensive or spiral into apology. "Yeah — no, fair" and he re-does his update in one clean line. (I was off = I went off-topic.) Being cut off in a stand-up is normal; taking it well and compressing on the spot is a skill. Notice he still lands his blocker — "needing that split confirmed" — so nothing is lost.
Just quickly — if the split's changed, that might affect my mapping too, so —
Yep. Park it — you're in the offline anyway. Let's not solve it standing up.
The discussion tries to restart, and David closes it in seven words. "Park it" is the shortest version of "take it offline." And the little joke — "let's not solve it standing up" — names the whole principle of the meeting: a stand-up surfaces problems, it doesn't fix them. Humour makes the cut-off land softly.
My turn — quick one. Yesterday, steering committee prep. Today, same, plus the Elena intro for Marco. Not blocked.
David gives his own update in the same three-part shape he asked of everyone — and it's the shortest one in the room. If the person running the meeting rambles, nobody else will keep it tight. "Plus the Elena intro for Marco" also closes the loop out loud: the action from two minutes ago now sits in someone's day.
Oh — one more thing, quickly. I'm off Friday, so if anyone needs anything from me, today or tomorrow.
"I'm off Friday" — no explanation, no apology, no "is that okay?" You're not asking permission; you're giving the team information. Then the useful half: "if anyone needs anything from me, today or tomorrow." That turns a note about you into an action for them. And "one more thing, quickly" is the polite way to add something after your update has finished.
Good shout. Anything you need from us before then?
Just Elena, really. Everything else can wait till Monday.
Good shout = good point, thanks for raising that. Extremely common in UK-influenced workplaces, and useful precisely because it's two words. David then checks the practical consequence in one question. Notice Marco's answer ties back to the blocker from two minutes ago — the meeting is holding its own thread.
And Thursday's demo — Priya, you're driving, right? I'll do the intro, you do the walkthrough.
Yeah, that's the plan.
"You're driving, right?" — David isn't opening a discussion about who should present; he's confirming something already agreed and stating the split in one line ("I'll do the intro, you do the walkthrough"). Driving = leading/running it. A stand-up can confirm a plan in eight seconds; it should never make the plan.
And heads up, all — Sarah's joining the first fifteen minutes of that demo.
Ah, good to know. I'll tighten the walkthrough then.
Heads up = advance warning so you can adjust. David doesn't say what to do about it; he just puts the fact in the room, and Priya draws her own conclusion ("I'll tighten the walkthrough"). That's the whole mechanic of a good stand-up: information in, decisions made by the people who own the work.
One ask, Priya — can you send me the two headline numbers for the steering committee deck? By lunch if you can.
Yep, I'll send them straight after this.
"One ask" signals a request, not a discussion — the room knows this won't expand. Then all three parts arrive together: what (two headline numbers), why (for the steering committee deck), when (by lunch if you can). "If you can" softens the deadline without making it vague. A request with no deadline is a wish.
Right — that's it. Three things off the back of this: Elena intro for Marco, Tom, Priya and me on the regional split straight after, and Marco's out Friday. Anything else that can't wait till tomorrow?
David recaps only the actions — not the updates. And the closing question is precisely worded: not "anything else?" (which invites a new meeting) but "anything that can't wait till tomorrow?" That phrasing gives people an easy no. A good chair makes silence the natural answer.
Nothing from me.
Nope, all good.
Two of the most useful phrases in working English, and they're three words each. "Nothing from me." "Nope, all good." You don't need a sentence. Non-native speakers often feel that saying nothing is impolite, so they add something — in a stand-up, the polite thing is silence.
Same, nothing here.
And the offline — now, or later?
Now. Marco, I'll ping Elena in the meantime — check your inbox in five.
"Now" — one word, and the deferred conversation becomes a real one. This is the difference between "take it offline" as a genuine move and as a polite way of burying something. David also gives Marco a concrete window ("check your inbox in five"), so the action from the start of the meeting lands before anyone forgets it.
Beautiful. Nice and quick — that's how they should be. Tom, Priya, stay on for two secs. Everyone else, see you tomorrow.
"Nice and quick — that's how they should be" — David points out they beat the clock he set at the start. Small thing, but it reinforces the culture: short is good, and short gets noticed out loud. Then he does the thing that makes "take it offline" real: "stay on for two secs." The offline happens now, not "sometime" — an offline that never gets scheduled is just a polite way of dropping a problem.