The Opportunity Backlog

Marty Cagan describes a proposal from Jeff Patton to replace the traditional product roadmap with an "opportunity backlog." The core problem is that roadmap items are often treated as commitments, yet genuine product discovery typically reveals that roughly half of them are not worth building. An opportunity backlog instead holds a prioritized list of problems to explore, separated from any predetermined solution. This framing keeps teams focused on the underlying problem so they can try multiple solutions until one succeeds. The idea matters because it reduces wasted engineering effort and keeps discovery outcome-oriented.

01Key takeaways

• Treat roadmap items as hypotheses to validate, not commitments to build.
• Maintain a prioritized opportunity backlog to guide what discovery teams explore.
• Frame every opportunity by the problem, the target persona, and the desired outcome.
• Keep problems separate from proposed solutions so you can try alternatives when ideas fail.
• Use the product vision and scorecard as the primary sources for new opportunities.
• Discovery's output is a product backlog of validated work for the delivery team.

02Key sections

Problems with the traditional roadmap

Roadmaps imply that every listed item will be built, but discovery with customers and stakeholders usually shows that many items lack value. This creates waste when teams commit to them.

Reframing the roadmap as an opportunity backlog

Patton's suggestion is to maintain a prioritized list of opportunities that discovery teams explore, rather than a list of features to deliver.

The three questions of an opportunity assessment

Each opportunity should be framed by the problem being solved, the target persona, and how success will be measured.

Separating problems from solutions

Roadmaps often name specific features, but initial solution ideas frequently fail while the underlying problem persists, so problems should be kept distinct from proposed fixes.

Inputs and the discovery-to-delivery flow

Opportunities come from the product vision and the product scorecard, and discovery turns the opportunity backlog into a product backlog for delivery teams.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.