Learning Paths: turning single exercises into a training program

A learning path is an assigned training program with a fixed sequence. It links several live audio role-plays and can also include short texts, videos and PDFs – as context before the practice or reflection afterwards.

The difference from open access is guidance: participants don't have to search a catalogue, they see exactly what comes next and how far along they are. At the end there's a conclusion, not open-ended practice.

This works particularly well when onboarding, enablement or leadership development should run as a clear process with a beginning and an end rather than as occasional sessions.

A path is built from individual steps. You can use scenario steps (the live conversation itself), text steps for short framing, video steps via embedded video, and PDF steps for documents such as guides, product material or conversation standards. Longer programs can be divided into phases using sections.

You decide the order. A typical pattern is: brief context, then the conversation, then the evaluation – and one level further in the next step.

The weighting matters: the other formats are preparation and framing. The training effect comes from the spoken conversation, not from reading.

No, deliberately so. A learning management system administers courses, certificates, mandatory training and compliance records across an organisation's entire training estate. Learning paths aren't built for that and don't replace an LMS.

What learning paths do is different: they turn conversation practice into a structured, assignable program with a defined conclusion. The focus is application under pressure, not knowledge administration.

In practice the two complement each other well. The LMS covers knowledge and compliance; the learning path covers the hard part – the real conversation.

A single scenario trains one specific conversational moment. A learning path puts several such moments into a meaningful order and turns them into a program with progression, supporting material and a conclusion.

The difference is both pedagogical and operational. Pedagogical, because skill builds step by step rather than being crammed into one session. Operational, because entire tracks can be standardised and rolled out repeatedly to teams, cohorts or clients.

If you only want to rehearse one situation before a real meeting, a single scenario is enough. If several people should follow the same route, a learning path is the better structure.

Mainly teams where conversations aren't settled in a single meeting: sales with multi-stage buying centre processes, managers with recurring employee conversations, L&D and academy teams running structured development programs.

Three situations in particular: when new hires need to reach a target level faster, when several locations should train to the same conversation standard, and when sensitive sequences need to be repeatable without risk.

Consultancies and training providers benefit too, because they can assign programs repeatedly instead of moderating every run by hand.

For most use cases three to six conversation steps is a good start – enough for visible progress and repetition, lean enough that people actually finish.

Short paths suit onboarding, individual negotiation phases or recurring leadership moments. Longer paths make sense when several stakeholders are involved or when you're building a complete cohort program.

More important than length is the logic between the stages. Every step should have a clear purpose and build on the previous one – and the path should have an end that's realistically reachable.

Small groups can be invited directly. For larger rollouts there's a CSV import: upload a participant list of up to 1,000 rows and decide whether invitations go out immediately or at a scheduled time.

Scheduled sending is more than convenience. When a cohort starts together on the same day, the likelihood of people actually beginning is considerably higher – a shared start beats trickled individual activation.

You can also define per person which training areas are accessible at all, for example leadership only or sales only.

The final report summarises the evaluations of the completed conversation steps. It's based on the actual assessments of the conversations held – not attendance, clicks or time spent.

That gives you something more substantial than a conventional training record: it shows how conversational behaviour developed across the path and where the strengths and open points lie.

For HR, program owners or clients it's the evidence at the end of a program – and for participants it's the closure that distinguishes a program from open access.

Yes. Access to training areas can be controlled at several levels – company, partner and additionally per individual user. An invitation can set the enabled area directly.

In practice: managers see leadership content, the sales team sees sales content, and a mixed program remains possible where that makes sense.

Evaluations can also be viewed per area, so skill development in leadership and sales doesn't blur into one indistinct overall figure.

Where the scenarios in a path are built as one connected case – the same person, the same company, the same conflict – earlier statements, commitments and the state of the relationship continue to matter in the next conversation. That's where the effect over time comes from.

This is a question of scenario design, not automatically a property of every path. A path can also consist deliberately of independent situations, for example when different conversation types are practised in sequence.

So make this call early when building a path: one continuous case, or a series of standalone situations.

No IT project and no finished academy structure. In practice you need a clear occasion, the target role, the typical conversation sequence and an understanding of which moments should be trained.

It also helps to have your product context, common objections, relevant stakeholders and your criteria for good conversation handling. The clearer that frame, the better the path fits your day-to-day. For a first draft, the AI can propose a path structure that you then adjust.

A typical sequence: start with one concrete use case – onboarding new managers, say, or SDR ramp-up – build the path, assign it to a manageable group and refine after the first run. Larger organisations do well to start with one clearly bounded area before adding roles or regions.

Yes. Training providers, consultancies and enablement partners can create their own paths at partner level and assign them to several client companies. Release is controlled per client, and you see progress for each assigned company.

Commercially that's the real point: you sell a program with your own methodology instead of individual conversations by the unit. Clearer for the client, more predictable for you.

Under your own brand the methodology stays yours; the practice and evaluation layer comes from the platform. For longer sales or leadership tracks in particular, this lets you build a scalable offering without moderating every run.

Seminars and e-learning convey models, conversation structures and examples. Learning paths pick up where application gets hard: real speaking under pressure, with resistance, objections and emotional reactions.

Unlike manual role-plays, you don't have to coordinate trainer schedules or guarantee consistent role-play quality. Everyone works through the same sequence whenever it suits them and gets immediate feedback on their own conversation.

Compared with generic chatbots the difference is depth: live audio, psychologically defined characters, clear scenario context and a separate evaluation of the conversation. If you only want to transfer knowledge, other formats are fine. If you want to train behaviour, a learning path is closer to reality.