Goals-based Roadmap
Many companies keep rolling out roadmaps just for the sake of it. In most cases, these roadmaps turn the teams (and the organization) into incoherent feature-building factories with no goals, no strategy and no eye on contributing towards the organization’s long-term vision.
With feature-based roadmap templates, no matter how religiously you follow your strategy, it is only a matter of time before you succumb to the myriad feature requests that will be thrown at you from all directions; whether it be from a sales person coming from a client demo where the client was not willing to buy our product unless it supported an Active Directory integration, or directly from the C-level executive who spent the weekend trying out competitor products and came across a list of feature ideas to copy. Having lost sight of the bigger picture in order to appease the executives, your roadmap would soon turn into an incoherent feature factory, with very little alignment with the strategy.With feature-based roadmaps, roadmaps can also often become contractual obligations with the stakeholders, rather than a view of progress your product is expected to make towards achieving its strategic goals.
Goals-based Roadmaps
Goals-based roadmaps shift the focus of the team from shipping features to delivering value and achieving product goals. While the features are still part of the roadmap template, the focus is always on meeting Goals set for each release.
How to use Goals-based Roadmap board?
Before you start building your roadmap, it is imperative that you and your team fully understand and are aligned on the Product's Vision and Strategy. By having both the Product Vision and the Strategy as part of the Roadmap template can serve two purposes:
The teams understand that they can't miss this step before they start creating a roadmap.
During the monthly/quarterly roadmap review sessions, the Vision and Strategy sections can also serve as a referesher for the team.
Step 1: Fill in your product vision
In the first section, add your product's vision here, which is the change you want to bring into the world through your product. We have used the Vision format from the Product Strategy Canvas by Melissa Perry. Feel free to plug in anyother format you prefer.
Step 2: Fill in your product strategy
In the second section, add your product's strategy here, which is what you need to do to accomplish your vision. Here, we have adapted Melissa Perry's Product Strategy Canvas format.
Step 3: Set the Goals
When you get into the roadmap section, the first step is to set the goals you want to achieve as part of your Product Strategy. Breakdown the goals into a prioritized set of releases over a period of time. You can use this board to create a roadmap from 3 months to 3 years.Each release can have one or more goals. As a general rule, we don't recommend having more than 3 goals per release as that can end up diverting the team's focus.
Step 4: Identify the Themes
Once you have defined your goals, you need to identify the themes for your roadmap features that will allow you to achieve your goals. These themes will often come from your customer research exercises and will be directly linked with your goals.
Step 5: List down the metrics of success
For each release, you should identify the metrics that will determine whether your release was successful in meeting its goal or not. These metrics need to be high-level and should be independent of any features that will be shipped as part of each release.
Step 6: Review your Goals, Themes & Metrics
Before you move ahead, it is important to review your Goals & Themes with other stakeholders and get their buy-in.
Step 7: Add features (Not to be shared outside the product and development team)
With everything else jotted down, now is the time to think about the low-level details pertaining to identifying features that will help you in achieving your release goals.We have kept this item towards the end (and even after the stakeholders review) because in today’s day and age, premature convergence on a solution (in the form of features), way before time, is very risky. Including such low-level details into your roadmap leaves very little room for your team to innovate and improvise. In most cases, they feel less valued because they are being spoon-fed and are bound to lose motivation over time.
Final Step: Adapt
You can continue to adapt your roadmap on a regular basis based on new information received from your customers. In most cases, you would only need to change the list of features you put in as part of each release, with the Goals and themes requiring very minor updates.
Credits
Product Strategy Canvyas by Melissa Perry
The Go Roadmap template by Roman Pichler
This template was created by Sami Rehman.
Get started with this template right now.
Flowchart Template
Works best for:
Flowcharts, Mapping, Diagrams
Trying to explain a process or workflow to your team — or just wrap your head around it yourself? Sometimes the best way is to see it, and that’s when you create a flowchart. Using common shapes (generally just ovals, rectangles, diamonds, and arrows), a flowchart shows you the direction a process or workflow goes and the order of steps. Beyond giving you a clear understanding, you’ll also be able to see potential flaws and bottlenecks, which helps you refine and improve your process and create a better product more efficiently.
Action Priority Matrix Template
Works best for:
Mapping
You and your teammates probably have more ideas than resources, which can make it difficult to prioritize tasks. Use an Action Priority Matrix to help choose the order in which you will work on your tasks, allowing you to save time and money and avoid getting bogged down in unnecessary work. An Action Priority Matrix is a simple diagram that allows you to score tasks based on their impact and the effort needed to complete them. You use your scores to plot each task in one of four quadrants: quick wins, major projects, fill-ins, and thankless tasks.
Customer Touchpoint Map Template
Works best for:
Desk Research, Product Management, Mapping
To attract and keep loyal customers, you have to truly start to understand them—their pain point, wants, and needs. A customer touchpoint map helps you gain that understanding by visualizing the path your customers follow, from signing up for a service, to using your site, to buying your product. And because no two customers are exactly alike, a CJM lets you plot out multiple pathways through your product. Soon you’ll be able to anticipate those pathways and satisfy your customers at every step.
Project Proposal Template
Works best for:
Project Management, Documentation, Project Planning
For any type of project, the Project Proposal template can be a crucial step toward clarifying the context, goals, and scope of a project to get stakeholder buy-in. A project proposal outlines what you want to accomplish, your goals, and how you plan to achieve them. Generally, a project proposal gives the reader some context on the project, explains why it is important, and lists the actions that you will take to complete it. Project proposals have myriad uses. Often, businesses use project proposals to get external buy-in from a donor or outside stakeholder. But many companies draw up project proposals for internal buy-in too.
Agile Transition Plan Template
Works best for:
Agile Methodology, Agile Workflows
An Agile transformation roadmap can help you, your team, and your organization transition from rigid compliance-heavy methods to the more flexible Agile way of doing things incrementally. From requirements to integrations to security, you can map out your organization's moving parts as “swim lanes” that you can then update regularly. Use your roadmap as a way to tell the story of how you see your product growing over a period of time. Get buy-in without overselling and keep your roadmap simple, viable and measurable. By using an Agile transformation roadmap, you can avoid getting bogged down in details and instead invest in big-picture strategic thinking.
Work Plan Template
Works best for:
Mapping, Project Planning
A work plan is essentially a roadmap for a project. It articulates the steps you must take to achieve the desired goal, sets demonstrable objectives, and establishes measurable deliverables. An effective work plan guides you throughout the project lifecycle, allowing you to realize an outcome by collaborating with your team. Although work plans vary, they generally contain four core components: goals, strategy, tactics, and deliverables.