CONTACT US
Sign In
CONTACT US

From courses to capability: Intentionally different

Aug 25, 2026 | Education

Team members collaborating in a practical workplace learning session

From courses to capability

“Learning in the flow of work” gets used so often now that it has started to lose its edges. For many teams it has become shorthand for shorter modules, mobile-friendly content, or anything a person can finish in a few spare minutes between meetings. That is a problem, because it confuses format with function. You can make content smaller without changing its relationship to work at all. What the phrase actually points to is learning that cannot be separated from performance. Not something scheduled before work, or bolted on after it, but something that happens inside the task itself. A decision made under pressure. A conversation that forces someone to rethink their approach. A moment of uncertainty that, handled well, shifts how a person operates the next time around. These are not interruptions to a development plan. They are the development. If that framing holds, it significantly disrupts and challenges a lot of what L&D teams are historically set up to do. The job stops being about building and making available content and starts being about shaping the conditions in which people can learn while they work.
olleagues discussing ideas during a workplace learning session

Most formal learning is designed as though people will sit with it in a calm, unbroken stretch and then carry it neatly into their next challenge. That almost never happens. Work is fragmented. Priorities shift mid-week. Decisions have to be made before all the information is available. This is especially true in leadership and government roles, where the stakes of getting it wrong are real and the luxury of waiting for certainty does not exist.

Courses tend to front-load knowledge that only becomes useful much later, and even then, only if the learner can bridge the gap between what they studied and what they are facing. That bridge is rarely as short as designers assume.

Completion data makes the gap harder to spot. A finished module shows up as progress in a dashboard but finishing something and actually using it are not the same thing. We have built evaluation systems that are very good at tracking activity and much less good at asking whether anything changed as a result. That is not a minor blind spot. It is a structural one. None of which is an argument against structure. It is an argument against structure that does not account for how work actually feels from the inside. There is a useful shift that happens when you stop treating friction as something to remove and start treating it as something to design around. The moments that feel hardest at work, where the evidence is incomplete, where two stakeholders want opposite things, where a conversation veers somewhere you did not expect, are exactly where learning gains traction. A policy decision made with imperfect data teaches more about judgement than a case study ever will, provided there is something in the workflow that helps the person pause and make sense of what just happened.
That changes the design question. Rather than asking what someone needs to know, you ask what they need to do differently, and when in their working week that behaviour matters most. The answer almost always points to a specific moment rather than a general topic. A prompt that arrives at the right decision point. A structured reflection completed within an hour of a difficult meeting. These small, well-placed interventions tend to outperform entire courses consumed months in advance, because they meet the learner inside the problem rather than before it. Social learning follows the same logic. Professional judgement does not develop in isolation. It sharpens when people see how others are thinking through comparable problems. But peer interaction only works when it has some structure around it. Left open and undirected, forums tend to either drift into polite generality or fall silent altogether. What produces real value is a specific question, a clear timeframe, and enough diversity in the group for people to encounter thinking that genuinely differs from their own.
Team members sharing ideas and learning together in a group discussion
When someone working in state health sees how a counterpart in a federal regulatory body weighed up a similar resource allocation problem, the point is not to copy the answer. It is to notice where the reasoning differs and why. That kind of calibration, learning where your own assumptions hold up and where they need adjusting, cannot be delivered through content. It has to happen through exchange.

Reflection ties all of this together, and it is the piece that gets dropped most often. Without it, experience piles up but never converts into learning. People repeat patterns without examining them. Decisions get made and moved past without anyone stopping to ask what worked. The issue is not that practitioners think reflection is pointless. It is that nothing in their day creates space for it. Effective reflection has to be timely, close enough to the moment of action that the detail is still fresh. It has to be specific, aimed at one decision or behaviour rather than a vague sense of how the week went. And it often has to be at least semi-private, because the honesty that makes reflection useful does not always survive a group setting. Treated as a performance tool rather than a feel-good exercise, reflection earns its place. Treated as an afterthought, it gets skipped.

Colleagues having a one-to-one workplace learning conversation

A few common mistakes are worth exploration. The most widespread is treating “flow of work” as a content format, just shorter videos and quicker reads. Another is stripping out all structure in pursuit of flexibility, which tends to leave learners without enough scaffolding to sustain their own development. A third is placing too much weight on individual motivation without asking whether the environment actually supports what you are expecting people to do. And there is still a persistent belief that the right platform or tool will solve what is fundamentally a design problem. Technology enables. It does not replace the thinking.

This cannot sit on the learner’s shoulders alone. It needs environments where learning is treated as part of the job rather than something extra. It needs time for reflection and discussion that is genuinely protected, not just encouraged in a strategy document. And it needs lightweight structures that sit alongside existing workflows rather than pulling people out of them. Where those conditions do not exist, individual willingness runs out fast.
Measurement is the hardest part, and probably the least resolved. Traditional metrics tell you what people did. They do not tell you whether it mattered. Better signals exist, things like shifts in decision quality over time, growing confidence in ambiguous situations, evidence of applied thinking showing up in real work outputs, but they require qualitative interpretation and a willingness to sit with incomplete data. That is uncomfortable for organisations that want clean numbers, but it reflects the reality of how capability actually develops. The most useful framing is probably developmental rather than evaluative: measurement that informs the next design iteration, rather than measurement that tries to prove the last one worked. There are tensions running through all of this that are not easy to resolve, but absolutely need consideration. Structure against flexibility. Speed against depth. What the individual can do against what the system allows. Learning against the immediate pressure to perform. The goal is not to make learning invisible inside work, it is to notice where development is already happening, and make it feel more supported, more visible, and much more useful than it would have been if nobody had paid attention. Real learning is inseparable from performance, triggered by real need, and resolved through action rather than consumption. Learning is work, and the more organisations consider it as such, the desired culture of reflective practice leading to better outcomes for all will follow. Craig Crowther CEO Cahoot Learning

Keep up-to-date, subscribe to our newsletter today

Simply complete the form.

Subscribe to our newsletter

Get the latest Cahoot Learning news, fresh thinking on workplace capability, early access to new products and invites to upcoming events.

Thank you for subscribing to our newsletter.