Operational Definition

An operational definition states how a concept will be observed, classified, or measured in a particular setting. It turns “fast,” “complete,” or “accurate” into rules that different people can apply consistently. It does not make the chosen rule a perfect representation of the underlying concept.

Take a document-processing workflow in which staff review submitted packets, each packet being the set of documents and fields that make up one submission. To define active handling time, state the start and terminal event, whose work counts, how pauses are logged, and whether verification, corrections, and manual handling when automation fails are included. Specify the unit, aggregation, eligible cases, missing-record handling, and follow-up cutoff.

Two reviewers may agree that 95 of 100 fields in a packet are correct while disagreeing about whether the packet as a whole is acceptable. Field accuracy and packet correctness are different operational definitions. Try the rule on ordinary and ambiguous cases, resolve disagreements, and record revisions before using it to compare results.

The workflow and figures here are illustrative.

References:

• GOV.UK service measurement guidance