🗺️Roadmap Prioritization
The hardest skill in product. Not the framework — the conversation that gets your team to commit to a hard choice.
Roadmap conversations are where strategy meets reality. PMs who can run these well drive coherent teams; those who can't preside over feature factories.
A great roadmap process aligns the team around 2-5 bets per quarter, ladders to strategy, and explicitly names what won't be done. The process matters more than the framework: structured stakeholder input, ruthless filtering, and a public commitment.
The quarterly roadmap process (8 weeks before quarter start)
Week -8: Strategic context. What does the strategy say we should prioritize this quarter? Refresh the strategy if needed.
Week -7 to -5: Generate candidates. Open input from PMs, sales, support, customers. Don't filter yet. Aim for 30-50 candidate bets.
Week -4: First filter. Apply strategic fit, impact sizing, effort estimate. Get to 10-15 candidates.
Week -3: Trade-off conversations. With engineering, design, leadership. Surface the trade-offs explicitly. Pick 5-8.
Week -2: Commit. Decide. Get exec sign-off. Communicate broadly.
Week -1: Operationalize. Sprint plans, dependencies, kickoffs.
Week 0: Execute.
The principles
- 2-5 bets per quarter per team. More than that, you're not prioritizing.
- Each bet has an outcome metric. Not 'ship X' but 'move Y to Z.'
- The 'not now' list is published. People who asked for things see explicitly that they were considered and deferred.
- Strategy ladders are explicit. Each bet shows the strategic rationale.
The trade-off conversation
The crux of the whole process. Pattern:
PM: "Here are 10 candidates. We have capacity for 5. Here's how I'd cut: keep A, B, C, D, E; defer F, G, H, I, J because [reason]. Pushback?"
This is sharper than the typical "let's discuss." It anchors the conversation on your recommendation and forces stakeholders to argue against specific cuts.
Common pushback patterns:
- "F is critical because of [deal/customer]." → 'understand the constraint, but here's why E ranks higher; happy to revisit if [condition].'
- "Why isn't [pet project] on the list?" → "it didn't make the strategic-fit cut. Here's the rationale."
- "We need both A and F." → "if we add F, what comes off? The team can't do both."
The Andy Grove move
Andy Grove: when you say yes to one thing, you're saying no to everything else you could have done. Force the team to confront this — make the 'no' explicit, in writing, with reasoning. The team's discipline depends on it.
Reframing the conversation upward
When sales/exec asks pile up beyond capacity, don't argue feature-by-feature. Reframe: "Let's jointly own the team's quarterly prioritization. Here's the strategic theme, here's the bandwidth. You pick 5 bets with me." Once stakeholders own the prioritization with you, the individual 'nos' stop being personal.
Real-world examples
Atlassian's product teams plan around quarterly 'missions' — specific outcomes each team commits to. The mission framing makes 'not now' decisions easier because the comparison isn't feature-vs-feature, it's mission-vs-mission.
Go deeper — recommended reading
Interview questions (1)
Q1Walk me through how you'd run quarterly planning for a 3-team product org.leadershipsenior▼
Eight-week process.
Weeks -8 to -7: refresh strategy with VPs and CPO. Each team understands what strategic themes they should anchor on.
Weeks -7 to -5: candidate generation. Each team's PM solicits input from sales, support, customers, engineers. Goal: 20-30 candidates per team.
Week -4: first filter. Strategic fit, impact sizing, effort estimate. Each team cuts to 8-10.
Week -3: cross-team alignment. Surface dependencies, shared resources, conflicts. Trade-offs negotiated.
Week -2: each team commits to 3-5 bets. Each bet has a measurable outcome and a strategic rationale. CPO signs off.
Week -1: communicate broadly. Publish the 'not now' list along with the roadmap so stakeholders see what was considered.
Week 0: execute.
The discipline that makes it work: making the trade-offs visible. Most planning failures happen when 'not now' decisions are implicit. Explicit 'not now' lists eliminate 80% of the political friction.