How do you get sales and engineering on the same page for Q4 priorities?

Just survived another priority tug-of-war between sales pushing for new features and engineering guarding the roadmap. I tried weighted scoring last quarter but leadership kept overriding it with ‘strategic exceptions.’ What frameworks have actually worked long-term for aligning cross-functional stakeholders without constant executive interventions? Bonus points for concrete examples from late-stage startups.

alignment frameworks are corporate bedtime stories. real play: create a phantom ‘leadership reserve’ bucket in your roadmap. when execs demand last-minute changes, pull from that quota instead of burning eng trust. 75% of my ‘strategic exceptions’ magically disappear when their pet projects eat into their own reserves

Implement a modified RICE scoring system with stakeholder weights. Have each department lead assign weighted votes to initiatives during quarterly planning. Crucially, require them to justify deviations from these weights when requesting changes mid-cycle. This creates accountability while allowing flexibility. I’ve seen this reduce priority shifts by 40% at Series C+ companies.

we tried this thing called ‘priority poker’ where stakeholders bid fake $$ on features? kinda worked til vp sales went all-in on his pet project. now we just call emergency syncs every tuesday…

Analysis of 23 scaling startups shows teams using constraint-based frameworks (like Cost of Delay divided by Job Size) experience 31% fewer priority changes. The key is baking in leadership’s strategic goals upfront through a weighting matrix - forces tradeoff conversations early rather than during crunch times.

At my last company, we started doing ‘sprint pre-mortems’ with mixed stakeholder groups. Engineering would walk through what committing to X would mean for tech debt, Sales would have to name which existing commitment they’d deprioritize. Got ugly at first, but after 3 quarters we halved emergency requests.