How do I write a proposal when different stakeholders define success differently?

Start with an outcome map, not a blended mission statement. For each stakeholder, note their desired outcome, how they would recognize progress, and any important constraint. Use their stated priorities where possible; label your interpretations as unconfirmed.

For a hypothetical project to improve an internal request process, the map might look like this:

• Requesters: clearer answers sooner; progress might mean fewer unclear handoffs; keep the process easy to use.
• Operations lead: more predictable workload; progress might mean fewer urgent interruptions; avoid adding unplanned work.
• Finance lead: controlled costs; progress might mean staying within an agreed limit; avoid ongoing expense.

These are placeholders, not assumptions to make about your own stakeholders. Replace them with what people actually say. Then mark each outcome as shared, compatible, competing, or unknown. Clear answers and predictable handling may fit together; faster service and tight cost limits may require a choice about scope or resources.

Compare the conditions for success, not just the words people use. Two stakeholders may both want “better efficiency,” while one means fewer steps for requesters and the other means less staff time per request. Those aims could align, but the phrase alone doesn’t establish that.

Ask each person: “What would need to be true for you to call this successful?” and “What would you not want us to sacrifice?” Then classify the answers:

• Shared: The desired result and measure are substantially the same.
• Compatible: Different benefits can coexist, though they may need balancing.
• Competing: Improving one outcome may make another harder, or priorities differ.
• Unknown: You don’t have enough information to classify the goal.

Keep unknowns visible rather than filling gaps with assumptions. If stakeholders disagree about a measure or a non-negotiable constraint, record both views and identify the decision still needed.

Compare meaningful alternatives if the choice is genuinely open. For each option, describe the intended benefit, main cost or limitation, whose outcomes it serves best, and what remains uncertain. Don’t call an option a win for everyone if it favors one priority.

You could use a section like this:

Stakeholder outcomes and tradeoffs

“Requesters have emphasized clear responses and fewer handoffs; the operations lead has emphasized predictable workload; finance has asked that spending stay within [agreed limit]. These priorities overlap around a more dependable process, but the proposed scope may require a choice between [faster service] and [lower operating cost].

“Our recommendation is [option], because it prioritizes [named outcome or stakeholder need] while aiming to preserve [other outcome]. Its main tradeoff is [specific cost, delay, reduced scope, or constraint]. [Alternative] would better serve [different priority], but would mean [consequence]. The decision-maker is asked to choose [specific unresolved choice]. We do not assume that all stakeholders agree.”

Replace bracketed text with verified details. Present predicted benefits as expectations, not guarantees, and name a decision-maker only if that role is established.

Check that the proposal separates what people said from what you inferred. Where practical, invite stakeholders to correct the relevant part of the map; label unconfirmed interpretations as provisional. Make sure the recommendation names the priority it favors, the tradeoffs affected, and the decision still needed.

Don’t treat silence as agreement. If an important interpretation is unconfirmed, say so and explain whether the recommendation depends on it. If the decision-maker is unknown, state the decision required without assigning authority by assumption. The proposal should make the proposed path and unresolved choice visible, rather than hiding disagreement behind shared-sounding language.