Start with the result, not the learning solution
Before designing a program, ask what would be observably different if it worked. Not what people would know. What would they do, decide, produce or stop doing?
If the answer is vague, the measurement will be vague too. ‘Improved leadership capability’ is hard to inspect. ‘Supervisors run the pre-start conversation, identify the changed risk and record the agreed control before work begins’ gives everybody something concrete to work with.
This does not mean every useful outcome fits neatly into one number. It means we are honest about the change we are trying to create.
Find out why it is not happening now
A capability gap is one possible cause. So are time, unclear ownership, broken systems, conflicting measures, poor access, manager behaviour and the fact that the requested action may not make sense in the real workflow.
If people already know what to do but the system makes it painful, more content will produce more completion data and the same performance problem.
Talk to the people doing the work. Watch the task. Look at existing data and artefacts. Treat ‘they need training’ as a hypothesis, not the diagnosis.
Build a short evidence chain
I like to connect four levels. The business result describes why the work matters. The performance behaviour describes what people need to do. The enabling capability describes what they must be able to notice, decide or perform. The learning activity is one possible way to build that capability.
The chain helps because it keeps the activity in its place. A workshop can be excellent and still fail to influence the result if managers, systems or incentives pull in the other direction.
- Business result: what measure or consequence matters?
- Performance behaviour: what must happen differently in the work?
- Enabling capability: what judgement, skill or knowledge supports that behaviour?
- Response: what combination of practice, support, process or technology will help?
Take a baseline before the launch email
A baseline can be simple. Sample ten pieces of work. Observe five hand-overs. Review the current error rate. Ask managers what they are already seeing. Record the time a task takes and where it waits.
Use evidence that is close to the work. Self-reported confidence can be useful, but it should not carry the whole story. People can feel confident and perform poorly. They can also feel uncertain while carefully producing a good result.
The baseline helps you decide whether the change is meaningful rather than merely different.
Use the lightest measure that answers the question
Not every initiative needs a dashboard with twelve tabs. Measurement has a cost, and collecting data nobody will use is its own kind of waste.
Choose a small set: one result measure, one or two behaviour or quality measures and enough participation information to understand who had the opportunity to change. Add a short qualitative check to explain the numbers.
Decide when you will review it and what decisions the evidence can change. Measurement that cannot influence a decision is reporting theatre.
Tell the honest contribution story
Workplace performance rarely changes because of one program alone. Customer demand shifts. A manager changes. A system improves. A policy lands at the same time.
Avoid claiming that learning caused every movement in the business measure. Show the chain, the timing, the evidence and other plausible influences. ‘Associated with’ is often more credible than ‘delivered’.
That honesty does not weaken the value of learning. It places learning inside the real system where performance is created.
Learning is not the output. Performance is the output.