Every learning function measures satisfaction. Most measure completion. Very few can answer the question a finance director actually asks: did any of this change what people did at work?
The reason is not lack of interest. It is that application evidence has to be designed in from the start, and most programmes are designed to end on the last taught day.
What counts as evidence
Evidence of application is a work product that could not exist unless the method was used on a real problem. On our pathway that means things like a challenge statement framed with stakeholders, an assumption map with the riskiest assumption identified, a prototype and the result of testing it, a prioritised backlog, a current-state and future-state process map, a delivery roadmap with a governance model, or a facilitation design and an observer’s notes from running it.
These are not essays about learning. They are the learning, made visible. A reflective review sits alongside them so the participant records what they concluded and what they would do next.
The Capability Portfolio
We organise this into six steps. Profile: where the person starts and what their role needs. Prepare: the live challenge and its stakeholders, confirmed by a sponsor. Apply: the methods used on the challenge during and after the programme. Evidence: the work products recorded. Reflect: the short review. Progress: assessment, recognition and the recommended next stage.
Two design principles keep it from becoming a bureaucracy. First, the evidence is the work itself, not a report about the work. If a team produced a prototype, the prototype goes in. Second, assessment is light and fast: an assessor reviews the evidence against a short standard and gives feedback within days.
What sponsors receive
At cohort level, a sponsor sees which challenges were worked on, which work products exist, what decisions were made and which people earned recognition. At academy level, a dashboard shows participation, certification, challenge outcomes and benefits across the organisation.
This changes the conversation with the board. Instead of “we trained 400 people”, the capability lead can say “400 people worked on 120 challenges, 85 produced tested prototypes, 30 solutions moved into delivery, and here are the benefits we are tracking”.
Starting small
You do not need an academy to begin. A single cohort with sponsored challenges, a simple portfolio template and one assessor is enough to produce the first evidence. Once sponsors have seen it, the case for scale makes itself.