Roadmap

A roadmap is a strategic plan that outlines the vision, direction, priorities, and timeline for a product or project over a defined period. It communicates what will be built and why.

Category: General (also: Software Engineering, Business)

Author: Atomic Glue Technical Team

## Definition

A roadmap is a high-level strategic document that communicates the planned direction and priorities of a product, project, or initiative over time. Unlike a detailed project plan with specific tasks and dates, a roadmap focuses on themes, goals, and major milestones. It answers the "why" and "what" before the "how." Roadmaps come in many forms: product roadmaps (features and enhancements), technology roadmaps (infrastructure and architecture), and business roadmaps (strategic initiatives). A good roadmap is a communication tool first: it aligns stakeholders, sets expectations, and provides a framework for decision-making. It should be updated as new information emerges, not treated as a binding contract.

## Roadmap vs Project Plan

A roadmap and a project plan serve different purposes. A roadmap is strategic, focusing on the big picture: themes, objectives, and time horizons (now, next, later). It is deliberately high-level and flexible. A project plan is tactical: specific tasks, assigned owners, dependencies, and exact dates. Roadmaps are for alignment and communication. Project plans are for execution. Both are necessary. The roadmap keeps the team pointed in the right direction; the project plan ensures they get there efficiently.

## Types of Roadmaps

Common roadmap formats include: * **Theme-Based Roadmaps:** Organize work around customer problems or business outcomes rather than specific features. Example: "Improve onboarding experience" instead of "Build signup wizard v2." * **Time-Based Roadmaps:** Use quarters or months as buckets for major initiatives. Most common for stakeholder communication. * **Now-Next-Later Roadmaps:** A flexible format that avoids committing to specific dates. "Now" is actively being worked on, "Next" is queued, "Later" is future possibilities. * **Outcome-Oriented Roadmaps:** Focus on measurable goals (metrics and OKRs) rather than outputs.

## Roadmap Best Practices

Focus the roadmap on outcomes, not just features. Explain why each item matters. Keep it high-level enough to allow for discovery and change. Update it regularly (monthly or quarterly) as you learn more. Distinguish between committed items (definite) and tentative items (aspirational). Tailor the roadmap for different audiences: executives want timelines and themes, teams want priorities and context. Never treat a roadmap as a delivery guarantee; it is a plan, and plans change.

## Common questions

Q: How far out should a roadmap plan?

A: 3-12 months is typical. Beyond 12 months, specificity becomes unreliable. Use themes and vision statements for longer horizons.

Q: Who owns the roadmap?

A: The Product Owner or Product Manager owns the product roadmap. For project roadmaps, a project manager or program manager typically leads.

Q: Should the roadmap include exact dates?

A: Avoid exact dates for items more than one quarter out. Use time horizons (Q1, Q2) or now-next-later instead of specific release dates.

## Key takeaways

• A roadmap is a strategic communication tool that aligns stakeholders on vision and priorities.
• It differs from a project plan: roadmap = strategy, project plan = execution.
• Use themes and outcomes rather than detailed feature lists.
• Update the roadmap regularly; it is a living document, not a contract.

## Related entries

• [Agile Development](atomicglue.co/glossary/agile-development)
• [Scrum](atomicglue.co/glossary/scrum)
• [Sprint](atomicglue.co/glossary/sprint)

Last updated July 2025. Permalink: atomicglue.co/glossary/roadmap