Adoption
Part of Customer success for B2B products
Defining customer outcomes before building a success programme
Turn a B2B customer's goal into a checkable outcome before choosing success activities, dashboards or service coverage.
Define the result the customer wants before deciding contact frequency, which playbook to run or what to put on a dashboard. An outcome is a result in the customer's work or operations that the customer can recognise and assess. Product use and vendor activity may help produce that result, but neither is the result itself.
Ask what will be different
Start with the people who own and do the work. Ask what prompted the purchase, where the current process falls short, and what success would let them do or avoid. Seek a recent example. A sponsor may give a broad aim while users name the step that slows them down; both views matter.
Draft a short candidate statement in the customer's language: who needs to do what, what should improve and why it matters. Check it with the customer. If their team cannot recognise the statement, revise it before building a programme around it.
For a hypothetical approvals product, the candidate outcome might be that regional managers complete required approvals within the customer's own target window. Creating accounts and attending training are possible steps towards that result. They do not show that approvals now happen on time.
Make the outcome checkable
For each candidate, record five things:
- Starting position:what happens now, using a period and population the customer accepts.
- Success condition:the change it would regard as meaningful. Let the customer set or approve the target rather than borrowing a generic benchmark.
- Evidence:the record or observation that can show whether the condition was met, and who can access it.
- Time horizon:when the work is expected to occur often enough for a fair check.
- Owners:the customer person who confirms the result and the provider person who coordinates the response.
If the outcome cannot yet be measured, say what must be learned. A short interview or manual sample may be more honest than a dashboard built on an unsuitable proxy.
Check whether the definition changes over time: a new approval policy, for example, may alter which cases count. Record both definitions before comparing periods.
Key Elements of a Checkable Customer Outcome
- Starting Position
- Current approval completion rate and timeframe used by the customer.
- Success Condition
- Target window for approval completion set by the customer.
- Evidence
- Approval logs or system records accessible to the customer’s team.
- Owners
- Customer’s process owner and provider’s success manager.
Separate the result from its signals
A useful sequence is outcome → required workflow → observable signals → possible intervention.
In the approvals example, completed approvals within the agreed window are closer to the outcome. Eligible managers submitting requests may be an early signal. Invitations sent and training sessions held describe provider activity. These measures can all be useful, but they answer different questions.
Ask what else could explain a change in the result. A staffing change or a quieter period may affect completion time. If the evidence shows only that the product was used while the customer's wider result is unknown, report that limit. Do not claim the product caused the whole improvement from a before-and-after comparison alone.
Outcome vs. Signals: What to Measure
- Actual Outcome
- Regional managers complete required approvals within the customer’s target window.
- Observable Signal
- Managers submit approval requests on time.
- Provider Activity
- Training sessions held or invitations sent.
Use the definition to design the programme
Once the customer confirms the outcome, choose interactions that could help advance it. A complex cross-team dependency may justify a named coordinator and a joint review. A standard workflow may need clear guidance and a route to help when a signal shows trouble. Define what would prompt a change of approach.
Keep the initial outcome set small enough to inspect. Record disagreements and unknowns. The result is a brief, customer-confirmed definition to inform later onboarding milestones, success plans and business reviews.
