Having Roadmap Conversations That Don't Suck

Roadmap planning used to give me anxiety. Everyone wanted their feature. Nobody wanted to make trade-offs. Every meeting ended in conflict or uncomfortable compromise.

Then I changed how I approached these conversations.

The old way (that sucked)

• Present a draft roadmap
• Watch everyone attack their least-favorite items
• Defend, negotiate, horse-trade
• Leave exhausted with a frankenstein plan

The new way (that works)

Step 1: Align on strategy before tactics

Don't start with "here's what we're building." Start with "here's what winning looks like this quarter/year." If everyone agrees on the destination, debating the path becomes productive.

Step 2: Present trade-offs, not decisions

Instead of "we're building X," say "if we build X, we can't build Y. Here's why I recommend X." This invites input instead of defensiveness.

Step 3: Make the opportunity cost explicit

Every feature you don't build has a business impact. When stakeholders push their priorities, ask: "Which of these should we deprioritize to fit that in?" Force the real conversation.

Step 4: Time-box the debate

"We have 30 minutes to align on Q1 priorities. At the end, I'm documenting the decision." Urgency focuses minds. Open-ended discussions spiral.

Step 5: Document decisions AND dissent

After the meeting, write "We decided X because Y. [Person] disagreed because Z, and we'll revisit if [condition]." This makes people feel heard and creates accountability.

What I've learned

The best roadmap conversations aren't about features—they're about strategy, trade-offs, and trust. If stakeholders trust your judgment and understand your reasoning, they'll support even decisions they disagree with.

If they don't trust you, no process will fix it.