Lunch & Learn series on From Code to Team (Second Edition), Chapter 1. 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. Every session has a half for each: what the lead does, and what the team should be able to expect.
0:00Told with the title slide up and nothing else. Under 4 minutes. Not on any slide. It is written in the presenter's voice; swap in your own if you have one, but keep the shape — one moment, the payoff held back, a turn, a takeaway.
Three hundred feet. Say it, then stop. Three hundred feet above the runway, and my hands are on the controls I am not supposed to be touching.
A friend of mine flies for a regional airline, and this is the story he tells new captains. For 9 years he was a first officer — the person in the right-hand seat. And he was, by every account including his own, a very good one. Smooth on the controls. Landings you did not feel. Captains asked for him by name.
Then he got the upgrade. Left seat. Four stripes. And on his first week in command, a Tuesday, crosswind at a short runway, he is sitting in the left seat with a first officer 8 months out of training — Priya, competent, a little tentative — flying the approach. And here is the moment. Three hundred feet. He can see she is drifting a touch left of the centerline. Nothing dangerous. Well inside the limits. The kind of thing she would have corrected herself in about 2 more seconds. And without deciding to, he says "I have control," and takes the aeroplane, and puts it exactly on the centerline, and lands it beautifully.
He was, for about 30 seconds, very pleased with himself.
Then he looked across the cockpit. Priya was not annoyed. She was waiting. Hands in her lap. And for the rest of that 4-day trip, every time the aircraft did anything, she looked at him first — not to ask, to check whether he was about to take it again. On day 3 she flew an approach so carefully, so far inside the limits, that it was actually worse, because she was flying for him instead of flying the aeroplane.
He told me the thing that made him understand it was not her. It was the debrief on the last night, when the training captain riding with them said: "On Tuesday you were still the best first officer on this airline. The problem is that nobody was being the captain." Because a captain's job at 300 feet is not to land the aeroplane. It is to decide whether the approach is safe to continue, watch the whole picture, and let the person flying fly. He had done the one thing he was brilliant at, and in doing it, had made the whole crew slightly worse — and taught his first officer that on this flight deck the important controls belong to the person on the left.
It took him most of a year, he says, to learn to keep his hands in his lap while somebody landed 2 meters left of where he would have. And he says the day he knew he had become a captain was the day he did not notice that Priya's landings were now better than his, because he was looking at something else. Which is the whole job.
That is what today is about: the day they give you the left seat, and every muscle you own still wants the controls.
3:30Melbourne, winter of 2005. First week I ever ran a team. Four engineers, an office I could cross in 6 paces. Friday afternoon, half-empty office, I close my laptop — and I genuinely cannot tell you what I did that week.
I can tell you what I touched. Eight email threads, answered. Six meetings, sat through. Two pull requests reviewed. And a customer escalation with my name on it that I hero-coded at 11 pm on the Wednesday from my kitchen table, because mine felt like the fastest hands in the room. Radhika, whose ticket it was, thanked me the next morning. My manager thanked me by mid-afternoon. The customer thanked me. The code shipped.
And I still could not tell you what I had done. The quarter before, I had shipped a feature alone at 2 am on a Saturday and could recite every commit from memory. That was a good week. This — was this a good week? I had no instrument that could tell me.
5:00Nobody rewrites your job description on the day of the promotion. HR sends a form. Monday arrives, and 10 or 15 years of muscle memory — close the ticket, close the design, close the incident — closes right down on you again and lies to you about what a good day now looks like.