Key Objectives

What are the core objectives driving this initiative?

Increase market share by 15% in the enterprise segment over the next 18 months.
Reduce customer churn to below 5% annually through improved user experience and support.
Launch three new product lines to diversify our revenue streams by Q4 next year.
Long-Term Goals

What major goals need to be accomplished over the next 1–3 years?

Redesign and re-platform our flagship product to a cloud-native architecture by Q3 next year.
Establish partnerships with three leading firms to co-develop new solutions.
Double the size of our engineering team through strategic hiring and acquisitions by 2025.
Short-Term Goals

What are the key deliverables to accomplish in the next 3–6 months?

Conduct market research and customer interviews to validate new product concepts.
Secure executive sponsorship and allocate budget for the cloud migration project.
Identify and onboard two senior engineering managers to lead the team expansion.
Milestones

What are the major checkpoints or accomplishments along the way?

Successful pilot launch of the new cloud platform with 3 key customers.
Establish a joint go-to-market strategy with one new partnership.
Migrate 50% of data workloads to the new cloud data platform.

What is a Strategic Roadmap Planning Retrospective?

Strategic Roadmap Planning is a session where your team turns the reasons behind an initiative into a plan. You start with the core objectives, break them into goals for the next few years and the next few months, then mark the milestones that will tell you you're on track. The board has four columns, moving from the big picture down to checkpoints. Key Objectives captures the why: the outcomes the initiative exists to deliver. Long-Term Goals covers the next 1–3 years. Short-Term Goals holds the deliverables for the next 3–6 months. Milestones marks the checkpoints along the way, such as a pilot launch or a migration that's half done. Bringing every function into the room surfaces roadblocks and dependencies early, while there's still time to plan around them, and it means the people doing the work have agreed to the timeline. Use it to kick off a major initiative, at the start of an annual or quarterly planning cycle, or when a change in the business means your current priorities need another look.

Strategic Roadmap Planning format

Key Objectives

What are the core objectives driving this initiative?

Key objectives are the purpose of the roadmap and the outcomes you want from it. Make them specific and measurable, and tie them to the organization's wider priorities. Spend time on the why until everyone can state it the same way.

Long-Term Goals

What major goals need to be accomplished over the next 1–3 years?

Long-term goals break the objectives into big pieces of work that span 1–3 years. Encourage ambition, but check each goal against the people and budget you actually have.

Short-Term Goals

What are the key deliverables to accomplish in the next 3–6 months?

Short-term goals are the steps that build toward the long-term goals. Each one should be specific, have a date and be achievable within 3–6 months. If a goal doesn't clearly feed a long-term goal, ask why it's on the list.

Milestones

What are the major checkpoints or accomplishments along the way?

Milestones are the checkpoints that show progress. They tell you when to celebrate and when to change course. Pick ones you can measure and that line up with the goals above.

When to use this retrospective

  • When kicking off a new planning cycle or a major initiative that needs several functions to agree.
  • At the start of a large, complex project, to map out a shared roadmap and how you'll measure success.
  • When a change in the business means your priorities need another look.
  • As part of annual or quarterly planning, to agree on the roadmap ahead.

Suggested icebreaker questions

  • If you could pick one superpower to help achieve our roadmap goals, what would it be?
  • What's a past project you're proud of that needed careful planning?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Invite someone from every function the roadmap depends on, and get their agreement early.
  • Lay the roadmap out visually so dependencies and milestones are easy to see.
  • Keep timelines realistic. A roadmap that slips in the first month loses the team's trust.
  • Book regular checkpoints to review progress, adjust and celebrate milestones.
  • Check that every goal is specific, measurable and traces back to a key objective.
  • List the main risks and dependencies up front, with a plan for each.

Frequently asked questions

What is a Strategic Roadmap Planning session?
It's a planning exercise where your team agrees on the key objectives for an initiative, sets long-term and short-term goals, and marks the milestones that show progress.
What columns does the Strategic Roadmap Planning template use?
Four: Key Objectives, Long-Term Goals (1–3 years), Short-Term Goals (3–6 months) and Milestones. They move from the big-picture why down to concrete checkpoints.
When should you run Strategic Roadmap Planning?
Run it when you kick off a major initiative or large project, when a business change means priorities need another look, or as part of annual or quarterly planning.
Who should be in the room?
The people who own the objectives and someone from each function the roadmap depends on. Leaving a function out is the quickest way to miss a dependency.
How is a roadmap planning session different from a retrospective?
A retrospective looks back at work you've finished. Roadmap planning looks forward and ends with goals and milestones. Many teams run a retro first, then use what they learned here.
Ready to run this retrospective?Try this retrospective live