Questions this pattern makes askable
- What hidden labor, risk, or emotional regulation is making this arrangement look smooth?
- Who became the crumple zone or maintenance layer for everyone else?
- What would fail visibly if the people carrying the burden stopped compensating?
- Who has decision authority, and who is still blamed when the system fails?
Read in this order
Burden
For when the system looks efficient only because somebody else is carrying the cleanup, translation, or emotional load.
For readers who can already name hidden strain but want a tighter sequence for where upkeep, fallout, and accountability get pushed downstream.
- Why Systems Lean on Our Backs: The Politics of Load Bearing The political question isn’t if shocks arrive, but where the load lands. This essay reframes “policy” as applied physics—and legitimacy as a system’s load-bearing capacity.
- Everyone is a Crumple Zone Now Machines once bent to save people. Now people bend to save machines.
- Optimizing the User Resilience is a subsidy we pay to cover the cost of structural failure
- Pretending Is Half the Job Why smoothing danger becomes your unpaid assignment
- This Did Not Have to Cost You This Much How systems survive by making suffering feel necessary.
- The Capture of “Maintenance” Reclaiming the maintenance that keeps people alive rather than the one that keeps systems standing.
- To Be is To Be Maintained Power as the Allocation of Persistence
After the path, widen into the coercion synthesis if you want to compare burden transfer with defaults, dependence, and hidden force across domains.
Another route
Response
For when you can name the delay, burden, or proof problem and need to ask what kind of response is actually possible.
For readers who have finished naming a pressure and want the next question: what to do about it.
- You Can Design Harm Out How to design systems that protect human limits and reject harm as the path of least resistance
- How to Design for Cognitive Scarcity Stop designing for the idealized “Hero User.” Build resilient interfaces that work when your user is stressed, tired, and operating on 15% battery.
- Engineering Mutuality Why freedom will depend on what we build together next.
- Stop Preaching. Start Engineering. Goodness isn’t a moral trait; it’s a design property. When systems reward correction instead of denial, virtue becomes infrastructure.
After the path, return to the pressure paths (Burden, Survivability, Delay) when you need a tighter diagnosis before deciding where leverage lives.
Mechanisms
How this pattern runs
Named mechanisms in this pattern. Each one has a checklist for telling whether you are inside it.
Load-Bearing Design
Narrates itself as trade-off, optimization, the design couldn't avoid it.
Was someone expected to absorb a cost that the system could have absorbed?
The Capture of Maintenance
Narrates itself as innovation, improvement, upgrade, efficiency.
Does the work that keeps things running get less recognition than the work that launches new things?
Hyperreal Labor
Narrates itself as metrics, KPIs, performance, optimization.
Do you produce metrics or outcomes?
Vocabulary
- Burden transfer
- Crumple zone after Madeleine Clare Elish (2019)
- No unprofitable people
- Human as crumple zone after Madeleine Clare Elish (2019)
More in this pattern
Other essays that name it
-
Once you label entire groups “too expensive,” friction-based eugenics is always just one step away
