# Deterministic work standard

> A deterministic work standard replaces rule-of-thumb execution with a measured, written method that produces the same result from the same inputs, so quality does not depend on which individual happened to do the work.

Category: Operations
Also searched as: scientific management, standard work, replacing rule of thumb
Source: Mediator Solutions — https://mediatorsolutions.io/learn/#deterministic-work-standard
License: free to read, learn, cite, and apply, with attribution to Mediator Solutions.

## What it is

When a task is done by habit and intuition, its result varies with the person and the day, and the variance is invisible until it fails. A deterministic work standard studies the task, writes the method that reliably produces the right result, and makes that method the default — so the outcome is a property of the process, not of who was on shift.

## Why it matters

When a task runs on habit and intuition, its quality varies with the person and the day, and the variance is invisible until it fails at the worst time. A written standard makes the result a property of the process rather than of who was on shift. The counter-intuitive discipline is that the standard is improved by measurement, not by exhortation — telling people to try harder against an unwritten method just hides the variance longer, while a written method makes deviation visible and improvement testable.

## When to use it

- A task runs on habit and intuition and its quality varies with who does it.
- You want a result to be a property of the process, not of who was on shift.
- Variance in an output is invisible until it fails at the worst time.

## Principles

- Replace rule-of-thumb execution with a measured, written method.
- The result should be a property of the process, not of the individual who ran it.
- A standard is evidence: it states what good looks like and how it is checked.
- Improve the standard with measurement, not with exhortation to try harder.

## Practice

1. Study the task as actually performed and record what produces the good result.
2. Write the method so another person produces the same result from the same inputs.
3. Make the written method the default and measure adherence and outcome.
4. Revise the standard when measurement shows a better method, not by appeal to effort.

## Where it fails

- **Intuition variance** — Quality rides on the person and the day, so the output varies invisibly until it fails under load.
- **Exhortation-not-method** — People are told to try harder against an unwritten method, which hides variance instead of reducing it.
- **Unexamined drift** — With no written standard, deviation is invisible, so the method erodes without anyone deciding it should.

## In practice

Two analysts produce the same report; one is reliably right and one is occasionally wrong, and no one can say why because the method lives in their heads. The standard writes the method down: the inputs checked, the order of operations, the validation at each step. Now the result is a property of the process, deviation is visible, and improvement is testable — you change the standard and measure, rather than telling people to be more careful against a method no one can see.

## Verification

Two different people, following the written standard from the same inputs, produce the same result, and deviations are visible against the standard rather than hidden.

---

Previous: https://mediatorsolutions.io/learn/#leverage-and-throughput
Next: https://mediatorsolutions.io/learn/#operational-time-allocation