When we work with experienced practitioners to design learning programs, one thing becomes clear very quickly — they don’t naturally “teach” in the way most programs expect.
They don’t think in modules.
They don’t structure their knowledge into frameworks.
They don’t start with definitions and build upward.
Instead, they talk about situations.
What happened. What went wrong. What they chose to do — and why.
And yet, despite the lack of structure, people often learn more from them than from perfectly designed content.
The Design Gap
This creates an interesting challenge from an instructional design perspective.
Most learning programs are built around clarity and structure:
- concepts
- models
- step-by-step explanations
But experience doesn’t exist in that format.
It exists in fragments:
- moments
- decisions
- trade-offs
- corrections
The role of design, then, is not to force structure onto experience — but to understand how learning is actually happening when practitioners share what they know.
What We Consistently Observe
Across programs, a few patterns show up consistently when practitioners engage with teams.
1. They Teach Through Stories, Not Slides
When practitioners explain something, they rarely start with a concept.
They start with a situation.
“We faced something similar a few years ago…”
“In one of our plants…”
“What typically happens in this case is…”
These stories carry more than just information. They bring in context — constraints, ambiguity, and real consequences. From a design standpoint, this is critical. Because context is what makes learning usable.
2. They Teach Through Decisions, Not Frameworks
Practitioners don’t just describe what happened.
They explain what they chose to do — often between imperfect options.
“We had two choices…”
“We could have gone ahead, but decided to hold…”
This is where real learning happens.
Not in knowing the “right answer”, but in understanding:
- how trade-offs are evaluated
- how priorities are set
- how decisions are made under constraints
This is difficult to capture in traditional formats, but essential for building capability.
3. They Teach Through Corrections, Not Assessments
Another consistent pattern is how practitioners respond to others.
They challenge assumptions.
They point out blind spots.
They reframe problems.
“That’s not the issue — the issue is…”
“You’re focusing on the symptom, not the cause…”
These moments are rarely planned.
But they are often where the most meaningful learning happens.
Because learning, in practice, is less about being tested — and more about being corrected.
4. They Teach Through Context, Not Abstraction
Practitioners rarely speak in generalities. They anchor everything in:
- specific environments
- real constraints
- actual conditions
This makes their input immediately relevant.
It answers not just:
– what should be done
But:
– what can be done here
And that distinction matters.
What This Means for Learning Design
If the goal is to build real capability, then learning design has to adapt to how experience is actually shared.
This means:
- Designing around situations, not just concepts
- Bringing out decisions and trade-offs, not just best practices
- Allowing space for interaction and correction, not just delivery
- Preserving context, instead of over-simplifying it
In many cases, the job of the instructional designer is not to structure content — but to extract and shape experience in a way that others can engage with.
Bridging Experience and Learning
This is also why learning led by experienced practitioners tends to have a very different impact.
It brings in:
- context
- judgment
- real-world nuance
— elements that are difficult to replicate in more traditional formats.
At Huksa, this belief sits at the core of how we design learning experiences — grounded in real-world expertise and focused on building capability that shows up in the work.
Some of the most valuable learning doesn’t come from being taught in a structured way. It comes from exposure — to how experienced people think, decide, and act in real situations. The role of design is not to make practitioners “teach better”.It is to make their experience usable for others.
