1 September, and an uncomfortable fact from years of year-end reviews: by December you will have a Q4 narrative. A sentence or two the people above you would use about your autumn. "Solid, kept things running." "Stepped up on the restructure." "Gone a bit quiet since summer." The narrative will exist either way; the only variable is the author.
Left alone, it writes itself out of accidents: whichever project happened to be visible, whichever fire you happened to catch, whoever happened to mention you in whichever meeting (day 4). Most careers run on accidental narratives, which is most of what "luck" means in organisational life. The protocol below writes the narrative first, then engineers the quarter to make it true. One page, three parts.
Part one: the headline
The sentence you want said about you in the December reviews. Specific, and scoped one level up: "Owned the pricing migration end to end, and the exec knew it." The second clause is not vanity; it's the transmission half of the series (days 6, 7, 8), stated as an outcome. A headline without a transmission clause is a diary entry.
Part two: the proof
Two or three concrete deliverables that make the headline true, numbers attached where possible, chosen because they're both real work and visible work. Where those diverge, and they will, you now have a decision rule for your autumn: the work that serves the headline wins your discretionary hours. This is the OVD engine run as a quarter: Observe what the system rewards (days 1, 4, 38), create Value against it, Deploy it where deciders can see (days 3, 6, 8). All three, deliberately, or the narrative reverts to accident.
Part three: the audience
Who must witness the proof, by name, through which channel: the Friday note, the monthly 1:1 mention, the skip-level update, the altitude upgrade (day 6). Your decider map (day 16), given a specific job for a specific quarter. Three names is enough; the room is small (day 1).
The survival mechanism
The January version of this plan dies by week three every year, cause of death always the same: written once, never re-read. This one survives because it plugs into machinery you've already installed: the weekly board meeting (day 21) checks progress against the headline; the Monday fifteen (day 36) schedules each week's transmission; the evidence file (day 2) accumulates the proof. The plan isn't a document. It's a setting on systems already running.
Why 90 days
Deadlines govern behaviour only when near enough to feel. A year is abstract; December is real, and it starts being real today, which is why this edition is dated 1 September and not 1 January. The autumn quarter also happens to be the one the real promotion calendar (day 38) is reading. Your narrative and the drafting season are the same window.
Your assignment
The three parts, one page, twenty minutes tonight. Then set it as this Sunday's board meeting agenda.
Talk soon, Yasar
P.S. Tomorrow, with five days left, the complete breakdown of what the Executive Cohort is: format, tools, who it's for, who it isn't. If your 90-day plan deserves backup, read it carefully.
