Design Pattern · 2026-09-15
Design out the memory dependency
For each control that depends on a person recalling guidance under pressure, look for a technical arrangement that makes the safe action the default or the only one.
Under the pillar Human error without human blame
The pattern
List the behaviours the security program currently asks staff to remember. For each, ask what would have to be true for the wrong action to be impossible, expensive, or automatically reversible. Some will have no technical answer, and those are where training belongs.
The list is usually short once it is written down, which is itself informative about how much of the program rests on memory.
Put this to work
Design out the memory dependency application record
Apply Design out the memory dependency to a real piece of work and record what happened.
- For
- Practitioners, researchers, founders, and operating leaders.
- What you keep
- A design out the memory dependency application record you can review, revise, and send.
- What counts as sound
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop
The result is a working analysis. Check it against source evidence and qualified judgment.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.