Multiple Stakeholders, No Proposal Decision: Build a Decision Map

Understand the situation before responding

Ask your contact how the decision is made rather than guessing the organisation chart. A person who likes the proposal may be an evaluator, user or sponsor without spending authority. Record each role only when confirmed. Identify where stakeholders have different priorities, such as implementation effort versus financial return. Avoid treating disagreement as politics you should manipulate or bypass; it may expose a legitimate weakness in the proposed work.

An example message to adapt

To make sure the proposal answers the right questions, who will use the work, who assesses the approach and who approves the spend? Is there one person coordinating those views? I can prepare focused clarifications, but it would help to know which decision each stakeholder needs to make.

Illustrative teaching example. Replace the prompts with buyer-confirmed facts; this is not a client conversation, claimed result or message to send automatically.

Prepare a useful next action

Create a small decision map containing role, question, evidence needed and next action. Share it with your contact for correction where appropriate. Offer a joint discussion if the relevant people welcome one. Do not add stakeholders to a confidential thread without permission. Where requirements conflict, bring the trade-off into the scope discussion rather than promising each person a different version of the outcome.

Record the decision and its limits

Agree who consolidates feedback and how a final decision will be recorded. If no one owns that coordination, make the gap explicit and pause speculative revisions. Do not count attendance at a meeting as approval. Once a stakeholder introduces a new condition, update the dependency list and ask whether the original timeline remains realistic. Progress means a resolved question or agreed action, not simply more people receiving the document.