Lunch & Learn series on From Code to Team (Second Edition), Chapter 4. 20 minutes: a story before the first slide (under 4), 12 talk, 4 discussion. Verbatim script; timing marks are the running clock. Slide numbers match the deck.
Room: mixed — leads, aspiring leads, and engineers who never intend to lead. Everyone attends these 5 meetings. Most will chair one within the year if the rotation is running.
0:00Told with the title slide up and nothing else. Under 4 minutes. Not on any slide. Presenter's voice; swap in your own, keep the shape.
"Right side. Confirmed." Say it and stop.
A friend of mine is an anaesthetist. Twenty years in operating theatres, and she told me this over dinner the way you tell a story you have told yourself many times.
Seven-forty in the morning, theatre 4, a knee. Before every operation there is a thing called the checklist — the whole team stops, and somebody reads a list out loud: patient's name, the procedure, which side, allergies, blood available. Everybody answers. It takes 90 seconds. And she told me that in most theatres, most mornings, it is the most pointless 90 seconds of the day, because everybody answers in the same flat voice they use for their own phone number. Name, confirmed. Side, confirmed. Allergies, none. Nobody is listening. They are waiting for it to end so the real work can start. She said she had watched surgeons answer with their backs to the room.
That morning the list was read. Right knee. Confirmed, confirmed, confirmed. The surgeon was already gloved. The patient was already asleep.
And a scrub nurse — a young one, 6 months in, the most junior person in the room — said, quietly: "Sorry. The consent form says left."
Silence. The kind where you can hear the ventilator.
Somebody went and got the form. It said left. The X-rays on the wall were up the wrong way round. And 8 people who had just said right, confirmed in their phone-number voice stood there and understood that the checklist had not caught it. She had caught it, because she had actually read the piece of paper the checklist was supposed to make everyone read.
Here is the part my friend wanted me to understand. The consultant surgeon — a formidable man — took his gloves off, walked over to that nurse, and said, in front of everyone: "Thank you. Say that every time." And then, from that day, he changed one thing. At the start of every list, he made every person in the room say their name out loud first. Not because anybody had forgotten it. Because a person who has just spoken in a room will speak again in that room, and a person who has not, will not.
My friend's line, over the dinner table: "The checklist did not save that knee. A meeting where the youngest person could speak saved that knee. The checklist just gave her the 90 seconds to do it in."
That is what today is about. Every team runs these meetings — the stand-up, the planning, the review — and it is entirely possible to hold every one of them, perfectly on time, in the phone-number voice, and never once make the decision the meeting exists for.
3:30Bengaluru, second month on the identity team. Stand-up at 11:15 IST, the last honest window before the US day. Devika, 4 months into her first cross-region team: "Yesterday I looked at the certificate-rotation issue. Today I'll keep looking at it. No blockers." She said it the way she had said it the previous 9 mornings — cleanly, in the cadence of someone who has learned what the meeting rewards. I nodded. The stand-up ended on time. It had ended on time every morning for 2 weeks.
On day 13, a customer escalation surfaced that the rotation had been silently failing since before she opened the ticket, and that she had known since day 2 that she did not know how to fix it. Devika paid the formal performance cost. But the ceremony had failed her first, and I had built the shape of it — a person-first meeting that taught her a blocker was a personal admission.
That is the handle for the whole chapter: the ceremony serves the decision, or it serves no one. It is possible — common — to hold every meeting in the Scrum guide and fail to make a single one of them. Five ceremonies today, each with one sentence to hold, one story of it failing, and one mechanic. For the half of the room that does not lead: if the chair rotates, and I am going to argue it should, you will be running these within the year. Every mechanic here is yours.