1. What this stage is for
Measure tracks learning, behaviour, workflow, business and workforce outcomes, and asks how much of any change was caused by what you did. It was set up in Define, when the success conditions and baseline were written down; it runs alongside Support for as long as the change matters; and it feeds Adapt, which decides what to change next. #10 · #14 · IDE-DES-07
Measurement goes wrong in two predictable ways. The first is measuring what's easy instead of what matters: satisfaction scores, completions, logins, hours logged. These are cheap to collect and almost never answer the question leaders actually ask, which is whether the work got better. The second is measuring the right thing badly: a before-and-after comparison that ignores everything else that changed, a baseline taken at the worst month, or a return on investment built on assumptions nobody would defend. LSC-MSR-01 · DGN-BSL-01 · IDE-EV-12
A useful standard: a measurement is good enough when a sceptical finance director could read how it was done and agree with the conclusion, or see exactly where the uncertainty lies. That's achievable for most organizations with records they already keep. It rarely needs a new platform; it needs a plan made before the change starts. LSC-ORG-03 · IDE-EV-08
2. Measure at the right level
Evaluation is usually described in levels: how people reacted, what they learned, whether they apply it at work, what changed in the business, and whether the return justified the cost. Each level answers a different question, costs more to measure than the one before, and moves on a longer timescale. Not every programme needs every level. Set evaluation targets by level, and choose the deeper levels for programmes that are strategic, expensive or highly visible. IDE-EV-01 · #10
Targets from published evaluation methodology, not research findings. The learning-level target rose over time; the deeper levels stayed about the same. IDE-EV-01 · IDE-EV-10
At the reaction level, ask the right question. How much people enjoyed training barely predicts anything; how useful they judged it predicts on-the-job use better than test scores do. Replace "how did you like it?" with "how are you using this in your current work?" LSC-MSR-02 · LSC-MSR-01
At the learning level, test performance on new, job-like tasks without aids, and test again after 30 to 90 days. Immediate tests mostly capture what people can do while the training is fresh. LSC-MSR-03 · LSC-MSR-04
At the application level, measure once the new behaviour should be routine, often three to six months after training rather than a fixed few weeks. Measure behaviour separately from knowledge: people can know the right answer and still not do it. IDE-EV-02 · GL-14
At the impact level, use the records you already keep. For technical work, that means quality defects, design-attributable RFIs, rework hours, time to a first independent deliverable, near-miss reports and close-out time. For digital adoption, measure the workflow itself: models issued on time, clash cycles, digital daily reports. LSC-ORG-03 · IDE-AEC-02 · QMS-COQ-03
3. Measurements you can believe
The hardest part of measurement is not collecting numbers; it's knowing what caused them. Projects rarely run in a vacuum: a new manager arrives, the market shifts, a difficult client finishes, the season changes. A before-and-after comparison can't separate the change's effect from all of that. IDE-EV-03 · LSC-MSR-05
Isolate the effect with a comparison group first. The best comparison is often free: a staggered rollout, where the teams or offices that haven't started yet act as the comparison for those that have. Where no comparison is possible, use trend lines or forecasts, and only then fall back on estimates from participants or managers, adjusted for how confident they say they are. IDE-EV-03 · LSC-MSR-05 · IDE-AEC-02
Get the baseline right. Never baseline at the moment the problem was noticed, because problems get noticed at their worst and tend to drift back toward normal on their own, which flatters any fix. Use several measurements from before the change, covering at least one full operating cycle, and say why the window was chosen. DGN-BSL-01 · DGN-BSL-04 · QMS-LSS-05
Prefer objective records to self-reports. Self-rated confidence inflates results, and so do self-assessment scores used as key performance indicators: people learn to score well. Where you must survey, read the results as perception data, and check survey timing against recent events. LSC-MSR-05 · BM-MAT-02 · BM-EVD-02 · DGN-DATA-01
Measure speed from telemetry, not opinion. When people are asked how much faster an AI tool makes them, the answer and the measurement often disagree, and in one controlled study experienced developers on familiar code were slower with AI assistance while believing they were faster. Measure the speed-up; don't ask about it. PRM-EVD-08 · SWD-AI-03 · SWD-AI-02
4. Indicators that mislead
Some indicators are so convenient that they survive long after their weaknesses are known. Learn to recognize them, and keep them out of the headline. SOP-GOV-10 · CM-EVD-01
| Indicator | What it really measures | Use instead |
|---|---|---|
| Satisfaction 4.7 out of 5 | How pleasant the course felt | Unaided performance on a job-like task, later |
| Logins or licences active | Access, not use | Workflow steps running the new way |
| Recordable injury rate | Mostly minor, reported injuries | Leading indicators and major-hazard precursors |
| Percent complete by hours spent | Effort consumed | Physical progress against rules agreed in advance |
| Badge swipes | Attendance | Sensor or observation data on actual use |
| CPD hours logged | Compliance | Competence shown on the work |
| Projected savings | A model's prediction | Measured savings, with measurement and verification |
None of these is useless; each is fine in its own lane. The harm comes from reading one as the other. LSC-MSR-01 · CM-DIG-03 · SOP-GOV-04 · PCF-EVM-01 · FAM-SPC-01 · LSC-CPD-01 · FAM-TWN-06
Two cautions about safety measures in particular. First, retire the recordable injury rate as the headline safety measure, and track leading indicators alongside it. Second, keep personal-safety and process-safety indicators separate: at Texas City, a very low injury rate gave a misleading picture of the risk of a major accident. Correct injury counts for under-reporting before trending them, especially where anyone's bonus depends on the count. SOP-GOV-04 · CM-SAF-02 · DGN-BSL-02 · DGN-BSL-03
Don't turn measures into targets or league tables. Delivery metrics in software, for example, are useful for a team to understand itself and harmful when used to rank teams, because people optimize the number rather than the work. Track speed and stability separately, and use several measures of productivity rather than one. SWD-MET-04 · SWD-MET-05 · SWD-MET-06 · SWD-MET-02
Measure quality locally, with definitions people agree on, and read every number in context. A defect rate that rose because inspection improved is good news that looks bad. QMS-ARC-04 · SOP-GOV-10 · DM-STD-04
5. Money, honestly
Leaders increasingly ask for the financial return on training and change, and most organizations can't answer. In one survey, nearly all chief executives wanted to see the business impact of training, but fewer than 1 in 10 received it. The usual barriers are isolating the effect and getting the data, which is why the data connections should be set up before leaders ask. IDE-EV-11 · IDE-EV-10
When return on investment is calculated, it's often inflated. Very high published figures usually come from counting several years of benefit, using undiscounted estimates, counting revenue instead of margin, or treating freed time as cash. Applying conservative rules to one widely circulated example turned a claimed return of about 540% into about 70%. IDE-EV-12 · IDE-EV-04
Seventy per cent in a year is still a good return. The problem with 540% isn't that it's too high; it's that nobody could defend how it was reached. IDE-EV-04 · IDE-EV-07 · IDE-EV-08
A defensible financial evaluation follows a few rules:
- Count the first year of benefit for short-term programmes; if you claim more, show the decay and the discount rate. IDE-EV-04
- Agree unit values with finance, and show how freed time becomes money. A saved hour is only worth money if it's billed or the cost actually goes away. IDE-EV-05
- Report quality and side effects alongside productivity. Faster work with more rework isn't a gain. IDE-EV-06
- Publish a range and a break-even point, not one figure: how much of the improvement must the change cause to pay for itself? IDE-EV-07
- Disclose the method: scope, comparison, baseline, values, horizon, costs, sensitivity and who checked it. IDE-EV-08
For complex programmes, such as leadership development, the Success Case Method is often cheaper and more convincing than a full return calculation: study the people for whom the programme worked best and worst, and find what made the difference. IDE-EV-09
6. Forecasts and controls
Measurement covers forecasts and controls too, and both are easier to fool yourself about than training results. Score forecasts and feed the results back. When estimators record a probability for a milestone, a cost or a risk, scoring it once the outcome is known shows who is calibrated, not just who was right. Used to punish, scoring makes people hedge toward 50%; used for feedback, it improves forecasting. Measure who is optimistic, too: in finance teams, a forecaster whose numbers are always high is valuable information. DQ-LRN-01 · FIN-FPA-02 · DQ-LRN-05
On projects, measure progress physically, with rules agreed in advance, never by hours or money spent. Treat an early bad cost index as a warning that rarely improves much later; the forecast it implies is a floor, not a ceiling. Keep an independent forecast beside the team's, and report forecasts as ranges with a stated confidence. PCF-EVM-01 · PCF-EVM-02 · PCF-EVM-04 · PCF-FC-01 · PCF-FC-03
For controls and governance, measure whether controls operate, not whether policies exist. A policy that says access is reviewed quarterly is not evidence that it was. For savings claims from energy, maintenance or digital-twin projects, require measurement and verification: projected savings are not measured savings. AIG-16 · FAM-NRG-03 · FAM-TWN-06
Use the right tool for repetitive measurements. Statistical process control charts suit repetitive, frequently measured processes, such as a production line, but not one-off construction activities; expect false alarms, and more of them as you add rules. QMS-SPC-01 · QMS-SPC-03
7. By team: what to measure
Most teams already collect the data they need. The skill is choosing the measures that reflect the work and reading them honestly. LSC-ORG-03 · SOP-GOV-10
Technology and software teams
Use the current delivery metrics, labelled with the year their definitions come from, and measure them from your own systems rather than surveys. Read published performance tiers as descriptions, not benchmarks, and don't turn the metrics into team rankings. Retire the mean time to restore as a headline metric; it's dominated by a few long incidents. Code health is worth tracking, because it predicts defects and delivery speed. SWD-MET-01 · SWD-MET-03 · SWD-MET-02 · SWD-INC-08 · SWD-TD-03
Project and construction teams
On projects, measure physical progress, Percent Plan Complete as an early warning, leading safety indicators, rework and the cost of your own nonconformances. Measure coordination value yourselves, by tracing resolved clashes to the RFIs and change orders they prevented, and measure contract value loss from your own ledger rather than an industry figure. PCF-EVM-01 · CM-LEAN-02 · CM-SAF-02 · QMS-COQ-03 · BM-COO-05 · VCM-ADM-03
Plants and facilities
In manufacturing, define equipment effectiveness and other key indicators the standard way, capture machine state automatically, and pair effectiveness with throughput so one isn't improved at the other's expense. In buildings, track a few maintenance indicators against simple targets, define a space-metric stack before comparing utilization figures, and remember that badge swipes are attendance, not use. DM-STD-04 · DM-SUS-03 · FAM-MNT-03 · FAM-SPC-02 · FAM-SPC-01
Learning and people teams
For training, measure performance on new, job-like tasks, re-test after 30 to 90 days, use comparison groups and objective records, and treat licensure hours as a compliance floor. For engineering firms, the records that already exist, such as quality defects, design RFIs, rework hours and time to first independent deliverable, are better outcome measures than any survey. LSC-MSR-03 · LSC-MSR-04 · LSC-MSR-05 · LSC-CPD-01 · LSC-ORG-03
AI initiatives
For AI tools, test prompt and model variants on many real examples, calibrate any AI-as-judge against people, measure speed-ups with telemetry, and know which adoption figure you're reading: "uses AI weekly" and "relies on AI for a core process" are very different numbers. PRM-EVD-04 · PRM-VER-06 · SWD-AI-03 · DM-AIM-05
An illustrative example
A mechanical contractor's new onboarding programme scored 4.7 out of 5 for satisfaction. The finance director asked whether apprentices could actually do the work. The training lead compared weld reject rates, spool rework and unaided performance on a new spool at day 90 for three groups: last year's cohort, this year's, and a small group that started later and was trained the old way. This year's cohort did noticeably better on all three, and the report said plainly that the groups were small and the results encouraging rather than conclusive. That honest framing is what made the board fund the programme again. LSC-MSR-05 · LSC-MSR-03 · IDE-EV-07
Common mistakes
- Satisfaction or logins as the headline. LSC-MSR-01 · CM-DIG-03
- Before-and-after with no comparison. IDE-EV-03
- A worst-month baseline. DGN-BSL-01
- One ROI figure with no method. IDE-EV-08
- Measures turned into league tables. SWD-MET-04
8. Handing it on
Measure hands Adapt evidence: what changed, at which levels, compared with what, and how sure you are. It should include what didn't change and what you couldn't measure, because those are often where Adapt's best questions come from. DGN-CNS-01 · #64
Run and share your own evaluations. Engineering, construction and manufacturing have very little controlled evidence about their own training and adoption programmes. A well-designed evaluation, shared with a trade association or professional body with its limits stated, adds to what the whole sector knows. LSC-MSR-06 · LSC-CPD-05
Feed the results into decisions, not reports. Measure IT performance and business benefits separately, and feed both into the next portfolio cycle; track benefits against the owners named in Define. A measurement that never changes a decision wasn't worth collecting. ITG-VAL-01 · ITG-VAL-02 · OGV-BIZ-02
For small organizations, a credible evaluation fits on a page: one business measure from records you already keep, a baseline from several months before, the teams that started later as a comparison, a check at three months, and an honest sentence about what else might explain the result. LSC-ORG-03 · IDE-EV-03
The checklist. Plan the measurement in Define. Evaluate by level, deeper for what matters most. Ask about usefulness, not enjoyment. Test unaided, later. Use a comparison group, often a staggered rollout. Never baseline at the worst month. Prefer records and telemetry to opinion. Keep satisfaction, logins and injury rates out of the headline. Report money as a first-year range with the method shown. Score forecasts; measure that controls operate. Share what you learn. Then go to Adapt.