What is a role-based customer curriculum?

It is a structured set of learning experiences organised around customer responsibilities and the capabilities needed to fulfil them. It typically combines common foundations with focused routes. Its purpose is to make learning relevant without requiring every customer to study every product function.

Should each job title have its own learning path?

Usually, responsibilities provide a better starting point than titles. People with the same title may perform different work, while different titles may share tasks. Define the responsibilities first, then let customers combine routes where one person holds several roles.

What belongs in the shared curriculum core?

Include foundations that each intended role genuinely needs, such as essential concepts or common working context. Keep specialised decisions in the relevant branches. Review the core regularly so it does not become a growing collection of material that only some learners require.

Can experienced customers skip foundation lessons?

Yes, where they already have the necessary capability and any other prerequisites. Make those requirements visible and provide a reasonable way to judge readiness. Prior experience should inform the entry point, although familiarity with terminology alone may not establish readiness for a particular task.

How do you prevent duplicate content across role paths?

Maintain shared concepts as common components with clear ownership and a record of where they are used. Keep role-specific examples in the branches. When updating a shared component, review the dependent routes so explanations, examples and prerequisites remain consistent.

Build a Role-Based Customer Learning Curriculum

Build a customer learning curriculum around responsibilities, shared foundations and realistic task dependencies rather than job titles alone.

Published: 13 October 2026
Topics: Customer education, Learning design

A role-based customer curriculum groups learning around the responsibilities people hold and the tasks they need to perform. Start with shared foundations, then create focused routes for different decisions and workflows. Sequence those routes by genuine prerequisites, give experienced customers suitable entry points, and maintain the map as responsibilities change.

Two customers with the same job title may use a product very differently. A useful curriculum accounts for those differences without creating a separate collection of lessons for every variation in an organisation chart.

Define roles through responsibilities

Begin with the work customers are responsible for, rather than a list of titles supplied by your own organisation. One customer administrator may configure processes, manage access and prepare reports. Another may only manage access while colleagues own configuration. The curriculum should make those responsibilities visible before assigning learning.

This is a preview. The full piece is free for members (3 reads a day) and unlimited with Premium.

Read the full piece on Led by Community (free account, 3 reads a day)