Adoption
Part of Customer success plans
Writing success outcomes in the customer's language
Edit a success-plan outcome in the customer's terms, then confirm its people, task, intended change and evidence.
When an outcome is already under consideration for a success plan, write it as a change in the customer's work. Use the customer's terms for the people, task and result, then ask them to correct the sentence. A feature, meeting or activity count may support the outcome, but should not replace it.
Work from the customer's description
Listen for the specific work behind a broad phrase such as “improve efficiency”. A sponsor may describe the aim while a process owner describes where approvals wait. Ask for a recent example: what had to happen, where it slowed down, and what a better result would look like. Check the wording with someone who performs the task and someone accountable for it.
Record the customer's terms accurately, without presenting an unconfirmed paraphrase as a quotation or promise. If stakeholders mean different things by “faster”, keep the disagreement visible until they settle which result the plan will track.
Turn a broad customer aim into a trackable outcome
- Listen for the specific workMove past phrases like “improve efficiency” to the task, people and result the customer means.
- Ask for a recent exampleWhat had to happen, where did it slow down, and what would a better result look like?
- Check with two perspectivesConfirm the wording with someone who performs the task and someone accountable for it.
- Record the customer’s terms accuratelyDo not present an unconfirmed paraphrase as a quotation or promise.
- Keep disagreements visibleIf stakeholders mean different things by “faster”, wait until they settle which result the plan will track.
Edit the sentence for clarity
A working form is: The named team will achieve a specified change in a defined task, checked in a way the customer accepts at an agreed review point. Use it as an editing prompt, not a rigid template. Leave a measure or date open if the customer still needs to establish one.
For a hypothetical approvals product, compare these candidate statements:
| Wording | What needs editing |
|---|---|
| “Drive platform engagement” | Name the customer's work and desired change. |
| “Train all regional managers” | Keep training as a possible action; state the result it is meant to support. |
| “Regional managers complete eligible approvals within the customer's agreed window” | Confirm which managers and approvals count, the window and the evidence. |
The last line is a better draft only if it reflects the customer's priority. Do not insert a target borrowed from another account. Ask where the completion record lives and whether staffing or policy changes could make the comparison misleading.
Candidate outcome wording: what still needs editing
- “Drive platform engagement”Name the customer’s work and desired change.
- “Train all regional managers”Keep training as a possible action; state the result it is meant to support.
- “Regional managers complete eligible approvals within the customer’s agreed window”Confirm which managers and approvals count, the window and the evidence.
Read the wording back
Ask whether this is the change the customer wants to see, who would notice it, and what the sentence leaves out. If the customer would describe success differently, revise it. Record who confirmed the wording and which questions remain open.
Keep the outcome separate from supporting signals. Product records may show eligible work entering or finishing a workflow. The customer may still need to confirm whether the finished work met its operational purpose. Carry that distinction into the plan.
Use the approved sentence when editing later milestones. If the customer's goal changes, revise the outcome explicitly so the plan does not keep serving an old measure.
Read the wording back before finalising
- Ask if this is the change the customer wants to seeRevise it if the customer would describe success differently.
- Ask who would notice itUse that answer to test whether the outcome is visible in the customer’s work.
- Ask what the sentence leaves outRecord open questions and unknowns rather than implying they are settled.
- Record who confirmed the wordingKeep the confirmed wording separate from supporting signals.
- Keep outcome separate from supporting signalsProduct records may show work entering or finishing; the customer confirms whether it met its operational purpose.
- Revise explicitly if the customer’s goal changesDo not keep serving an old measure.
