90-day roadmap template — editable, free
A 90-day roadmap starts the day you start, not on a calendar quarter, and it is phased: days 1 to 30, 31 to 60, and 61 to 90. This one holds ten items across those three blocks, each carrying a confidence value, with a written diagnosis and a ninety-day review as milestones.
| View | Groups by | Visible fields |
|---|---|---|
Phases (board) | Phase | Name, Confidence, Status, End |
Leadership (timeline) | Phase | Name, Phase, Start, End |
Low confidence (timeline) | Phase | Name, Confidence, Start, End, only Low |
All items (table) | Nothing — one flat list | Name, Phase, Confidence, Status, Owner, End |
Why phases rather than dates?
Because the window starts whenever it starts. A 90-day plan beginning on 14 October has nothing to do with Q4, and forcing it onto calendar quarters produces a document where the interesting boundaries — day thirty, day sixty — are invisible.
So the grouping here is the phase, and the dates underneath are real dates you can schedule against. The board view reads as three blocks. The timeline reads as a window. Both are the same ten items.
What is in this template?
Ten items, weighted the way a real ninety days is weighted: the first block is almost entirely finding out what is true — customer calls, which numbers people already trust, actually reading the backlog — and it ends in a written diagnosis, on the timeline as a milestone.
The second block is where something is meant to stop. Naming three things to stop doing is the hardest item on the page and the one that buys room for everything after it, which is why it carries a note rather than sitting there as a title.
Every item has a confidence value, and the third block is almost all low. That isn’t pessimism; it is what you actually know on day one, and publishing it’s what stops the ninety-day review becoming a list of explanations. The fourth view filters to exactly those items, which is the list to revisit at day thirty.
Who reads this, and what happens after?
Usually one person, and then their manager. The onboarding audience has a field list of its own — roadmap for new team members is specific about why owner and notes earn their place on a view built for somebody learning the place, which is the opposite call from every other audience.
After day ninety this document should stop. The plan it produces is a longer-horizon one, and the habit that keeps it alive is in how to keep a roadmap up to date — attach the update to a meeting that already exists instead of to a reminder.
If the window really is a calendar month, a monthly roadmap template is tighter. If what you need is the goals underneath the work, a goal-oriented roadmap template puts the target above the items.
Common mistakes
Filling the first thirty days with delivery. The first block is for finding out what is true; a visible ship in week three usually means you committed before you understood the problem.
Skipping the written diagnosis. If it isn’t written down and circulated, there’s no shared account of what you found, and everything you do afterwards looks like preference.
Naming no things to stop. A ninety-day plan that only adds work is a wish list, and the room reads it as somebody who hasn’t yet had to choose.
Carrying high confidence into the third block. Day sixty-one is four months of assumptions away; marking it high is how the ninety-day review becomes a list of explanations.
Questions
Is this only for a new job?
No. A turnaround, a recovery after a bad quarter and the first ninety days of a new team all have the same shape: a fixed window, a diagnosis phase, and a review at the end that somebody has agreed to hold.
Why a confidence field instead of status?
Because most of the plan hasn’t started, so status says to do for everything and tells you nothing. Confidence says which parts you would defend and which you’re guessing at, which is the real state of a plan written on day one.
What happens on day ninety?
A review that either confirms the diagnosis or replaces it. The template puts it on the timeline as a milestone so it’s a commitment, not an intention, and so the person who agreed to it can see the date.
Related
- Monthly roadmap templateFour workstreams across one month at week resolution, and the point where this stops being a roadmap.
- Roadmap for new team membersOwner and notes are the payload here, shipped work stays on, and the dates come off.
- How to keep a roadmap up to dateStaleness is a copies problem, not a discipline problem. What to change so the update happens.
Last updated