Lore

Saying No Together

Rather than a PM unilaterally telling a stakeholder no and citing a reason, "saying no together" walks the stakeholder jointly through the cost of delay, opportunity cost, risk, and dependencies of their request. Because the stakeholder is included in reasoning through the trade-offs rather than receiving a verdict, they frequently arrive at the "no" conclusion themselves — making it a shared decision rather than an imposed one.

This is a specific tactic for building Disagree and Commit-style buy-in at the individual-stakeholder level, and depends on Applying Jobs/Pains/Gains Thinking to Stakeholders, Not Just Customers framing to know which trade-offs (cost, risk, dependency) will actually land with that particular stakeholder.

Cost-of-Delay Framework

When a stakeholder pushes an urgent request into an already-committed roadmap, the joint walkthrough works through four factors together, rather than the product person unilaterally declining:

1. Cost of delay — what does waiting cost?
2. Opportunity cost — what else could be done with the same capacity?
3. Risk of delaying vs. switching — what breaks either way?
4. Dependencies — what does this affect or get affected by?

Walking through these together is designed so the stakeholder arrives at the "not now" conclusion themselves, rather than having it imposed on them.

Из тем: Stakeholder Power and Trust