666 Roadmap Template
Plan your product vision and strategy over 6 weeks, 6 months, and 6 years.
Trusted by 65M+ users and leading companies
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.
Product Voice Design toolkit
Works best for:
Product Management, Planning
The Product Voice Design toolkit facilitates the development of consistent and impactful product messaging. By defining brand voice attributes, tone guidelines, and messaging principles, this toolkit ensures that product communication resonates with target audiences. With sections for crafting messaging frameworks, storytelling templates, and content guidelines, it empowers product teams to create compelling and cohesive product narratives. This toolkit serves as a valuable resource for enhancing product communication strategies and building strong brand identities.
Epic & Feature Roadmap Planning
Epic & Feature Roadmap Planning template facilitates the breakdown of large-scale initiatives into manageable features and tasks. It helps teams prioritize development efforts based on business impact and strategic objectives. By visualizing the relationship between epics and features, teams can effectively plan releases and ensure alignment with overall project goals and timelines.
T-Chart Template
Works best for:
Ideation, Operations, Strategic Planning
T-Charts can help you compare and contrast two different ideas, group information into different categories, and prove a change through “before” and “after” analysis. T-Charts are visual organizational tools that enable you to compare ideas, so you can evaluate pros and cons, facts and opinions, strengths and weaknesses, or big-picture views versus specific details. Designers and content creators can use T-Charts to turn possibilities into actionable ideas. T-Charts are useful for discussing differences and similarities with your team or clients and can help you to reach a decision together.
Data Flow Diagram Template
Works best for:
Flowcharts, Software Development, Diagrams
Any process can get pretty complex, especially when it has multiple components. Get a better grasp of your process through a data flow diagram (DFD). DFDs create a simple visual representation of all components in the flow of data and requirements in an entire system. They’re most often used by growth teams, data analysts, and product teams, and they’re created with one of three levels of complexity—0, 1, or 2. This template will help you easily build the best DFD for your process.
Simple Project Plan Template
Works best for:
Project Management, Strategic Planning, Project Planning
A simple project is a North Star for your team, helping them answer any big questions about the project. The project plan should describe the nature of the plan, why you’re doing it, how you’ll make it happen, how you’ll carry out each step of the process, and how long each step is projected to take. If you’re a project manager or team lead, use this template to start a simple project plan, which can then be adapted to suit internal team projects or external client partner projects.
Syllabus Template
Works best for:
Education
A Syllabus is a brief guide to your course, including expectations for your students, readings they will complete throughout the course, and a mission statement or course description. The Syllabus outlines any policies your students should follow during the course, rules and regulations that apply to them, and anything else your students should know. A Syllabus is a valuable tool for orienting your students, and it’s important the syllabus be clear and easy to follow. Use the Syllabus template to streamline the process of creating a simple, intuitive syllabus for your course.