Strategy Roadmap: How to Turn Your Vision Into a Quarterly Plan
7 min read ยท 2026-10-09
A strategy roadmap is a visual plan that links your long-term vision to the work your team will do this quarter. It works as a chain: a vision, 3 to 5 strategic pillars, yearly outcomes, quarterly objectives, and finally initiatives with owners and dates.
You can build the first version in about six weeks. After that, you review it every quarter. The vision and pillars stay stable for a year or more. The quarterly plan changes as you learn. The roadmap below covers every phase. It then explains how to write each layer, how to run the quarterly review, and which mistakes to avoid.
The roadmap at a glance
Goal: Turn a company or team vision into a quarterly plan with clear owners and measurable outcomes. Duration: 6 weeks to build, then a review every quarter
Write the Vision (Week 1)
Agree on where you want to be in 3 to 5 years, in words everyone can repeat.
- Interview the founders or leadership team for 30 to 45 minutes each, one at a time.
- Write down the problem you solve, who you solve it for, and what success looks like.
- Draft a vision statement of one or two sentences.
- Share it with a few people outside leadership and ask them what they understood.
Milestone: A vision statement signed off by leadership, which people outside the room can explain back.
Choose Your Strategic Pillars (Week 2)
Pick the 3 to 5 big areas where you must win to reach the vision.
- List every possible focus area, then group the ones that overlap.
- Keep only the areas where a big change would move you toward the vision.
- Name each pillar in plain words, for example "Win mid-size customers" or "Make onboarding effortless".
- Write one sentence per pillar that explains why it matters now.
Milestone: 3 to 5 named pillars, each with a one-sentence reason.
Set Yearly Outcomes (Week 3)
Decide what must be true at the end of the year for each pillar.
- Write 1 to 3 outcomes per pillar. Each one should describe a result, not a task.
- Attach one metric to each outcome, and record today's value as the baseline.
- Set a target for the end of the year.
- Remove any outcome nobody can measure yet, or add "set up the measurement" as an early task.
Milestone: A list of yearly outcomes, each with a baseline, a target and one owner.
Break Outcomes Into Quarterly Objectives (Week 4)
Split each yearly outcome into steps your team can reach in 90 days.
- For each outcome, ask: "What must be true by the end of this quarter to stay on track?"
- Write 2 to 4 objectives for the coming quarter, with key results you can check.
- Sketch rough themes for the next three quarters, without fixing the details.
- Check team capacity and cut objectives until the plan fits.
Milestone: A quarterly plan with objectives and key results for the next 90 days.
Plan the Initiatives (Week 5)
Turn each quarterly objective into concrete projects with owners and dates.
- List the initiatives that serve each objective, such as a pricing test, a new feature or a hiring round.
- Give each initiative one owner, a start date and a target end date.
- Flag dependencies between teams.
- Move anything that does not support a pillar to a "not now" list.
Milestone: Every initiative has one owner, dates, and a clear link to a pillar.
Publish and Set the Review Rhythm (Week 6)
Share the roadmap and plan how you will keep it up to date.
- Put the full chain on one visual roadmap: vision, pillars, outcomes, quarterly objectives, initiatives.
- Present it to the whole team and answer questions live.
- Book a short monthly check-in and a longer quarterly review in everyone's calendar.
- Decide who updates the roadmap after each review.
Milestone: The roadmap is published, everyone can find it, and the first quarterly review is on the calendar.
What a Strategy Roadmap Is (and What It Is Not)
A strategy roadmap answers one question: how does today's work connect to where we want to go? It sits above your other plans. A product roadmap shows which features ship and when. A project plan shows the tasks, dates and resources for one project. A strategy roadmap shows why those plans exist and which bets come first.
Keep these layers separate, but keep them linked. Each initiative in a product roadmap or project plan should trace back to a quarterly objective, then to a yearly outcome, then to a pillar. If you cannot draw that line, either the strategy is missing something or the work should not be happening. Here is how the layers fit together.
- Vision: where you want to be in 3 to 5 years. Rarely changes.
- Pillars: the 3 to 5 areas where you must win. Stable for 12 months or more.
- Yearly outcomes: measurable results for the year.
- Quarterly objectives: what must be true in 90 days.
- Initiatives: the projects that get you there, with owners and dates.
How to Write a Vision That Actually Guides Decisions
A useful vision helps people say no. "Be the best company in our market" cannot do that, because nothing fails the test. "Become the default tool for independent accountants in Europe" can. It names a customer, a place and a position. When someone suggests a feature for large enterprises, the vision gives a clear answer.
Test your draft with three questions. Can a new employee repeat it after hearing it once? Does it rule out at least one tempting direction? Will it still make sense in three years? If the answer to any of these is no, rewrite it. Short and specific beats long and inspiring.
How to Turn Yearly Outcomes Into a Quarterly Plan
The jump from a year to a quarter is where many strategies get stuck. A yearly outcome like "Double active customers in the mid-size segment" is too big to act on. Ask what must be true after 90 days for the year to stay on track. Maybe the answer is "Launch a mid-size pricing plan and sign the first customers on it". A team can plan around that.
Use simple key results to make each objective checkable. A good key result is a number or a yes or no fact, such as "Pricing page live by week 6" or "20 sales calls held with mid-size prospects". Then check capacity. If the team cannot deliver every objective, cut some now. That is better than failing quietly at week ten. A quarter with three objectives that ship is better than one with eight that drift.
How to Run the Quarterly Review
The quarterly review keeps the roadmap honest. Plan two to three hours with the people who own pillars and objectives. Follow the same agenda each time so the meeting stays short and useful.
Between reviews, a 30-minute monthly check-in is enough. Look at progress on key results, raise blockers and move dates if needed. Do not rewrite objectives every month. Frequent changes tell the team that the plan does not matter.
- Score each key result from the past quarter: hit, partly hit or missed.
- Note what you learned, especially from the misses.
- Confirm the pillars still hold. Change them only after a major shift, such as a new market or a change in leadership.
- Write the objectives for the next quarter and update the initiatives.
- Publish the updated roadmap the same week.
How to Show a Strategy Roadmap Visually
Different readers need different levels of detail. Leadership wants to see pillars and outcomes. Teams want to see their quarterly objectives and initiatives. A good visual roadmap shows the whole chain on one page, with pillars as rows and quarters as columns. Each initiative sits in its pillar's row, under the quarter where it happens.
Many teams start with a slide in PowerPoint or a page in Notion, and that works for a first draft. What matters is that the roadmap is easy to find, easy to update after each review, and readable in under a minute. Use color to mark pillars and keep the text on each item short. Show milestones clearly so anyone can see what "done" looks like this quarter.
Common mistakes to avoid
- Choosing eight or ten pillars spreads the team too thin. Keep 3 to 5 and move the rest to a "not now" list.
- Writing outcomes as tasks, like "launch a blog", hides the result you want. Write "grow organic sign-ups" and make the blog one initiative.
- Planning all four quarters in full detail locks you into guesses. Detail only the next quarter and keep later quarters as rough themes.
- Giving an initiative to a whole team means nobody owns it. Name one person per initiative.
- Skipping the baseline makes progress impossible to judge. Record today's value before you set any target.
- Publishing the roadmap and never opening it again turns it into decoration. Book the quarterly review before you publish.
Frequently asked questions
What is the difference between a strategy roadmap and a strategic plan?
A strategic plan is usually a written document that explains the analysis, choices and reasoning behind the strategy. A strategy roadmap is the visual version that shows the vision, pillars, outcomes and quarterly work on a timeline. Many teams write the plan once and use the roadmap every week.
How long should a strategy roadmap cover?
A strategy roadmap often covers 12 to 18 months, with full detail only for the next quarter. The vision behind it looks 3 to 5 years ahead. This mix gives direction without pretending you can plan every detail a year in advance.
Do I need OKRs to build a strategy roadmap?
No, but they fit well. OKRs work as the quarterly layer: the objective is what you want, and the key results show whether you got there. If OKRs feel heavy for your team, a simple list of quarterly goals with one metric each does the same job.
How often should I update a strategy roadmap?
Update the quarterly objectives and initiatives at every quarterly review, and adjust dates at monthly check-ins when needed. Change the vision and pillars only after a major event, such as entering a new market or a change in leadership. A stable top and a flexible bottom keep the plan both trusted and realistic.