The Field Guide to Understanding 'Human Error'

by Sidney Dekker · 6 ideas

  1. Old View vs New View

    The old view treats human error as the cause of failure and tries to remove the "bad apples". The new view sees error as a symptom of deeper problems in tools, pressures and design. Replacing people leaves those problems in place, so fix the system instead.

  2. Local Rationality

    People do what makes sense to them at the time, given their goals, knowledge and focus. Nobody comes to work planning to fail. When something goes wrong, ask why it made sense to them, not why they were careless.

  3. Counterfactuals

    Saying what someone "should have done" explains nothing about why they did what they did. It only describes a path that wasn't taken. Drop "should have" and describe what actually happened and why.

  4. Work as Imagined vs Work as Done

    Procedures describe how work should go, but real work always needs adapting to messy conditions. That gap is normal and often how things get done at all. Study it to learn how work really happens, instead of punishing it.

  5. Blame Drives Errors Underground

    When mistakes get punished, people stop reporting them. Problems don't disappear, they just become invisible until they cause something serious. Make it safe to speak up, so you hear about trouble early.

  6. Drift

    Systems slide toward failure through many small, normal compromises that each seem reasonable. Every step looks fine on its own, so nobody notices the margins shrinking. Watch for slowly eroding safety buffers, not just dramatic mistakes.

More on systems