Your last learning journey looked complete. Good content, a strong session, people engaged in the room. Three months later, they work much the way they did before.
It's easy to blame the content, or the session, or the people. Usually none of those is the problem. The parts of a learning journey that actually change how people work — practising the new behaviour on real work, a manager noticing and asking about it, a peer group comparing what landed and what didn't — mostly weren't skipped on purpose. They were left to hope: told to happen, then trusted to happen on their own. And the parts you leave to chance are the first ones that don't.
That's the idea underneath everything else in this collection. The activities that create the change don't happen because you scheduled a workshop and crossed your fingers. They happen because you designed for them to — so nothing rides on anyone remembering. If you'd rather start with the how-to, building a learning journey covers the mechanics; this article is about why the design has to carry the parts that matter.
Behaviour change lives in the parts a slide can't carry
Information has never been behaviour change, though most rollouts are built as if it were: explain it well enough and people will do it. They mostly don't. A new way of working — a difficult conversation, a coaching habit, a new sales motion — gets built through practice, reflection, and the people around someone, not through a well-made deck.
That's the good news and the catch at once. The content is the easy part to produce and the easy part to deliver. The parts that actually move behaviour — a real task practised in the week, a manager who asks the right question, a peer group that meets and goes deep — are harder to make happen, and they're exactly the parts that decide whether anything changes. Deciding which of those parts your goal actually needs is its own job, and the one to get right first.
The parts that matter are the first to slip
Every one of those parts depends, quietly, on someone remembering. Someone has to book the peer call. Someone has to step up and lead it. The manager has to recall which week it is and think of something useful to ask. The participant has to go and try the thing, then come back and reflect on it. Miss any one link and the chain goes slack.
And under time pressure — which always comes — the essential parts are the first to erode. The workshop stays on the calendar, because thirty diaries are locked in and you can't un-book it. Everything around it slips: we'll skip the manager notes this round, we'll do the peer group over chat instead. Session three opens with who met with their group? and four hands go up out of twenty. On anything that matters, hope isn't a strategy.
Scaffold each essential activity so it can't quietly be skipped
The fix isn't more enthusiasm, or a facilitator in every room. It's scaffolding — the same training wheels you'd put around any process you actually want to happen. Give each essential activity a date, a prompt that lands in a busy inbox, a deadline, and a place to report back. Then it stops being hoped for and starts being knowable: you can see whether it happened, and it happens without anyone chasing it.
That's what a learning journey in Knowly is for. You place each activity on the timeline, and Knowly sends it on its date, reminds people as a deadline gets close, and shows you what's been done — so the peer group, the manager note, and the follow-up reflection all land on their own. The point of principle: put scaffolding around every part the result depends on, not just the workshop.
Point the scaffolding at the parts that matter most
Scaffolding is only worth building around the parts that carry the change — which is why the rest of this collection is organised around them. The manager is the biggest single predictor of whether anything sticks, so involve managers in parallel with short, specific prompts rather than a copy of the deck. Peer groups carry the knowledge a module can't, but only when a few mechanics are wired in — make peer groups actually meet. And which parts your goal needs in the first place comes from designing from the goal and the blockers, not the content.
You can see it all threaded through one scenario in onboarding a new manager and the one who hired them — the manager track, the peer group, the follow-through, each one scheduled rather than hoped for.
Design for the essential parts to happen, and they will. Leave them to chance, and something else will fill the week instead — just not the thing you meant to change.