This concept is the operational foundation of Safety II. Understanding the gap between how work is supposed to happen and how it actually happens is where most of the learning lives.
The Illusion of "Process"
Every organization has two parallel realities running simultaneously.
Work-as-Imagined (WAI) is the world that managers, architects, and process designers live in. It is captured in runbooks, architecture diagrams, and onboarding documents. It is clean, linear, and rational.
"To deploy code: the engineer runs the full test suite, gets two peer approvals, and triggers the deployment via the CI/CD pipeline. The pipeline runs integration tests, then promotes to staging, then production."
Work-as-Done (WAD) is what engineers actually do under real conditions — time pressure, ambiguous requirements, flaky tooling, and incomplete information.
"To deploy code: I skip the last three test cases because they've been failing for six weeks and nobody's fixed them. I ask my teammate to click 'Approve' because it's urgent and she trusts me. I use a shell script I wrote six months ago because the pipeline takes 40 minutes and this is a one-line fix."
The Gap is Resilience, Not Deviance
Safety I interprets the WAI/WAD gap as a compliance failure. The engineer broke the rules. The fix is enforcement: more audits, stricter gates, mandatory checklists.
Safety II interprets the same gap as rational adaptation. The engineer is not lazy or reckless — they are compensating for a flawed system to keep the business running. The WAD is evidence that the WAI is wrong.
- Why do they skip the tests? Because the tests are slow, broken, and nobody owns them.
- Why do they use a personal script? Because the official pipeline is too slow for the urgency of the situation.
- Why do they get a rubber-stamp approval? Because the approval process adds no real safety value in this context.
Closing the gap means fixing the system, not punishing the person. Make the safe path the easy path, and engineers will take it.
A common SRE interview question is: "Tell me about a time a process failed." Strong candidates describe a WAI/WAD gap — where the documented process didn't match reality — and explain what they did to reconcile them. Weak candidates describe following the process perfectly and being surprised when it didn't work. The Safety II framing shows you understand that processes are approximations, not ground truth.