Learning Measurement Playbook

Prove learning impact with metrics finance and operators will respect.

Format

Playbook · ~10 minutes

Audience

L&D leaders and analytics partners

Output

Metric set + baseline plan + review cadence

Measurement is where learning programmes win or lose credibility with finance and operators. This playbook keeps the set small, ties it to outcomes you can defend, and builds a review rhythm so numbers do not replace judgement.

Frame

Pick three layers, not thirty metrics

Kirkpatrick still helps when you use it as a conversation scaffold, not a scorecard. Most programmes need one signal at each layer: reaction and intent, behaviour or workflow change, and one business-aligned outcome.

Reaction: did the right people complete it and say it was relevant.
Application: did behaviour or process change in the work environment.
Outcome: did a lagging indicator move that leaders already track.

Model

Baseline before you promise uplift

Finance partners listen when you show the starting point and a conservative expected change. If you cannot baseline, you are not ready to claim ROI. Pair qualitative manager quotes with one or two numbers.

Name the business problem the programme sits against.
Capture baseline for one efficiency, quality, or speed measure where learning is a plausible lever.
Document assumptions so a sceptic can challenge one number without collapsing the whole story.

Govern

Review on a fixed cadence and decide scale, adjust, or stop

The failure mode is measuring once at the end and calling it done. Agree upfront who owns the metric, where the data lives, and the date of the first honest review.

30 days: leading indicators and completion quality.
90 days: early behaviour or workflow evidence.
120 days: first read on business outcome, with a clear decision.

Pick three layers, not thirty metrics

Reaction: did the right people complete it and say it was relevant.

Application: did behaviour or process change in the work environment.

Outcome: did a lagging indicator move that leaders already track.

Baseline before you promise uplift

Name the business problem the programme sits against.

Capture baseline for one efficiency, quality, or speed measure where learning is a plausible lever.

Document assumptions so a sceptic can challenge one number without collapsing the whole story.

Review on a fixed cadence and decide scale, adjust, or stop

The failure mode is measuring once at the end and calling it done. Agree upfront who owns the metric, where the data lives, and the date of the first honest review.

30 days: leading indicators and completion quality.

90 days: early behaviour or workflow evidence.

120 days: first read on business outcome, with a clear decision.