666 Roadmap Template
Plan your product vision and strategy over 6 weeks, 6 months, and 6 years.
About the 666 Roadmap Template
The 666 roadmap works across three timelines: one for your long-term vision, one that lets you plan (with some flexibility), and a short-term fixed plan.
This roadmap was created by Paul Adams, a VP of Product at Intercom. He believed that common suggested timelines such as two years or 18 months were either too shortsighted or too far into the future to manage unpredictability or understand the market.
Keep reading to learn more about 666 roadmaps.
What is a 666 roadmap
A 666 roadmap helps product managers plan and decide on what they’d like to build by encouraging them to focus on three key timelines:
The next six years: What will the world look like six years from now? And how will that affect today’s market trends? These questions give your team an opportunity to do some industry forecasting and future thinking, thus informing your product build.
The next six months: Think of this as a rolling timeline you can update every quarter. Over six months, you can build 50-75% of your product. That leaves 25% to chance, perhaps impacted by things you can’t predict. Progress is possible, but circumstances can change. Adapt accordingly.
The next six weeks: These are your most concrete, immediate priorities – a rolling timeline that gets updated every two weeks. Your team is usually across all the details here. They should be familiar with the design work and what’s committed to being built.
The 666 roadmap method's success hinges on product managers and their teams balancing a project’s vision and significant milestones with its day-to-day work.
When to use 666 roadmaps
These roadmaps help product managers and their teams practically plan while dealing with the realities of week-to-week workloads.
You may also need to present a 666 roadmap to your leadership or agile development team. Buy-in presentations are excellent opportunities to show everyone your confidence in balancing customer needs with your company's business objectives.
Remember that roadmaps shouldn't exist in isolation. Instead, they should back up other work your product team may be doing. You can connect roadmap goals to team progress by breaking down initiatives into epics in your product backlog. Break down these epics into requirements and user stories.
Product managers can pitch the 666 roadmap approach to their teams and any external stakeholders as an alternative to thinking in only two timelines: the twenty-year stretch and the six-month container.
Create your own 666 roadmap
Making your own 666 roadmaps is easy. Miro’s whiteboard tool is the perfect canvas to create and share them. Get started by selecting the 666 Roadmap Template, then take the following steps to make one of your own.
Record your goals for the next six years. These are your long-term product vision goals. They can be updated every two weeks to keep your goals accurate and a shared source of truth for your entire team.
Record your goals for the next six months. These are your quarterly ambitions, such as implementing a new feature. Include only as much detail as your stakeholders and team need for each column. Ideally, they should be confident in consulting the roadmap independently to understand the status of current work and long-term goals, rather than asking you for updates.
Record your goals for the next six weeks. These are your easily definable daily team goals, such quality assurance or implementing a functional customization. No more than six goals are recommended per timeline, to keep teams focused between long- and short-term ambitions.
Review and adjust the details for each timeline as needed. Make sure everyone can access the roadmap by updating your board’s Share settings as needed. Staying connected with teammates and stakeholders at all levels by automating updates (such as notifications of new changes) or regularly scheduled check-ins helps keep everyone aligned and motivated.
Get started with this template right now.
Advanced Project Gantt Chart Template
Works best for:
Gantt Chart, Planning
Manage complex projects with ease using the Advance Project Gantt Chart Template. This tool helps you schedule tasks, set deadlines, and track progress in a visual format. Ensure that all team members are aligned and that your project stays on track. Ideal for project managers handling multifaceted projects with multiple dependencies and timelines.
Technology Product Canvas Template
Works best for:
Product Management, Meetings
Originally created by Prem Sundaram, the Technology Product Canvas allows product and engineering teams to achieve alignment about their shared roadmap. The canvas combines agile methodologies with UX principles to help validate product solutions. Each team states and visualizes both product and technology goals, then discusses each stage of the roadmap explicitly. This exercise ensures the teams are in sync and everyone leaves with clear expectations and direction. By going through the process of creating a Technology Product Canvas, you can start managing alignment between the teams -- in under an hour.
The Product Storyboard
Works best for:
Product Management, Planning
The Product Storyboard template enables product managers to visualize product experiences and user journeys. By mapping out key touchpoints, interactions, and scenarios, this template helps teams understand user needs and pain points. With sections for defining user personas, storyboarding user flows, and capturing feedback, it supports iterative product design and validation. This template serves as a storytelling tool for communicating product visions and guiding product development efforts towards delivering exceptional user experiences.
Timeline Template
Works best for:
Project Management, Flowcharts, Project Planning
A timeline displays a chronological order of important dates, and scheduled events. Timelines help product managers, project managers, and team members tell visual stories about progress and obstacles. Timelines enable teams to see at a glance what happened before, what progress is happening now, and what needs tackling in the future. Projects or products with specific purpose or deliverables should be based on a timeline to be successful. Use the timeline as a shared reference for start dates, end dates, and milestones.
UML Sequence Deployment Pipeline Template
Works best for:
UML
The UML Sequence Deployment Pipeline Template in Miro visually maps the sequence of steps in an automated deployment pipeline, helping teams in software development and deployment. It helps identify bottlenecks, standardizes the deployment process, and facilitates new member onboarding for continuous improvement.
DevOps Roadmap Template
Works best for:
Documentation, Product Management, Software Development
DevOps teams are constantly creating code, iterating, and pushing it live. Against this backdrop of continuous development, it can be hard to stay abreast of your projects. Use this DevOps Roadmap template to get a granular view of the product development process and how it fits into your organization's product strategy. The DevOps Roadmap lays out the development and operations initiatives you have planned in the short term, including milestones and dependencies. This easy-to-use format is easily digestible for audiences such as product, development, and IT ops.