Customer adoption management

Customer adoption management is the ongoing work of helping the intended people use a product for the tasks that matter to their organisation. After the first useful use, agree which workflow should continue, check whether it runs when needed and address what prevents it. A login alone cannot establish useful adoption.

Define adoption for the account

Start with the customer's confirmed goal. Which team needs to do what, and how often does that work arise? Identify the product workflow that supports it. This keeps a busy but irrelevant feature from outweighing a quiet, essential one.

For a hypothetical approvals product, an operations team might want regional managers to complete eligible approvals through an agreed route. The adoption question is whether those managers complete that task when it arises. Invitations, training attendance and sign-ins may help explain progress, but they answer different questions.

Record the intended users, the task, what counts as completion, the expected task cycle and who can confirm that the result is useful. If the customer's priorities change, revisit this definition before comparing activity with an old target.

Establish a fair view of use

Look at the people or accounts expected to perform the task during the review period. Separate access, attempts and completed work. Where several people contribute to one account workflow, inspect individual actions and whether the account completes the work. Account-level reporting may require additional tooling or configuration; an account identifier in an event is not, by itself, a reliable account report.

Choose a period that gives the task a chance to occur. A monthly process cannot be judged fairly from a few days of inactivity. Check event definitions and role or account mapping before acting on a surprising chart. A changed event name, missing identifier or automated action can alter a count without changing the customer's experience.

Product records can show recorded activity. Ask the customer whether the resulting work was correct and useful. If the operational outcome sits in the customer's systems, agree how to check it rather than treating product activity as proof.

Australia’s Digital Transformation Leadership

Choose events for the adoption question

Keep the event set focused on the account's agreed adoption questions: events record actions people take in the product, while properties describe their context. Tracking every possible action can bury useful signals, while missing a key completion event can leave the adoption question unanswered.

Prioritise events that mark completion of a product process and actions that show how people use the workflow's main mechanics. Review the selection if the account's questions change.

Investigate the gap and assign a response

Describe the gap by role, task and period, then ask the relevant people what happened. Missing completions might reflect access, configuration, a difficult step, a policy decision, an infrequent task or work handled elsewhere. Check the explanation before choosing an action.

If an administrator has not granted access, name that dependency. Route a suspected product fault to a technical owner. If the customer no longer needs the workflow, confirm the new goal before trying to restore the old pattern. Customer success can coordinate the response without owning every fix.

Record the obstacle, the person able to address it, the next step and when progress will be checked.

Use conversations to test the diagnosis

Speak with current users who perform the workflow to understand their circumstances, how they use the product and what they need to achieve the intended result. Interviews are usually conducted with one person at a time; a pair or small group can be appropriate when people complete the task together.

Plan the discussion around the adoption question. List the topics, prepare starter and follow-up questions, and decide which process or technology you want the user to show. A discussion guide helps keep the conversation on track and ensures the same topics are covered consistently across users.

Test the questions and structure with a colleague before using the guide with customers. Revise questions that are unclear, and use follow-ups to explore what happened when the workflow stalled or the result did not meet the intended need.

Check whether the response helped

After enough time for the task to recur, review the affected users and workflow again. Did they complete the work? Did the customer confirm that it met the intended need?

If activity rose but the task still failed, keep the gap open. If no eligible task arose, defer the judgement and set a fair review point.

Keep a brief account record: agreed adoption definition, evidence and its limits, customer explanation, action owner and next review point. Update it as the customer's work changes.

When a task is shared across a team, speak with the people involved in its relevant steps, not only an administrator. Compare their explanations to see whether they describe the same obstacle or different ones, which can help distinguish an individual difficulty from a workflow problem affecting the account.