Lunch & Learn series on From Code to Team (Second Edition), Chapter 11. 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 has a manager. Almost nobody has ever told that manager exactly where to push.
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.
"The patient doesn't look right."
A friend of mine spent 12 years as a nurse on a surgical ward before she moved into training, and she says that sentence is the one she spent most of her career trying to get junior nurses to stop saying.
Here is the night she tells. Two in the morning, a ward of 28 beds, one senior nurse — her — and a graduate 3 weeks in. The graduate comes to the desk, pale, and says exactly that: "Bed 14 doesn't look right." So my friend asks what she means. "I don't know. He just… doesn't." And my friend, to her credit, gets up and goes and looks, and bed 14 is fine — a bit restless, a bit warm, nothing that needs anyone woken up.
At 4 am the graduate comes back. "Bed 14 still doesn't look right." And this time my friend is with another patient, and says — the words she still regrets — "Keep an eye on him." Which is not an instruction. It is a feeling, handed back.
At 5:20, bed 14 is in serious trouble. He is fine now — this is not that kind of story — but it took a crash call and a very long morning, and in the review afterwards the consultant asked the graduate a question my friend has never forgotten: "When you came to the desk at 4, what did you want her to do?" And the graduate, in tears, said: "I wanted someone to come." And the consultant said, gently: "Then that is the sentence. Not 'he doesn't look right.' 'I need you at bed 14 in the next 10 minutes, because his breathing has changed since 2 and I am not comfortable.' She would have come."
Every hospital my friend has worked in since teaches this as a 4-letter thing — the situation, the background, your assessment, and your recommendation — and the whole point of the fourth letter is that the person paging you cannot act on a feeling. They can act on "I need you here in 10 minutes." They can act on "I want a review before 6." They can even act on "I think this is nothing, but I want it on the record that I said so." All 3 of those are asks with a shape. "He doesn't look right" is a problem handed upward, and a problem handed upward at 4 am gets handed straight back.
My friend's line, when she tells this to new nurses: "The consultant is not slow. You have not yet told her what you want her to do."
That is what today is about. The person above you is not an audience. They are a lever — and a lever does nothing at all until you tell it exactly where to push.
3:30A manager once asked me, in the middle of a resourcing conversation I had been pushing for weeks, to give him an idea of where I thought I could use the people I kept asking for. I did not have an answer. Not a real one. I had a problem — described accurately, at length, more than once — and nothing on the other side of it. No roles, no shapes, no dates. Nothing he could carry into a room and trade for. I had been asking for help for weeks and had never once given him the surface area to help me with.
It was not a communication failure; I had communicated constantly. It was not a relationship failure; we got on well. It was a failure to understand what the relationship was for. I had been treating my manager as an audience — someone to be kept informed, kept comfortable, kept on side.
5:00Your manager is the single most leveraged relationship you have at work. Almost every good outcome I have had above the first line traces to a manager who knew what I was doing before they had to ask and could speak for me in rooms I was not in. No surprises. Real ground truth. A short list of asks. Nothing here is a new skill — it is session 10's honesty about status, session 6's structured 1:1, session 9's escalation etiquette, pointed at somebody who never agreed to your working agreements. And for the engineers who never intend to lead: every mechanic here works one level down. Your lead is your manager.
Name both sides of the trade out loud. You want air cover for the hard call the organization does not yet understand; organizational context you cannot see from your seat; and honest calibration — where you stand and what would move you. You owe back no surprises; the unpolished read of what is actually happening, because a manager operating on your press release defends a position that does not exist; and a short list of asks, so their time converts into action rather than sympathy. When either side breaks, it does not blow up. It hollows out over 4 to 6 weeks and nobody names it. Your tell: you prepare the 1:1 as a recital. Theirs: the meeting starts moving. The anxiety underneath sounds like virtue and is fear: asking for things feels like admitting you cannot handle your own patch, so you report in a register of unbroken competence — everything is fine, no asks this week — until the week something is not fine and there is no way to say so that does not read as collapse. That is Devika's "no blockers" from session 4, one level up, with less excuse.