The Alternative to Roadmaps

Cagan argues that feature-list roadmaps often tell teams what to build without explaining the underlying problem, producing waste. He proposes replacing them with shared context: a product vision describing the organization's overall aim, plus prioritized business objectives for each team, measured through key results such as OKRs. This preserves the two real needs roadmaps serve, prioritizing high-value work and making date-based commitments, while letting teams choose how to solve problems. The approach shifts focus from output (features shipped) to outcome (business results achieved), which is why it matters for product organizations trying to empower teams.

01Key takeaways

• Describe the problem and desired outcome for each item instead of listing features to build.
• Give each product team prioritized business objectives with measurable key results, such as OKRs.
• Provide a product vision so teams understand how their work contributes to the larger purpose.
• Reserve high-integrity commitments for situations that truly require fixed dates or deliverables.
• Audit how many past roadmap items met their business objectives to test whether your current approach is working.
• Judge teams by outcomes achieved, not output shipped, and expect initial solution approaches to fail sometimes.

02Key sections

Problems with feature roadmaps

Typical roadmaps list features without stating the problems they should solve, so teams build solutions to unclear goals. Cagan uses a PayPal integration example to show how many hidden reasons can sit behind one item.

Two needs roadmaps serve

Roadmaps exist because management wants the highest-value work done first and sometimes needs date-based commitments. Any alternative must meet both needs at least as well.

Context and autonomous teams

Teams need deep context on company direction to work autonomously, a model borrowed from military squads operating under a common intent. Clear intent lets teams find their own solutions.

Vision and business objectives

Cagan recommends a product vision for the whole organization plus prioritized business objectives per team, managed with OKRs. An example is cutting customer onboarding from 30 days to under 3 hours.

Benefits and self-assessment

Autonomy motivates teams, outcomes must be proven by key results, and failed first attempts are expected. Teams can audit past roadmap success rates to see if the change is needed.

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.