A 30-60-90 day plan is not a schedule. It is a commitment device, and almost every version circulating in leadership training is built as the wrong thing, which is why so many of them get written in week one, presented in week two, and never opened again.
The distinction matters because the two artifacts have different contents. A schedule lists what you intend to do. A commitment device lists what will be observably true on three specific dates, and the difference is that only one of them can be checked by somebody other than you. What follows is the version I would write, the template itself, and an honest account of what to leave out.
What a 30-60-90 plan is actually for
The plan exists to make your judgment auditable. It records what you believed on day one and what you committed to producing, so that on day 91 you and your boss are evaluating the same set of claims rather than two different memories of a conversation nobody wrote down.
That is a narrower purpose than most templates assume, and the narrowness is the value. A document trying to be a strategy, an introduction, a relationship map, and a schedule at once will not be checked against anything, because there is nothing in it precise enough to check.
There is a second audience for the document and it is not the one people write for. Your direct team will read it, and what they take from it is the standard of specificity you intend to hold. A plan full of soft intentions tells them that vague commitments are acceptable currency here, and you will get vague commitments back for a year. A plan where every line could be ruled on by a third party sets a different expectation without you ever having to give a speech about accountability, which is the more durable way to establish it.
Why learn, plan, act is the wrong content
Learn, plan, act describes phases of your internal process rather than outcomes anyone can observe. Nobody can tell from outside whether you learned in month one. They can tell whether the three numbers you said you would establish exist and whether the two decisions you said you would make have been made.
The second problem is that the phases are not sequential in any real operating role. You will be acting in week one whether you planned to or not, because situations arrive on their own schedule. A document asserting that you will not act until day sixty is either aspirational or a description of a job you do not have.
Replace the phases with states. By day 30, these things are established. By day 60, these decisions are made. By day 90, these mechanisms are running. Each of those can be verified by somebody who was not in the room.
Nobody can tell from outside whether you learned in month one. They can tell whether the three numbers you said you would establish actually exist.
The other reason phases fail is that they make the document unusable as a mid-quarter instrument. If the plan says you are in the learning phase until day sixty, there is nothing in it to check on day twenty, so nobody checks. A state-based plan can be read at any point: either the three numbers exist or they do not. That property is what turns the document from a presentation into something you and your boss actually open in week five.
What must be true by day 30
By day 30 you should have established facts, not formed opinions. Three to five numbers, each defined precisely enough that somebody else could reproduce them, each with a value attached, and each with a note on how it differs from what the reporting said.
The set will vary by role, but the shape does not. One capacity or throughput measure you counted yourself. One financial measure read against eight quarters of history rather than against budget. One measure of how the organization behaves, which is usually how long a decision takes. And the commercial reading: what you quoted and what you won.
If the plan says anything about strategy at day 30, that is a tell. Strategy formed on thirty days of information is a preference wearing a document.
What must be true by day 60
By day 60 the plan should name decisions made, not analysis completed. Two to four specific calls, each with a name and a date, each of which somebody in the organization will notice. Analysis that produced no decision is indistinguishable from no analysis.
The decisions at this stage should be ones you can make unilaterally. Thresholds, cadence, escalation rules, resource assignment, the retirement of something small. Save the decisions requiring your boss or a peer function for month three, when you have the day-30 facts to support them.
Include at least one decision that costs somebody something. A month-60 list of purely additive decisions demonstrates activity without demonstrating judgment, and everybody reading it knows the difference.
What must be true by day 90
By day 90 the plan should name mechanisms that are running without you. A weekly report someone else produces. A standing meeting someone else chairs. A number somebody owns end to end. These are the only day-90 outcomes that survive your absence.
The reason mechanisms belong at day 90 rather than earlier is that a mechanism installed before you have the day-30 facts will be aimed at the wrong thing, and removing a mechanism is considerably harder than installing one.
Do not put financial results at day 90. Operating changes take one to two quarters to reach a P&L, and committing to a financial number at ninety days is committing to something outside your control on a horizon that does not match the mechanism.
One more thing that belongs at day 90 and rarely appears: a named list of what you decided not to do. Every quarter contains three or four initiatives you deliberately declined, and they are invisible unless you record them. Writing them down protects you from the month-ten conversation where somebody asks why an obvious opportunity was ignored, and it demonstrates the thing a ninety-day plan is least able to show otherwise, which is that you were choosing rather than reacting.
The five lines your plan needs
Five lines carry the whole document: the situation you believe you are in, the evidence for it, what will be true at 30, 60 and 90, what you need from your boss, and what would make you change your assessment. Everything else is decoration.
The last of the five is the one almost nobody includes and the one that does the most work. Naming in advance what evidence would change your mind converts the plan from an assertion into a testable position, and it gives you a legitimate route to revise it in month two without that revision reading as retreat.
Keep the whole thing to eight lines and resist expanding any of them into paragraphs. The compression is not a formatting preference. A situation line that runs to four sentences is usually two competing readings that you have not yet resolved into one, and the discipline of choosing a single sentence forces the resolution while it is still cheap to get wrong. If you genuinely cannot compress it, that is useful information about how well you understand the business, and it is better to discover it in week one than in month six.
What to leave out
Leave out the relationship map, the list of people you intend to meet, the values statement, and any commitment to a financial outcome inside the ninety days. All four are standard in circulated templates and none of them is checkable.
Leave out anything you would be unwilling to be held to. A plan is a commitment device, so every line in it is a line you have accepted evaluation against. Padding it with soft intentions dilutes the lines that matter and trains your boss to skim.
And leave out length. If the document runs past a page, the excess is almost always things you put in to demonstrate thoroughness, and the reader will take away whichever paragraph happened to catch their eye rather than the position you actually formed.
Leave out anything that depends on somebody else delivering. Commitments contingent on a peer function, a system implementation, or a hiring decision outside your control will be the first ones to slip, and they will slip for reasons that are entirely reasonable and completely useless in a review. Put those in the what-I-need-from-you line instead, where they belong and where they create the right kind of pressure on the right person.
How specific should the commitments be?
Specific enough that a third party could rule on whether you met them without asking you. “Establish gross margin by product family for the last eight quarters” passes. “Develop a deep understanding of the cost structure” does not, because there is no state of the world in which it is unmet.
The test is adversarial: imagine somebody who wants to argue you did not deliver. If they have room to argue, the line is not specific enough. If they can only agree or disagree with a fact, it is.
Who should see it?
Your boss, and your direct team, and nobody else in the first ninety days. Your boss because the document’s purpose is shared evaluation, and your team because they are the ones who will be asked to produce most of what it commits to.
Sending it wider is tempting and usually costs you. A plan circulated to peers in month one gets read as a claim about their functions, and you will spend month two managing reactions to a document that was supposed to be an instrument rather than a communication.
What if you miss a milestone?
Write down that you missed it, why, and what changed, on the date you missed it rather than at day 90. A contemporaneous note about a missed milestone reads as judgment. The same note assembled in retrospect reads as an excuse, even when it is identical.
Missing one of three or four commitments is normal and says almost nothing. Missing them all says the plan was written to impress rather than to be met, which is a finding about the plan rather than about the quarter.
A contemporaneous note about a missed milestone reads as judgment. The same note assembled in retrospect reads as an excuse, even when the words are identical.
The template
Copy the eight lines below, fill them in, and delete anything you were tempted to add. It fits on one page by design, and the constraint is doing real work: a position you cannot state in eight lines is a position you have not yet formed.
- Situation: the state I believe this business is in, in one sentence.
- Evidence: the two or three facts that support it, with numbers.
- By day 30, these will be established: three to five numbers, each defined precisely.
- By day 60, these decisions will be made: two to four calls, each with a name attached.
- By day 90, these mechanisms will be running: two or three, each owned by someone other than me.
- What I need from you: specific, and short.
- What would change my assessment: the evidence that would move me off the situation line.
- Date written.
How to use it in a review
Bring the original, unedited, and go through it line by line in order. Do not produce a summary of the quarter. The document already framed the questions, and answering the questions you asked yourself in week one is a materially stronger position than presenting a narrative assembled in week thirteen.
Read out the situation line first and say whether you still believe it. That single move sets the whole conversation, because it demonstrates that the plan was an instrument rather than a formality, and it is the part your boss will remember.
Then keep it. The day-91 document becomes the baseline for the next one, and after three of them you have something more valuable than any of the individual plans: a record of how accurate your week-one reads tend to be, which is the thing that actually improves with practice.
About the Stagnation Assassin
Todd Hagopian is a Fortune 500 transformation executive who has generated $3B in shareholder value across Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, where he serves as Global VP of Product Strategy and Marketing. Known as The Stagnation Assassin, he is the author of two published books: The Unfair Advantage: Weaponizing the Hypomanic Toolbox and Stagnation Assassin: The Anti-Consultant Manifesto. His blog is published in 15+ languages and read by operators worldwide. Bring him to your stage via his speaking page or connect with him on LinkedIn.
Answer this before you write anything: could a third party rule on whether you met each line, without asking you? If the answer is no on more than one line, the plan is a schedule rather than a commitment. Send me your eight lines and I will tell you which ones would survive an adversarial reading.