Customer education for B2B products

Customer education helps people in a customer organisation complete useful work with a product. Build it around the tasks each role needs to perform, make help available when those tasks arise, and check whether people can complete them. Course attendance and guide views show engagement with education; they do not establish that the customer's work improved.

Decide who needs to do what

Start with the customer's intended workflow. An administrator may configure access, a team member may perform the task, and a process owner may check the result. They need different guidance even when they use the same product.

For each role, record the next task, its prerequisites, what a successful finish looks like and where to get help. Confirm the map with people who do the work. If the customer has agreed an outcome, use it to prioritise tasks. The education plan should explain product work; the wider success plan records the customer's overall result.

Consider a hypothetical approvals product. An administrator grants managers access; a manager submits an eligible decision; an operations owner checks that it reaches the agreed record. A single product tour would leave important differences between those jobs unexplained.

Refine the audience beyond job titles

Treat a role label as a starting point, not a complete description of what someone knows. People in the same role can have different experience, and familiarity with a related product or project can affect what they need explained.

Consider how close the audience already is to the knowledge behind a task. Someone familiar with a related workflow may need less context than someone encountering it for the first time; knowledge can also become less current over time. Use those differences to decide which explanations are essential and which would repeat what learners already know.

A practical way to frame the gap is to compare the knowledge and skills a task requires with the audience’s current knowledge and skills. This helps a programme focus on what people need to learn for the work, rather than treating every user of a product as having the same starting point.

Give each resource one job

These are design choices, not measured rankings of formats. A recording can help someone revisit a demonstration; written steps may be easier to consult during a task. Make the starting point and expected result clear in either format. Route a technical fault or unresolved customer policy decision to its owner rather than assigning more training.

Customer Needs vs. Appropriate Learning Resources

Make the programme easy to discover and manage

For a programme spanning products or services, consider how customers will discover relevant learning. They do not know which team or portal hosts it. Microsoft Engage Center, for example, brings learning and services together in one place, with browsing, keyword search and filters for product and service type.

Plan access as part of the programme, especially when some people need to manage learning as well as consume it. In Microsoft Engage Center, users with the Learning User role can view learning content. Learning Managers can grant management of learning content and access to learning content. Clear role boundaries help customers know where to go and who can make changes.

Put help near the work

Organise resources by the task, using terms customers would search for. State the required role and prerequisites before the steps. Separate first-use guidance from reference material for experienced users. Provide a clear route to support or the customer's process owner when the instructions cannot settle a problem.

Education may begin during onboarding, but new staff, changed tasks and product releases create later needs. Assign an owner to each important resource. Revise or retire instructions when the interface, permissions or workflow changes.

Set programme-level maintenance criteria

Review guidance when a new or enhanced feature affects users or administrators, the interface or API changes, a process or workflow changes, or a feature is deprecated or removed.

Agree who drafts and reviews guidance when customer work is affected by a product change, and coordinate timing with the people responsible for the change.

Check the work and improve the guidance

Decide what task evidence to inspect before distributing a resource. After the task has had a chance to arise, check whether the intended people started and completed it, and ask the customer whether the result was usable. Review questions and failures at particular steps. If records cannot identify eligible users or tasks, state that limit.

A change after training warrants investigation, but it does not establish that education caused the change. Compare relevant roles and periods, and check what else changed. Use the findings to clarify a step, change when guidance appears, add practice or route a product problem to its owner.

Microsoft Engage Center automatically tracks progress in its on-demand learning experience. That records learning progress; a separate task check is needed to establish whether product work was completed.