Written by Christoffer Andreasson
Head of Content at Promote
Ask your own team how you'd define an "effective" learning journey, and watch the goalposts move. Completion rates come up first ("nearly everyone finished the modules"). Then satisfaction scores. Then engagement dashboards, attendance, time in the platform. None of it answers the question. All of it is measurable, easy to report upward, and, importantly, safe. Numbers that can always be improved without ever proving that anyone changed how they work.
This isn't a data problem. It's an incentive problem. Completion and satisfaction are the numbers a stakeholder update expects. Behavior change happens weeks later, on the job, in front of a manager, largely outside L&D's direct line of sight. Answering "was this effective?" with a completion rate isn't dishonest so much as convenient. It just isn't an answer.
What does "effective" actually mean for a learning journey?
Robert Brinkerhoff's research on training transfer, the foundation of the High Performance Learning Journey (HPLJ) methodology, offers a definition that holds up under pressure. Training is effective when the intended behavior shows up on the job, in a way that produces a business result someone can point to. Not "was understood." Not "was well received." Applied, sustained, and connected to an outcome the organisation actually cares about.
That standard rules out most of what passes for evaluation today. A program can score highly on every reaction survey and still fail completely, because reaction was never the thing that mattered. Completion and satisfaction data can't tell you what happened afterwards. Only following up with real participants, months later, can.
One story from Promote's own collected training case archive makes the gap concrete. A group of technicians went through a well-designed, well-reviewed technical training program, the kind that would score well on any standard evaluation. Months later, a review found a large share of participants had never even had the opportunity to apply what they'd learned. The training itself worked. As an investment of time and budget, it hadn't delivered anything. "Effective training" and "effective learning journey" are two different claims, and only one of them is worth the investment.
Why don't more learning programs use this definition?
Committing to sustained behavior change as the definition of effective is harder to guarantee than a completion certificate. That's exactly why it's easy to quietly default to the easier standard instead. It means admitting three things:
None of that fits neatly onto a steering committee slide. Most internal reporting settles for softer language instead, "engagement," "impact," "success", language that sounds like it means behavior change without committing to prove it.
What should you ask before a learning journey launches?
If effectiveness is sustained behavior change tied to a business result, four questions matter more than any completion target:
A learning journey designed against this standard looks different from a course rolled out over a few weeks. It's built backward from the behavior and the business result, with the event itself as one part of a longer structure, not the whole of it.
The point isn't to throw out completion data
It's to stop letting it stand in for proof. Whatever shape a program takes, the question that actually determines its value is whether it was designed to produce behavior change, or just to produce a report that looks like it did.
That's the definition worth holding your own programs to before the goalposts move.
