Training is still frequently designed around what people should learn. A subject is selected, learning objectives are written, content is gathered, exercises are added, and a programme gradually takes shape. The result can be perfectly respectable: a coherent curriculum, clear learning objectives, relevant materials and participants who leave with new knowledge.
Yet something important can still be missing.
The participant may know more without being able to do anything differently. The buyer may have received the programme they commissioned without being able to point to a meaningful change in practice. And the trainer may have delivered everything that was promised while still wondering why the programme did not have the impact everyone expected.
The problem is not necessarily poor training design. It is that learning has quietly become the object of the exercise.
I have come to think that this is the wrong starting point. Training becomes considerably more useful when we stop treating learning as the destination and start treating it as one of the mechanisms through which a practical outcome is achieved.
That changes the question.
Instead of asking, What should participants learn?, we begin with, What should be different because they participated?
That difference sounds small. It is not. It changes how a training offer is positioned, how it is designed, how participants understand its relevance, how buyers evaluate it and, eventually, whether anything changes after the training room has been left behind.
The problem with starting from learning
Learning objectives are useful. They give designers something concrete to work with. They help determine content, activities and assessment. In instructional design, they are considerably more useful than vague intentions such as “participants will gain insight into…” or “participants will understand the importance of…”.
The problem begins when a good design instrument becomes the definition of success.
Consider a training programme for project managers about stakeholder management. Its learning objectives might say that participants will understand different stakeholder types, recognise sources of resistance and apply several communication techniques.
Those objectives are reasonable. They are also insufficient.
A project manager does not wake up on Tuesday morning thinking, “Today I would like to understand stakeholder mapping.” They have a project that is stuck. A department that is resisting a change. A sponsor who has stopped responding. A meeting in which everyone appears to agree and then does something different afterwards.
The topic matters because of the problem it helps solve.
This is the first shift: people rarely value a subject in isolation. They value what becoming capable in that subject allows them to do.
The distinction becomes particularly important when training is sold rather than simply assigned.
A participant asks, consciously or not, “Why should I spend my time on this?” A manager asks, “Why should I pay for this?” An organisation asks, “What will be different afterwards?”
None of these questions is answered particularly well by a list of topics.
“Stakeholder management” is a topic.
“Handle resistance to a project without allowing every objection to derail the work” is closer to an outcome.
The first tells me what the training is about. The second tells me why I might care.
That difference is at the heart of practical transformation.
Practical transformation begins where the learner’s problem begins
A useful training outcome sits much closer to reality than a learning objective.
It describes a change in capability, behaviour, performance or decision-making that matters in the participant’s actual context. It does not have to promise some spectacular transformation. In fact, the smaller and more concrete the change, the easier it is to make credible.
Imagine a subject-matter expert who wants to teach colleagues how to interpret a new regulation.
The conventional approach starts with the regulation. The trainer identifies the important concepts, explains the framework, creates examples and perhaps finishes with a quiz.
An outcome-led approach starts somewhere else.
What are these people struggling to do because they do not yet understand the regulation? Are they making inconsistent decisions? Asking the same questions repeatedly? Escalating cases unnecessarily? Spending an hour interpreting something that should take ten minutes?
Now the training has somewhere to go.
The regulation is still there. The knowledge still matters. The concepts still need to be explained. But they have acquired a job to do.
This is a subtle but important point. Outcome-led training does not make content less important. It gives content a purpose.
That purpose also makes decisions easier.
If an explanation does not help participants reach the intended outcome, its presence needs justification. If an exercise does not rehearse something they will actually have to do, its value becomes questionable. If a learning activity is engaging but disconnected from the work, engagement alone is no longer enough to defend it.
The outcome becomes a kind of filter.
That is useful because training design is full of tempting additions. Another model. Another activity. Another video. Another worksheet. Another concept that is interesting enough to include.
Without a clear outcome, the programme tends to accumulate.
With a clear outcome, the designer has permission to remove things.
That is one of the less discussed benefits of outcome-led thinking: a strong outcome reduces content.
Buyers do not purchase topics. They purchase reduced problems.
There is another reason this matters, and it has little to do with learning theory.
Training is also a buying decision.
A buyer has a problem, a budget and an amount of organisational attention they are willing to spend. They need to make a judgement about whether a particular intervention is worth the cost.
This is where training providers sometimes make their own lives unnecessarily difficult.
They describe what they offer in terms of subjects.
“Communication training.”
“Leadership development.”
“Data literacy.”
“Change management.”
“Project management.”
These descriptions are understandable. They also force the buyer to do part of the thinking.
The buyer has to work out why the subject matters, which problem it addresses, what improvement it might produce and whether that improvement is worth paying for.
A stronger offer does some of that reasoning for them.
It might say that the training helps newly appointed team leaders run difficult performance conversations with greater clarity and consistency. Or that it helps policy advisers turn complex information into decisions that non-specialists can act on. Or that it helps experienced professionals turn their specialist knowledge into a practical workshop colleagues can actually use.
Now the buyer can recognise the problem.
This does not mean promising a guaranteed financial return or inventing an impressive number. It means making the intended change visible.
That distinction matters because positioning is fundamentally an exercise in relevance.
A topic is broad.
A practical outcome narrows the field.
That narrowing is not a weakness. It is what makes an offer recognisable.
The uncomfortable consequence: specificity excludes people
There is a tension here that is easy to overlook.
If you describe a training programme as “improving communication skills”, almost everyone can see themselves somewhere inside it. That feels commercially safe.
If you describe it as “helping experienced technical specialists explain complex decisions to non-specialists without losing the substance”, fewer people will identify with it.
That can feel like losing potential customers.
In practice, it is often the opposite.
A vague promise creates weak recognition. People can imagine that the programme might be relevant, but they cannot immediately see that it is relevant to their situation.
A specific outcome creates recognition because it gives the reader something against which to compare their own reality.
This leads to a useful principle: the strength of a training offer is not determined by how many people could theoretically benefit from it, but by how clearly the right people recognise themselves in it.
That has consequences for subject-matter experts in particular.
A subject-matter expert often sees the breadth of their own knowledge. They know there is much to teach. They may have spent years accumulating expertise and naturally want to represent that expertise accurately.
But the learner does not need the entire map.
They need to get somewhere.
The challenge is therefore not simply to transfer expertise. It is to decide which part of that expertise becomes useful for a particular person facing a particular situation.
That is a different kind of work.
It requires judgement.
Engagement is not the starting point
The discussion about training outcomes frequently gets mixed up with another concern: engagement.
How do we keep participants engaged?
The usual answers involve variety, interaction, discussion, exercises, videos, quizzes, group work and increasingly sophisticated digital experiences. These can all have their place.
But engagement has a peculiar weakness when it is treated as the primary design goal: people can be highly engaged in something that they do not need.
A participant can enjoy a workshop and still fail to apply it.
They can describe the facilitator as excellent and still return to exactly the same behaviour on Monday.
They can remember the exercise and forget why they were doing it.
This does not mean engagement is irrelevant. Attention is necessary for learning. Motivation matters. Poorly delivered training is unlikely to produce much change.
But engagement is better understood as a condition that supports transformation than as the transformation itself.
The distinction is particularly visible when training moves from the room into the workplace.
I have seen a recurring pattern in professional environments: people can participate seriously in a session, understand the material and even agree enthusiastically with the approach, yet revert to familiar behaviour when the first real-world complication appears.
That moment tells us something important.
The problem was not necessarily that they failed to learn.
The problem was that the training had not sufficiently connected learning with the conditions under which the new behaviour would actually have to survive.
This is why practical outcomes matter. They force the designer to think beyond the learning event.
If the intended outcome is “participants understand how to structure a difficult conversation”, the programme can stop at understanding.
If the intended outcome is “participants can prepare and conduct a difficult conversation using a clear structure, even when the other person becomes defensive”, the design problem becomes more demanding.
It also becomes more useful.
The second outcome tells us what the participant must practise. It tells us what realistic difficulty needs to be introduced. It gives us something to observe. It creates a bridge between the training environment and actual work.
The outcome therefore changes the training before the first slide is ever created.
There is a difference between knowing, doing and being able to do
This is where a useful distinction emerges.
Knowledge, behaviour and capability are related, but they are not interchangeable.
Someone can know the steps of a process without being able to perform them under pressure. Someone can perform a task once with extensive guidance without being able to do it independently. Someone can demonstrate a skill in training without using it consistently in the workplace.
These are different states.
Training discussions sometimes collapse them into the single word “learning”. That makes the design problem appear simpler than it really is.
Suppose a training programme teaches employees how to give better feedback.
At the knowledge level, participants might be able to explain the difference between constructive and unhelpful feedback.
At the practice level, they might be able to conduct a role-play.
At the workplace level, the real question becomes whether they initiate and handle difficult feedback conversations differently when there is something at stake.
The outcome should therefore describe the level of change that actually matters.
This also explains why some apparently well-designed training programmes struggle to create impact. Their objectives describe the learning event, while their buyers are hoping for a workplace result.
There is a gap between the two.
The wider that gap, the more faith everyone has to place in transfer.
And faith is a poor operating model.
The hidden value of an outcome is that it creates a chain of reasoning
A strong practical outcome does more than improve marketing language.
It creates a chain:
Problem → desired change → capability required → learning experience → application.
This chain gives the training a logic that can be inspected.
If a programme is supposed to help policy professionals make clearer recommendations, we can ask what currently prevents that from happening. Perhaps they struggle to separate evidence from interpretation. Perhaps they produce documents that contain information but do not make a recommendation visible. Perhaps they are writing for completeness rather than decision-making.
Those observations tell us what capability is missing.
Only then does it make sense to decide what people need to learn.
The order matters.
If we start with the content, we tend to ask, “What should we teach?”
If we start with the outcome, we ask, “What needs to become possible?”
The second question is harder. It is also closer to the real problem.
This is why I increasingly see training design as a form of translation.
A subject-matter expert starts with knowledge.
A participant starts with a situation.
A buyer starts with a problem.
Good training connects those three perspectives without allowing any one of them to dominate.
The subject-matter expert must recognise that expertise is not the product in itself. The participant must be able to see how the capability relates to their work. The buyer must be able to understand why the intervention is worth attention and money.
The practical outcome is where those perspectives meet.
A strong outcome also changes the conversation before training begins
There is a second-order effect that deserves more attention.
When people know exactly what they are expected to become capable of doing, they enter the training differently.
They can recognise relevant examples. They can connect concepts to situations they have experienced. They can judge whether an exercise is useful. They can notice where they are struggling.
In other words, a clear outcome does not merely improve the trainer’s design.
It changes the participant’s role.
Instead of consuming a programme, the participant has a destination against which they can orient themselves.
This is particularly important for experienced professionals. They are rarely empty vessels waiting for knowledge to be poured in. They already have habits, assumptions, examples, shortcuts and workarounds.
Their problem is often not a lack of information.
It is that they need to change something they already do.
That makes the training challenge fundamentally different.
Teaching a new concept is relatively straightforward compared with helping someone recognise that their existing way of working is no longer producing the result they need.
Practical outcomes bring that tension into the open.
They give the participant something against which current practice can be examined.
This changes how training should be positioned
Positioning is sometimes treated as a marketing exercise that happens after the training has been designed.
I think that gets the relationship backwards.
Positioning is partly a consequence of knowing the outcome clearly.
Consider two offers.
The first is:
A workshop on effective presentations.
The second is:
A practical workshop for technical specialists who need to explain complex information clearly enough that decision-makers can act on it.
The second is not simply better copy.
It reveals a different understanding of the product.
The first offer is organised around a subject. The second is organised around a person, a situation and a change.
That makes the intended audience easier to identify. It makes examples easier to choose. It makes exercises easier to design. It even makes it easier to say no to people for whom the training is not intended.
This is why I would argue that positioning should begin with transformation rather than description.
If you cannot explain what becomes different for the right participant, you probably do not yet have a sufficiently defined training offer.
You may have a subject.
You may have expertise.
You may even have excellent training material.
Those are useful ingredients. They are not the same thing as a proposition.
The subject-matter expert has a particular problem
This becomes especially relevant when the person creating the training is an expert in the subject.
Expertise creates an abundance problem.
The expert knows too much.
They see nuance, exceptions, history, competing perspectives and edge cases. All of those things are intellectually legitimate. The temptation is to include them because leaving them out can feel irresponsible.
But a training programme has a different responsibility from a reference work.
Its purpose is not to represent everything that is true.
Its purpose is to make something possible.
That requires selection.
The expert has to move from “What do I know that people should know?” to “What do these people need to be able to do, and which parts of what I know help them do it?”
That shift can be surprisingly difficult because it changes the status of expertise.
Knowledge becomes raw material.
The outcome becomes the organising principle.
This is also where I see a connection with the broader idea behind Training Stacks. A useful training asset does not begin with the amount of knowledge an expert possesses. It begins with the practical change that knowledge can enable. Once that change is clear, the expertise can be shaped into a workshop, exercise, guide, template, explanation or other learning component that serves the same purpose.
The stack follows the outcome.
Not the other way around.
Three tests for a meaningful training outcome
The idea can be made practical without turning it into another elaborate methodology.
When looking at a proposed training outcome, I would ask three questions.
Could the participant recognise the situation?
If the outcome is so abstract that a participant cannot connect it to something that happens in their working life, it is probably still a learning goal disguised as an outcome.
Could we observe the change?
“Understand”, “know”, “gain insight” and “be aware of” are difficult to connect to practical evidence. A useful outcome gives us something that could actually be seen, heard, produced, decided or done differently.
Would the buyer care if this changed?
This is the uncomfortable test.
A participant might benefit from knowing something that has little organisational consequence. A buyer is less likely to invest in it unless the knowledge connects to a problem they care about.
The three questions create a useful pressure test:
recognisable, observable, valuable.
If an outcome fails one of them, the training may still be worthwhile. But the case for it becomes weaker.
The unresolved part: outcomes are not entirely under the trainer’s control
There is an important limit to this argument.
Training can influence capability. It cannot completely control what happens afterwards.
A participant might leave a workshop ready to apply a new approach and return to an organisation that rewards the old behaviour. A manager might understand a better process but lack the authority to change it. A team might acquire a useful skill while the surrounding systems make using it unnecessarily difficult.
This is where outcome thinking needs to remain honest.
The more ambitious the promised transformation, the more external variables become relevant.
A trainer can reasonably promise that participants will leave able to perform a particular task under specified conditions. It becomes much harder to promise that an entire organisation will behave differently as a consequence of a two-day workshop.
That does not weaken the argument for outcomes. It makes it more precise.
Good outcome design separates what the training is responsible for from what depends on the environment around it.
That may be one of the most useful disciplines an outcome-led approach creates.
It prevents training from becoming the convenient answer to problems that are actually caused by unclear processes, poor management, missing authority, inadequate systems or conflicting incentives.
Sometimes the honest conclusion is that training is not the intervention required.
That is a valuable conclusion too.
From learning event to practical change
The deeper shift is therefore not from “bad learning objectives” to “good learning objectives”.
It is from seeing training as an event to seeing it as part of a change process.
The event still matters. The content still matters. Learning still matters.
But they sit inside a larger chain of cause and effect.
A participant does not need training because training exists. They need a new capability because something in their work needs to change.
A buyer does not purchase a topic because the topic is interesting. They invest because they believe a meaningful problem can be reduced, a capability strengthened or a result improved.
And a trainer does not create value simply by transferring expertise. The value emerges when expertise is translated into something another person can use.
That translation is where practical transformation begins.
It also provides a more useful way to judge training quality.
Instead of asking only whether the content was accurate, the session was engaging or the participants were satisfied, we can ask whether the intervention made the intended change more possible.
That question is harder.
It is also far more interesting.
Because once we start there, a surprising amount of training practice becomes easier to reconsider: what we teach, how we package it, how we describe it, what we ask participants to practise and even whether training is the right answer in the first place.
The unresolved question for me is how far we should take this.
There is a risk in becoming so obsessed with measurable outcomes that we reduce learning to whatever can be observed immediately. Some valuable learning takes time. Some changes in judgement are difficult to measure. A person can become better at thinking without producing an obvious metric the following Friday.
So practical transformation should not become another rigid formula.
The point is not to force every form of learning into a narrow performance measure. The point is to restore the connection between learning and the reason anyone cared about the learning in the first place.
Perhaps that is the more useful definition of an outcome.
Not a promise of total transformation.
Not a metric invented because a training proposal needs one.
A clear description of what becomes more possible for someone because they learned something they can actually use.
Once that becomes the starting point, training becomes easier to explain, easier to design and easier to value. The subject still matters, but it takes its proper place. It serves the change rather than becoming the change itself.
And that leaves us with a deceptively simple question that is worth asking before another slide is created, another module is written or another training catalogue is published:
What should be different because this training happened?
The quality of the answer may tell us more about the quality of the training than the learning objectives ever could.
Thanks for reading!
Ruben.