In the current discourse of work and technology, “resilience” is the ultimate virtue. We celebrate thedoctor who powers through a clunky EHR, the pilot who manages a chaotic dashboard, and the citizen who navigates a labyrinthinebenefits portal.
We have built an entire industry of thought leadership—spanning management theory, psychology,and tech design—dedicated to making the human operator tougher, faster, and more adaptable.
But viewed through the lens of Industrial Hygiene, this obsession withresilience is not a solution; it is a symptom of structural failure.
Resilience is a subsidy. It is atax the user pays to cover the cost of lazy engineering.
When a system fails to resolve ambiguity, manage memory, orhandle errors, it doesn’t just stop working. It borrows stability from the user. The user supplies the memory, the patience,
and the metabolic energy to bridge the gap. This is not a character trait; it is a resource transfer. Institutions are balancingtheir books by burning your nervous system.
To build truly safe systems, we must dismantle the five dominant myths thatallow institutions to offload their maintenance costs onto us.
Myth 1: The Myth of “Grit”
- The Intellectual Source: Angela Duckworth (Grit).
- **The Thesis:**Perseverance and passion for long-term goals are the primary predictors of success.
My Critique:
Grit is a valid virtue for intrinsic pursuits (learning the violin, training for a marathon). It is a toxic metric forextrinsic friction (navigating a billing code).
When we demand “grit” from a nurse struggling with amedication dispenser, we are committing a category error. We are treating a Logistical Bottleneck as aCharacter Test. The “grit” required to endure bad software is not a sign of high character; it is a signof high Failure Demand. Every ounce of grit spent fighting the interface is a tax paid on behalf of a vendor whodidn’t finish the design.
Myth 2: The Myth of “Antifragility”
- The Intellectual Source: Nassim Taleb (Antifragile).
- The Thesis: Systems (and organisms) benefit fromshocks and disorder; they should get stronger under stress.
My Critique:
Taleb’s physicsapply to evolutionary systems, not administrative ones. A muscle grows when torn; a distinct cognitive processdegrades when fragmented.
Administrative burden follows the laws of thermodynamics, not biology. It createsEntropy (waste heat), not Hypertrophy (growth). When a user faces high-frequency interruptions, they do not become“antifragile”; they become cognitively insolvent. Applying this logic to UX justifies negligence by framing burnout as afailure to adapt to chaos.
Myth 3: The Myth of “Atomic Habits”
- The Intellectual Source: James Clear (Atomic Habits), Charles Duhigg.
- The Thesis: You do not rise to thelevel of your goals; you fall to the level of your systems. Optimization comes from personal habit stacking.
My Critique:
This is true for the individual, but false for the operator of a hostile system. You cannot“habit stack” your way out of a Coercive Architecture.
If an algorithm is designed to interruptyou every 11 minutes (the average for hospital staff), no amount of personal discipline can maintain a flow state. TheInstitutional System (the alerts) always overwhelms the Personal System (the habits). Suggestingthat a user can “optimize” their way through toxic infrastructure is a form of gaslighting that obscures the structuraldeficit.
Myth 4: The Myth of the “Growth Mindset”
- The Intellectual Source: Carol Dweck (Mindset).
- The Thesis: Abilities can be developed. Failure is just alearning opportunity.
My Critique:
The “Growth Mindset” presumes a rationalenvironment where inputs yield outputs. But modern bureaucracy functions as “Sludge” (CassSunstein)—friction designed to be irrational and opaque.
Navigating a broken system acts as a RegressiveTax. It requires surplus resources (time, literacy, emotional reserve) that vulnerable users do not have. To tell a user whohas hit a dead-end in a benefits portal to “adopt a growth mindset” is to ignore the material reality of the barrier. Thebarrier isn’t a learning opportunity; it’s a locked door.
Myth 5: The Myth of the “MVP” (Minimum Viable Product)
- TheIntellectual Source: Eric Ries (The Lean Startup), Agile Orthodoxy.
- **The Thesis:**Move fast, ship early, and iterate based on user feedback.
My Critique:
In safety-criticalenvironments, the MVP often functions as a Maximum Liability Product.
“Shipping to learn” createsa moral hazard where the cost of Quality Assurance (QA) is externalized onto the user. If the interface is confusing or the workflowis buggy, the user pays for the company’s “learning” with their own time, errors, and stress. It is a directsubsidy: the vendor saves money on testing, and the user pays for it in burnout.
Rejecting the Tax
If a bridge requires a driver to be a stuntman to cross it safely, we do not start a training program for “ResilientDriving.” We fix the bridge.
Yet in the digital world, we have accepted the stuntman standard. We have acceptedthat our tools will be hostile, extracting, and broken, and that it is our job to be tough enough to survive them.
Wemust stop paying this tax.
The goal of design is not to build a user who can endure the friction.
The goal is to build asystem that does not require endurance to use.