Track L&D progress

L&D reporting has settled into a comfortable theatre: completion rates, satisfaction scores, a quote from a happy participant. Everyone in the room knows these numbers measure attendance and mood, not capability, and everyone accepts them anyway, because the alternative, actually measuring whether training changed how people work, has historically been too hard. With AI capability spend climbing across every budget, that bargain has become expensive.

The gap between training and capability has a name in the research literature: the transfer problem. People complete the course, pass the quiz, and return to their desks to work exactly as before, because the workflow, the pressure and the habits are all still there. A capability programme that does not measure transfer is not underperforming; it is unmeasured, which is worse, because it cannot even be fixed.

If the training worked, it shows up in the work. If it only shows up in the LMS, it did not.

There is also the quieter question of where the training went. Capability budgets flow disproportionately to the teams easiest to schedule, not the teams whose work is changing fastest, because without an exposure map nobody can see the difference. Training the wrong teams well produces excellent completion rates and no strategic movement at all.

This programme replaces the theatre with measurement: competency re-measured on a rolling basis against the baseline you set in Discovery, applied usage read from real workflows, and progress mapped against each role's exposure trajectory, so you can prove the budget is building capability where the work is actually changing, and redirect it fast where it is not.