Present stakeholder priority conflicts as forced binary…
When priority conflicts arise with stakeholders, present the tradeoff as a forced binary choice with visible costs for each option rather than silently absorbing both demands or refusing without explanation.
When This Fires
- When two or more stakeholders need conflicting things from the same resource (your time, your team, your budget)
- When the instinct is to "make it work" by absorbing the conflict personally
- When stakeholders don't realize their requests conflict because you've been silently managing the collision
- Complements Surface trade-offs with forced-choice (forced-choice formula) with the stakeholder-specific presentation format
Common Failure Mode
Silent absorption that eventually fails: you try to do both, work excessive hours, produce lower quality on both, and eventually miss one deadline. The stakeholder whose deadline was missed is angry: "Why didn't you tell me there was a conflict?" You didn't tell them because absorbing felt easier than surfacing — until it wasn't.
The Protocol
(1) When stakeholder priorities conflict, prepare the trade-off presentation: Option A: deliver [stakeholder 1's priority] by [date]. Cost: [stakeholder 2's priority] is delayed by [amount]. Option B: deliver [stakeholder 2's priority] by [date]. Cost: [stakeholder 1's priority] is delayed by [amount]. (2) Present to the relevant decision-maker (or both stakeholders if they're peers). (3) Let them choose. The trade-off is theirs to resolve — they have the organizational context to make the priority call, you don't. (4) If they say "do both" → escalate the constraint: "Here's what 'both' costs: [quality reduction / timeline extension / additional resources needed]. Which cost is acceptable?" (5) Document the decision. You presented the trade-off; they made the call. Accountability is shared.