Lunch & Learn series on From Code to Team (Second Edition), Chapter 7. 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 here will receive a review this year. About a third will write one. All of them will be read, years from now, by someone with no context.
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.
Fourteen cakes. Say it and stop. Fourteen cakes, one afternoon, and I gave the ribbon to the wrong one.
A community show, a marquee, a trestle table with a white cloth, and me — for reasons that were never fully explained — as one of 3 judges of the sponge section. There is a sheet. There are criteria: crumb, rise, flavor, presentation. Ten points each. Very fair. Very rigorous. I had a pencil.
Cake number one, I tasted carefully. I wrote 4 lines. Cake 2, 3 lines. By cake 8 I was writing a number and a word. By cake 12 the marquee was hot, I had eaten 12 slices of sponge, and I could not have told you, under oath, what cake 3 tasted like. Then cake 14 — the last one — was warm. Still slightly warm from the oven. Lemon. And it was lovely, and I wrote 9, 9, 9, 8, and we gave it first prize, and the woman who made it cried, and it was a nice afternoon.
Except that on the drive home the other judge — a retired home-economics teacher, 40 years of shows — said, without looking at me: "Cake 3 was the best cake on that table. You gave it a 6 for crumb. Did you look at your notes before you scored 14?"
I had not. Nobody had. We had scored 14 cakes against whatever we could remember, and what you can remember at 3 pm in a hot tent is the one you just ate. She had a system, it turned out — she tasted the last cake, then went back and re-read her own notes on every cake in order, and only then wrote a ranking. Cake 3 had been dense, dark, perfectly even, and cold — because it had been baked properly, the night before, and cut cleanly. It had lost to a warm one.
She said one more thing, which is the reason I am telling you this. "The notes are not for the cake. The notes are for you at 3 o'clock — so you judge the cake you tasted, not the cake you remember."
I have judged nothing since. But I have written a great many things that decide what happens to a person for the next year, and I have written most of them at 3 o'clock, in a hot tent, with the warm lemon one right in front of me.
That is what today is about: the review is only ever as good as the year you actually read — not the year you remember. And the notes are for you at 3 o'clock.
3:30The first annual review I ever wrote, Melbourne, took me a full weekend to draft and about 90 seconds to deliver. I remember the 90 seconds better than the weekend. I read what I had written out loud in a small meeting room, watched the engineer nod politely at each paragraph, watched them not react to any of the specific things I had agonized over, and walked out convinced I had done the job.
Three months later, in a 1:1 that had drifted somewhere real, they told me the review had been the least useful conversation we'd had all year. "Everything you said was true. But I already knew all of it. And the 2 things I actually wanted to talk about weren't in there."
5:00That is the chapter in one paragraph. A review is not the moment feedback happens. It is the moment feedback gets summarized. If session 6 was run well, it is 90% written before the template opens. It has to answer the 2 questions every person carries into the room: where do I stand? — which needs judgment — and what happens next? — which needs care.
The frame I hold: a document you would be proud to have subpoenaed, and proud to read aloud to the person 5 years later. Every sentence defensible, dated, and something they have already heard from you. For the half of the room that does not lead: you are on the receiving end of everything here, and I want you to leave able to tell the difference between a hard review and a bad one.