What is it?
An Operational Definition states exactly what will be observed or measured, how it will be measured and where the boundary sits. It turns an appealing phrase such as ‘on time’ or ‘defect-free’ into something different people can apply consistently.
What's it really for?
It is a small agreement that prevents larger arguments later. Teams often discover that apparently different results came from different definitions, cut-off points or exclusions rather than different performance.
You know when…
The dashboard says ninety-two per cent on time. Operations count arrival at site, the customer counts usable delivery, and Finance excludes anything still disputed at month end. The number has reached two decimal places before the definition has reached one.
Have a go
- Name the measure or condition. ☐ Describe exactly what counts and what does not. ☐ Specify the method, unit, timing, source and sampling rules. ☐ Add examples near the boundary. ☐ Ask two people to apply it independently and resolve any difference.
Why it works
Words that sound precise often contain several reasonable interpretations. Making the test, method and decision rules explicit reduces variation created by the measurement itself.
Look for…
Terms such as complete, available, urgent, clean and successful; hidden exclusions; judgement at category boundaries; and results that change when a different person collects them.
Watch out…
Do not make the definition so elaborate that nobody can use it. Precision should serve the decision. Record changes, because a revised definition can create an apparent improvement without anything in the work changing.
Worth noticing…
The most useful example is often the awkward case sitting exactly on the boundary. That is where polite agreement tends to end.
Try next…
Use a Check Sheet to collect consistently defined observations. Use Measurement System Analysis when disagreement or instrument variation needs testing. Use a CTQ Tree to connect the measure to customer need.