Establishing an Outcome-Driven Roadmap
31 October, 2020
Roadmaps frequently turn into runways for features where individual features would populate the roadmap at random. Adding ideas indiscriminately and making time commitments is harmless on multiple levels. Instead of assessing what pieces of work would drive the real outcome that you are trying to achieve as a product team, features will be piled up without being related to any outcome.
The first logical step is to challenge yourself to create a more outcome-driven roadmap. I would start thinking about a roadmap from an outcome perspective as opposed to laying out a number of features in random order and without attaching them to a clear outcome. Typically, you will have two or three key outcomes, precisely defined and easily measurable (for example, increase customers by 20 percent). To achieve these outcomes I would identify opportunities that may drive them. In the end, through a product discovery process, I would come up with ideas that would help achieve those opportunities.
I was inspired by Teresa Torres, a product discovery coach, who created the opportunity solution tree, a visual chart that helps create an outcome-driven roadmap. The tree itself consists of four parts: outcomes, opportunities that have emerged from the research, solutions to target opportunities, experiments to evaluate the solutions, and the riskiest assumptions behind them.
Her approach inspired me to be more intentional during the discovery phase and generate ideas that directly contribute to the outcomes. Before adding any ideas to a roadmap, I would pick a handful and validate them against already defined outcomes.
- Don’t fall into the feature-roadmap trap. Don’t put features on a timeline with only the hope that the result will contribute to the outcomes.
- Start with establishing outcomes you want to achieve and opportunities that will help you achieve those outcomes.
- Mapping them first will provide you with a much clearer picture of choices you should make to drive successful outcomes for your product and not just deliver features that may not result in any value for your product.
Raghavendra Iyer, Head of Engineering at ReachStack, explains how he envisioned a new product and engineering stack that he was trying to roll out for a yet-unknown problem.
Head of Engineering at ReachStack
Matt Pillar, VP of Engineering at OneSignal, shares how he had to abandon a technology investment his team was pursuing that neglected the real customer problems and instead focused on the brilliance of the solution alone.
VP Engineering at OneSignal
Ido Cohen, Head of Product at Permutive, discusses the importance of solving the right problems and how failing to identify them can lead to misuse of resources and lost opportunities.
Head of Product at Permutive
Toby Delamore, Product Manager at Xero, describes how to establish an outcome-driven roadmap by introducing the “opportunity solution tree”.
Product Manager at Xero
Patrick Chen, Lead Product Manager at Next Insurance, recollects how his rich international experience helped him create a better, culturally-adapted product.
Lead PM at Next Insurance
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.