Somewhere in every product org is the belief that if you just get the right people in a room with the right data, alignment will emerge. Sometimes it does. More often, you end up with three stakeholders who read the same research and walked away with three different priorities, all defensible, all incompatible with shipping this quarter.
Waiting for consensus in that situation isn't neutral — it's a decision to let the loudest or most senior voice win by default, dressed up as patience.
What moved the release
Not a bigger meeting. A narrower question: what is the one thing this release has to be true for it to count as a win, for each stakeholder, separately. Once those were written down next to each other, it became obvious that two of the three "must-haves" were actually about sequencing, not scope — they didn't need to happen in this release, they needed a committed date for the next one.
That left one genuine scope conflict, and a genuine scope conflict is a much smaller problem than it looks like inside a meeting where everyone is arguing past each other.
Most roadmap conflicts are sequencing disagreements wearing a scope disagreement's clothes.
The part I'd do differently
I let the disagreement run for two weeks longer than it needed to, because I was treating "get everyone aligned" as the goal instead of "get a decision made that people can live with." Those aren't the same goal, and conflating them is the single most common way I've seen a roadmap stall — not from lack of data, but from an unstated assumption that shipping requires agreement rather than a decision.
It doesn't. It requires a decision, a reason attached to it that the room can hear even if they don't love it, and someone willing to own the call.