Lunch & Learn series on From Code to Team (Second Edition), Chapter 8. 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 inside somebody's quarter right now. Most could not say, in one sentence, what it is for.
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.
Quick show of hands. Who here has, at some point, said out loud that this was the year they would ride the big one — the 200-kilometer day, the mountain, the ride they had been talking about?
Keep them up. Now — who rode it?
Right. That is the gap I want to talk about, and I was in the first group for 4 years running.
January, every year. The same sentence: this year. And I meant it. I serviced the bike. I rode in February. By April there was a work thing. By July it was dark at 6. In September I would think, well, next year, properly. Four Januaries. Zero big rides. Not because I was lazy — I was riding most weeks. Because a year is exactly long enough to never start the hard part.
Then a friend — who had done it 6 times — did something unkind. She entered me. Paid the fee. Sent me the confirmation. Twelve weeks out. And then she sent me a plan: 12 weeks, one page, every ride written down with a distance and a day. Week 1, Tuesday, 40 kilometers. Week 6, Sunday, 130. Week 11, taper. And at the top of the page, in her handwriting: "Every week you miss is 8% of the plan. Do the maths."
I did the maths. And something changed in my head that I had not expected. In January, a missed ride was nothing — there were 50 weeks left. In a 12-week plan, a missed Sunday was a thing. You could feel it. I rode in the rain. I rode at 5 am before a flight. Not because I had become a different person, but because for the first time the deadline was close enough to see and the plan was short enough to hold.
Here is the moment, though. Week 6. The plan said 130 kilometers on Sunday. I got to 95 and stopped, halfway up a climb, one foot on the ground, and I knew — not suspected, knew — that at this rate I would not make 200 in 6 more weeks. And I had a choice I had never had in the 4 January years: I could see it coming. I called her. She said: "Good. Week 6 is when you find that out. Do the 120-kilometer option, properly — or add 2 weeks and take the later date. Pick one today. Do not pretend." I took the later date. Eight weeks after that, I finished.
If I had found that out in week 11, there would have been nothing to pick. The 4 January years were not failures of effort. They were 12-month plans that never had a week 6.
Hands down. That is what today is about: why 90 days is the horizon a team can actually hold, why the halfway point is where a quarter is saved or lost, and why the plan has to be short enough to feel a missed Sunday.
3:30Somewhere around week 7 of my first serious attempt at running a quarter, I sat at a Sunday-night table with a printout of what I had told my manager the team would deliver 90 days earlier, and I could not, in good conscience, defend a single item on the list. Two of the goals had been overtaken by a re-org I did not see coming. One had shipped, quietly, without anyone remembering it was on the plan. Two were still being worked on by people who could no longer tell me why. And one — the one my manager cared about most — was in a state a generous reader would call "in progress," and an honest reader would call "we forgot."
I had not run a bad quarter. I had run no quarter. I had run 12 weeks of sprints stapled together, and the staple was the plan.
5:00A week is a heartbeat. A sprint is a lung. Ninety days is where a body of work happens. Shorter and you are just running sprints; longer and you are pretending to know things you cannot know. The frame that fixed it for me is The 12 Week Year — Moran and Lennington — which I re-read every 6 months: stop planning in 12-month years and plan in 12-week years. When you believe you have a year, you procrastinate. Look at any team carrying an annual number and the execution bunches into the weeks before the deadline — the deadline produced it, not the plan, and an organization running one deadline a year has arranged to be good at its job for 6 weeks out of 52. Twelve-week years give you 4 deadlines instead of one. Every week you delay is 8% of the plan.