Build support without overselling
Adapt a proposal to stakeholder concerns without changing its facts.
You propose a shared customer record. Sales worries about admin time; support worries about missing handover details. Both teams need the same facts, but not the same explanation.
1 · Notice the conversation
Stakeholder: Sales will not fill in another form.
You: Where would this duplicate work you already do? If we can reuse the existing record, we may only need to add the handover details that are missing.
Stakeholder: Support wants every detail included.
You: Which missing details currently prevent you from acting? Let’s make those required and leave background notes optional.
Stakeholder: Can you promise this will save everyone time?
You: That is the hypothesis. The pilot should measure both entry time and the follow-up questions it prevents.
2 · Understand what each phrase does
Make the recommendation
Put the decision where the listener can find it.
The aim is to reduce repeated customer questions during handover.
Use the move when it serves this situation. This is not a phrase that must appear in every answer.Explain the consequence
Show what the proposal changes for people or work.
For sales, we should keep the required fields short enough to complete during the normal workflow.
Use the move when it serves this situation. This is not a phrase that must appear in every answer.Define the next move
Specify an action, condition or question that moves the discussion forward.
For support, the record needs to show the customer’s request, the promise made and the next owner.
Use the move when it serves this situation. This is not a phrase that must appear in every answer.3 · Rehearse, then change the details
The aim is to reduce repeated customer questions during handover.
For sales, we should keep the required fields short enough to complete during the normal workflow.
For support, the record needs to show the customer’s request, the promise made and the next owner.
Let’s test those fields with both teams before deciding on a wider rollout.
Keep the purpose; change the person, document or time. A simple, accurate sentence is enough.
4 · Respond to your colleague
Sales will not fill in another form.
Explore the workflow cost.
See one possible reply
Where would this duplicate work you already do? If we can reuse the existing record, we may only need to add the handover details that are missing.
Support wants every detail included.
Distinguish essential information from helpful extras.
See one possible reply
Which missing details currently prevent you from acting? Let’s make those required and leave background notes optional.
Can you promise this will save everyone time?
Avoid a benefit claim not yet tested.
See one possible reply
That is the hypothesis. The pilot should measure both entry time and the follow-up questions it prevents.
5 · Try a different situation
Finance supports a new purchase process while engineers fear slower approvals. Explain the shared aim, identify the necessary controls and propose a bounded test of approval time.
What do you recommend, and what should we decide next?
Use the new facts. State the consequence or trade-off and one next action.
- I ask about the stakeholder’s actual concern.
- I keep the factual claim consistent across audiences.
- I propose evidence that can test the expected benefit.
6 · Recall without the model tomorrow
Adapt a proposal to stakeholder concerns without changing its facts.