Contents
Everything here, in eight sections. If you are scoping a programme, read the foundations first. If individual measurement is being proposed, read the section on monitoring people before the section on technology.
Foundations
6 notesThree different things share the name: measuring a process, tracking equipment, and watching people. They need different justifications, and most of the value is in the first two.
What to measure
9 notesOutput per person is easy to compute and explains little. The measures that explain performance are about waiting, travel and variation — and all of them are aggregate.
Capturing the data
7 notesMost facilities already generate more than they use. What each source sees, what it misses, and the data quality defects that produce confident wrong answers.
Monitoring people
8 notesAttributing measurement to a named person is workplace surveillance with obligations attached, and it costs the cooperation that determines whether any of the data is accurate.
Safety
5 notesThe clearest justification in the field, and the place where monitoring is most often substituted for the physical control that should have been there.
Making sense of it
5 notesMost of the errors in this field are analytical rather than technical. Reacting to ordinary variation, comparing without normalising, and producing findings nobody acts on.
Running a programme
6 notesNinety days without a purchase, then buying for the gaps you named. Plus the failures that recur, each visible early and each with a specific correction.
Reference
4 notesSafety, data protection and employment law all apply and pull in different directions. Plus the boundary: questions the data cannot answer, and what to use for each instead.