Establishing an Outcome-Driven Roadmap
31 October, 2020

Product Manager at Xero
Problem
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.
Actions taken
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.
Lessons learned
- 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.
Discover Plato
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Related stories
24 May
Jord Sips, Senior Product Manager at Mews, shares his expertise on a common challenge for product managers – finding root causes and solutions.

Jord Sips
Senior Product Manager at Mews
16 May
Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Snehal Shaha
Senior EPM/TPM at Apple Inc.
9 May
Pavel Safarik, Head of Product at ROI Hunter, shares his insights on how to deal with disagreements about prioritization when building a product.

Pavel Safarik
Head of Product at ROI Hunter
25 April
Matias Pizarro, CTO and VP of Residents at ComunidadFeliz, recalls a time in his early career when he took a technology risk that had wide-ranging benefits to his product's user experience.

Matias Pizarro
CTO and VP of Residents at ComunidadFeliz
20 April
Waldo Vanderhaeghen, VP of Product at 3YOURMIND, details an experience in product discovery, analyzing user research, and testing.

Waldo Vanderhaeghen
VP Product at 3YOURMIND
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.
