Ask a learning director what happened after last year’s innovation programme and the honest answer is usually the same. People enjoyed it. The feedback scores were good. A few teams tried something. Then the quarter got busy and the workbook went in a drawer.
That is not a failure of the participants or the facilitator. It is a failure of design. A course is designed to transfer knowledge. Capability is something different: the ability of an organisation to do a hard thing repeatedly, with its own people, to a standard it can evidence. Knowledge is a necessary input. It is nowhere near sufficient.
What capability actually consists of
When we look at organisations that solve complex problems well, four things are always present.
People in specific roles can do specific things. An ambassador can frame an early challenge. A practitioner can take it through research, prototyping and validation. A facilitator can design and run the session that gets a room to a decision. A leader can prioritise a portfolio and govern it.
There is a shared process. Not a rigid one, but a common vocabulary and sequence that lets a team in one department work with a team in another without renegotiating the method each time.
There is evidence. Framed challenges, stakeholder maps, tested prototypes, experiment results, backlogs, roadmaps and benefits reports exist as artefacts, and sponsors can see them.
And there is governance. Somebody decides which challenges matter, what evidence is required before money moves, and when to stop.
A two-day course touches the first of these, for one role, for two days. It cannot touch the other three. Which is why we design programmes as one connected system rather than a catalogue.
Five design choices that make learning transfer
The first choice is to work on live challenges. Every cohort brings problems the organisation needs solved. The learning happens on the way to a result, and the result is the evidence that the learning took place.
The second is to assess application, not attendance. Certification on our pathway is awarded after a workplace application has been completed and reviewed. This is unpopular with people who want a certificate for turning up. It is popular with sponsors.
The third is to build role-based routes through a common foundation. Everyone starts in the same place. Ambassadors stop early. Practitioners go through the full process. Facilitators and leaders go further. Nobody sits through a module designed for somebody else.
The fourth is to develop internal facilitators from the start. The measure of a capability engagement is whether the organisation can run the next cycle without us. If it cannot, we have sold training and called it something else.
The fifth is to embed AI in every stage rather than bolt on a masterclass. Research synthesis, ideation, prototyping, analysis, backlog development and portfolio scenarios all move faster with AI in the loop. The judgement stays with the people who are accountable for it.
What this means for a buyer
If you are responsible for capability, the question to ask a provider is not “what will people learn?” It is “what will people have done, and how will I know?” A good answer names the work products, the assessment, the internal roles that will exist afterwards and the report the sponsor will receive.
That is the standard we hold ourselves to. It is also the reason we describe what we do as capability rather than training.