Designing the complete learning journey in six steps

Step 1: start with the learning goal

Write down what the learner does differently afterwards. Not "knows the procedure" but "carries out the procedure without having to look it up". Check the learning goal with three questions: can I see it, can I measure it, and why does it matter for the work?

A good test: could a manager see whether it worked? If not, the goal is still too vague.

Step 2: design and create

Choose the forms that fit the goal. Knowledge: swipeslides. Conversation: a CrewMate. Deciding in a team: a scenario game. Getting to know a place: a 3D scene. Let the AI make the first draft from a topic or document, and let the expert sharpen it. See AI-generated learning content without losing quality.

Step 3: learn and practise, in small pieces

Start with short pieces and spread the material over several moments. Have the learner do something after each piece. Add practice moments where skill is the point. A learning journey has the shape of a tree with steps and branches, so you can adapt the route to what someone already knows. See microlearning with swipeslides and spaced repetition.

Step 4: bring it to the work

Do not design learning as a separate event. Link it to the work process: a workflow that assigns the learning journey at the right moment, a chat for questions, an assignment the learner carries out in real work. See learning in the flow of work and transfer to the shop floor.

Step 5: measure and reward

Decide in advance what you measure. Give questions a weight and a theme, so you see where the group stands. Have the AI write a personal report per learner. Choose a reward that gives recognition: certificates, awards with a reason, growth paths. See measuring learning and rewards without the gamification pitfalls.

Step 6: improve

Look at the statistics per learning journey and per learner. Where do people drop off, which question keeps going wrong, which theme stays weak? Adjust the learning journey, let the AI help per slide, and publish again. Because adjusting is cheap, the learning journey gets better with every round.

An example: a learning journey for customer conversations

The learning goal: an employee holds a customer conversation in which they ask follow-up questions before offering a solution. The design: a short series of swipeslides on the structure of the conversation, with an ordering question and a case. Then a CrewMate conversation to practise it, with assessment and report. Then an assignment: hold two real conversations this week with this approach and briefly share what you noticed, for example through a voice report.

For measuring: scores per theme on the knowledge questions, the conversation report, and a response from the manager after a month. For improving: see what kept going wrong and adjust the case. The whole journey fits in a few weeks and consists of parts that each serve their own goal.

Pitfalls in design

• Building everything at once. Start with a minimal learning journey, test with a small group and expand.
• Choosing forms for the form’s sake. A game, VR or 3D is not a goal. Choose what serves the learning goal.
• No owner. A learning journey without someone who maintains it goes out of date. Appoint an owner and plan a moment to look back.
• Forgetting the measuring. Decide in advance what you want to know.

Branching: adapting the route to the learner

Not everyone starts at the same point. A learning journey with branches lets the route depend on answers: whoever answers a question correctly skips an explanation; whoever gets it wrong gets an extra explanation or a simpler case. That saves time for those who already know and supports those who need it.

Start with a short entry test or a few questions at the beginning. Decide in advance which routes you want, keep them limited (two or three) and test each route. A tree with too many branches becomes unmanageable and does not maintain itself.

Maintenance and versions

A learning journey is never finished. Rules change, systems change, examples go out of date. Make maintenance part of the design: appoint an owner, plan a review twice a year and keep track of what changed. Because you can export and import a learning journey, you can keep a version and test a new version before you put it live.

• An owner with a name.
• A fixed review date.
• A short list of changes per version.
• A place where users can report mistakes, for example the chat.

Structure: what a learning journey contains

A learning journey in CoVince has steps in a tree structure with a goal, members and roles, a calendar, a call and a chat. You get a start screen, export and import, folders and an "Ask the AI" bar. Whoever joins again continues where they stood. Progress is tracked per learner and per step, and completing it earns certificates and growth paths.

For planning, see planning classes and sessions.