Lunch & Learn series on From Code to Team (Second Edition), Chapter 10. 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 in this room is read by somebody who will never watch them work.
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.
Two flights. Same airline, same route, 6 months apart. One of them I still think about, and it is not the one where things went wrong.
The first one. Somewhere over the desert, 3 hours out of Dubai, the seatbelt sign goes on and stays on. Nothing is said. Forty minutes. Then a voice: "Ladies and gentlemen, we're experiencing a small delay." A small delay. To what, from what? Nothing. Another hour. The cabin crew stops making eye contact — you know the look, the one where they have been told something and told not to tell you. The man next to me starts doing arithmetic about his connection out loud. Two hours after the sign went on, we land somewhere that is not where we were going, and then they tell us: a hydraulic warning, a precautionary diversion, a 5-hour wait for an engineer. Nobody was in danger. It was, honestly, a well-handled diversion. And every single person on that plane got off it furious — not because of the hydraulics, but because for 2 hours, 300 people had been building their own stories in silence, and every story was worse than a hydraulic warning.
The second flight. Twenty minutes after takeoff, the captain comes on — calm, slightly bored, the best register in the world — and says this. I wrote it down afterward. "Folks, a quick one. We've got a fault light on a system we don't need for this flight, but the rules say I get it checked before we cross the water. So here's what we're going to do. We'll turn around and land back at the airport, an engineer will look at it, and we'll be on our way. Best case, an hour on the ground. If it's the worst case, I'll tell you within 30 minutes of landing, and the ground team will have hotel and rebooking options ready. Nothing for you to do right now. I'll speak to you again when we're on the ground."
That is the whole thing. What is happening. What it means for me. Why, in one sentence, with no apology and no defense. The options, already on their way. And when I will hear from him next. The cabin went — quiet. Not tense. Quiet. People went back to their films. And he came on again 28 minutes after we landed, exactly as he said, and it was the worst case, and I did not hear one person complain.
Same airline. Same diversion, more or less. The difference was not the fault. It was that one captain told us early, short, with the ask attached, and the other one told us nothing until the story we had made up in our heads was already worse than the truth.
That is what today is about. Every one of you is that captain to somebody — a manager, a director, a peer team — and the only question is which of those 2 flights they are sitting on.
3:30Seattle, a Wednesday in the back half of 2021, the monthly business review — 20-odd people in the room and twice that on the dial-in. My project was 3 slides in when a director 2 levels above me asked about a dependency. The honest answer was that it had been in trouble for 9 days, that I had known for 8 of them, and that I had not told anybody above me because I was still, in my own head, working the problem. So he heard it in the room, in front of 40 people, from me, badly, with no options attached and no idea what I wanted him to do. He was completely reasonable about it. That was somehow worse.
What I lost was not the project — it landed, late and fine. I lost 6 months of being the person whose read could be taken at face value. For 2 review cycles I could feel the extra question underneath every question: is that the whole picture, or the picture as of the last time you looked? The dependency was ordinary. The delay was survivable. What cost me was that my manager's manager found out about my project at the same moment as 40 other people.
5:00Session 9 was tracking — how you know the truth. This is reporting — how everybody else comes to know it. A lead who tracks badly and reports well is dangerous: persuasive about a picture that is wrong. A lead who tracks well and reports badly is merely wasted. This is the chapter first-year leads skip, because reporting looks like the bureaucratic tax on real work. It is the mechanism by which the organization decides how much rope to give you, and one of the very few leadership acts visible to people who will never watch you run a stand-up. Your team experiences your leadership continuously. Everybody above and beside you experiences it almost entirely through what you write down. For the non-leads: everything here applies to the update you send your lead on Friday.
6:15The most common reporting failure is not dishonesty. It is sending one update to everybody. Your team needs the why and the change — they already know what happened — and nobody on your team should ever learn something about their own project from an outsider. Your manager needs exceptions and decisions, and there is a second obligation nobody thinks about: your manager will be asked about your project when you are not in the room, and the quality of their answer is entirely your doing. If they cannot summarize it in 3 sentences without calling you, that is a reporting failure. Executives need shape, risk and ask, with the mechanism removed — "2 weeks late because of a design problem we found in week 4 and have solved; new date the 14th; I need nothing." And the adjacent teams who depend on you hear about your slips when your manager does. One source of truth at 3 altitudes; write the wide one first.
Four parts, in this order. Where we are — one sentence with a state and a date, because most readers stop there. What changed — the delta; "no material change" is a complete update, and sending it is what makes the long ones credible. What is at risk — the week you first believe it might be real; a flagged risk that never lands is forgotten in a fortnight, an unflagged one that lands is remembered for years. And what I need — a decision by a date, a person, an introduction, or explicitly nothing. Assume a phone, between meetings, 11 seconds. Under 200 words. If the consequential fact is in the last line you have written a mystery novel. Short update, deep link.