In the current discourse of work and technology, “resilience” is the ultimate virtue. We celebrate the doctor who powers through a clunky EHR, the pilot who manages a chaotic dashboard, and the citizen who has to fight a benefits portal for what they are owed.
We have built an entire industry of thought leadership (management theory, psychology, tech design) dedicated to making the human operator tougher, faster, and more adaptable.
View source
%% title: Who supplies what the software lacks
%% caption: When software cannot handle ambiguity or keep track of state, the operator supplies the memory and patience, and the strain shows up as burnout.
flowchart TD
classDef actor stroke-width:1.6px;
classDef system stroke-width:1.2px;
classDef gate stroke-width:1.6px;
classDef binding stroke-width:3px,font-weight:bold;
classDef status stroke-dasharray:4 3;
classDef burden stroke-width:2px;
classDef repair stroke-width:2.4px,font-weight:bold;
classDef failure stroke-width:2.2px,stroke-dasharray:6 3;
S["System software / interface"]:::system --> A{"Unresolved ambiguity<br/>Missing memory / error"}:::gate
A -- "unhandled by design" --> T["Friction transfer<br/>Resource subsidy"]:::burden
T --> U([Operator nervous system]):::actor
U --> C["Supplies memory, patience & metabolic energy"]:::repair
C --> M([Apparent system stability]):::status
U --> B([Cognitive burnout / insolvency]):::failure
To an industrial hygienist, this obsession with resilience is a symptom of structural failure.
Resilience is a subsidy. It is a tax the user pays to cover the cost of lazy engineering.
When a system fails to resolve ambiguity, manage memory, or handle errors, it borrows stability from the user. The user supplies the memory, the patience, and the metabolic energy to bridge the gap. The institution’s books balance because your nervous system covers the shortfall.
Building safe systems means dismantling the dominant myths that allow institutions to offload their maintenance costs onto us.
Grit and antifragility mistake friction for training
Angela Duckworth’s Grit holds that perseverance and passion for long-term goals are the primary predictors of success. Grit is a valid virtue for intrinsic pursuits (learning the violin, training for a marathon). It is a toxic metric for extrinsic friction (deciphering a billing code).
When we demand “grit” from a nurse struggling with a medication dispenser, we are committing a category error. We are treating a logistics problem as a test of character. The “grit” required to endure bad software measures Failure Demand. Every ounce of grit spent fighting the interface is a tax paid on behalf of a vendor who didn’t finish the design.
Nassim Taleb’s Antifragile holds that systems (and organisms) benefit from shocks and disorder and should get stronger under stress. Taleb’s physics were worked out for evolutionary systems, and they break when carried over to administrative ones. A muscle grows when torn; a distinct cognitive process degrades when fragmented. Design for cognitive scarcity starts from the same fact: attention and bandwidth are finite, and options that exist on paper are unusable in practice for anyone already at capacity.
Administrative burden behaves like a thermodynamic system, and the resemblance is an analogy rather than a law. It produces Entropy (waste heat), and no amount of it adds up to Hypertrophy (growth). When a user faces high-frequency interruptions — demands that outpace what the person can absorb between them — they do not become “antifragile”; they become cognitively insolvent. Applying this logic to UX justifies negligence by framing burnout as a failure to adapt to chaos. Individual support still has worth: a useful coping tool helps the person who uses it, and it does not discharge the obligation to change the conditions that made the coping necessary.
View source
%% title: Strain that builds nothing
%% caption: Muscle grows back stronger after strain. Administrative load produces only exhaustion.
flowchart TD
classDef actor stroke-width:1.6px;
classDef system stroke-width:1.2px;
classDef gate stroke-width:1.6px;
classDef binding stroke-width:3px,font-weight:bold;
classDef status stroke-dasharray:4 3;
classDef burden stroke-width:2px;
classDef repair stroke-width:2.4px,font-weight:bold;
classDef failure stroke-width:2.2px,stroke-dasharray:6 3;
subgraph Biological["Biological Antifragility (Taleb)"]
direction TB
B1["Physical stressor / micro-tear"]:::system --> B2["Metabolic recovery"]:::repair
B2 ==> B3(["Hypertrophy / adaptation"]):::binding
end
subgraph Administrative["Administrative Friction (UX / Bureaucracy)"]
direction TB
A1["Context fragmentation / interruptions"]:::burden --> A2["Executive function depletion"]:::burden
A2 ==> A3(["Entropy / cognitive insolvency"]):::failure
end
Biological ~~~ Administrative
Personal systems lose to institutional ones
James Clear (Atomic Habits) and Charles Duhigg hold that you do not rise to the level of your goals; you fall to the level of your systems. Optimization, on their account, comes from personal habit stacking. That’s true for the individual, but false for the operator of a hostile system. You cannot “habit stack” your way out of a system built to interrupt you.
Where an algorithm interrupts every 11 minutes — the rate one observational study of 13 nurses found — no amount of personal discipline can reliably maintain a flow state, and the Institutional System (the alerts) tends to overwhelm the Personal System (the habits). That is a claim about overload thresholds and the attention-recovery evidence, not a law of thermodynamics. Telling the user to optimize their way through toxic infrastructure obscures the deficit that needs fixing.
Carol Dweck’s Mindset holds that abilities can be developed and failure is a learning opportunity. The “Growth Mindset” presumes a rational environment where inputs yield outputs. But modern bureaucracy functions as “Sludge” (Cass Sunstein)—friction designed to be irrational and opaque.
Getting through a broken system is a Regressive Tax. It requires surplus resources (time, literacy, emotional reserve) that vulnerable users do not have. To tell a user who has hit a dead-end in a benefits portal to “adopt a growth mindset” is to ignore the material reality of the barrier. The barrier isn’t a learning opportunity; it’s a locked door.
The vendor’s savings are the user’s burnout
Eric Ries’s The Lean Startup and Agile orthodoxy say to move fast, ship early, and iterate based on user feedback. In safety-critical environments, the MVP often functions as a Maximum Liability Product.
“Shipping to learn” creates a moral hazard where the cost of Quality Assurance (QA) is externalized onto the user. It is a direct subsidy: the vendor saves money on testing, and the user pays for it in burnout.
If a bridge requires a driver to be a stuntman to cross it safely, we do not start a training program for “Resilient Driving.” We fix the bridge.
Yet in the digital world, we have accepted the stuntman standard. We have accepted that our tools will be hostile, extracting, and broken, and that it is our job to be tough enough to survive them.
Stop paying this tax.
The goal of design is not to build a user who can endure the friction.
The goal is to build a system that does not require endurance to use.1
“Optimizing the user” makes a system look efficient because the costs in time and health it pushes onto users never show up in its numbers. Breaking this loop means counting the user’s metabolic debt, the unrecorded wear and repair the system’s mistakes impose on them, as a primary system cost.
Resilience stories are the subsidy’s PR
The same cost-shifting has a narrative version, the resilience inversion, and it teaches the lesson. Every story about the worker who made it work, the nurse who held the ward together, and the family who managed despite the process is a story about whose adaptability was being spent—told as if the adaptability were the point. The resilience story is the subsidy’s public relations: it converts the evidence of a design failure into the celebration of a person, so the same side keeps being asked to be more resilient. When a resilience story is told, ask which design failure the person was absorbing.
Notes
The subsidy has an accounting. The Rule Works. She Doesn’t Fit. names the residue every rule produces and asks who is assigned to carry it; Rank Means Never Having to Adapt names the position that lets one side stay simple because the other must flex; and A Great Metric Can Mean Someone Is Quietly Fixing It shows what the subsidy conceals from the institution that lives on it.