The car’s crumple zone was an ethical invention. Engineers designed steel to fail on purpose — to absorb thecrash instead of the driver’s body.
The choice was clear: human life mattered more than keeping the car intact. Designisn’t neutral. Every structure prioritizes something.
In the crumple zone, that priority was explicit: the machine breaksso the person survives.(note 1)
The carmaker didn’t install it outof compassion; product liability law made human life too expensive to ignore. The crumple zone emerged when math finally favoredsafety.
How the Hierarchy Reversed
Digital systems inherited the same calculus but reversed the answer. Today’splatforms face the same question — where should damage land? — but optimize differently.
Wasting a million hours ofuser time costs less than slowing a machine for one second. The reversal isn’t moral decay; it’s efficiency pursuing adifferent target.
- An algorithm denies your claim.
- A chatbot loops your appeal.
- Amoderation model deletes your work with no explanation.
In each case, the software stays smooth while you scramble.
Your patience, your time, your emotional labor absorb the system’s failures.
We call this good design, the kindthat hides its effort until something goes wrong. But frictionless often means voiceless. Smoothness hides seams, and seams are wherecorrection happens.(note 2)
Friction isn’t about virtue; it’s how systems notice their mistakes. Remove it, and errorshave nowhere to register.
When a design never bends, something else has to break.
Who Carries theForce
Institutions stay intact by pushing consequences outward. When systems fail, the burden lands on whoever has the leastprotection: the gig worker, the moderator, the user.
This isn’t moral failure, it’s good old structural logic
— you preserve your architecture by making someone else absorb the damage.
- Uber drivers navigate impossiblearbitration clauses while the platform stays legally untouchable.
- Content moderators process trauma soFacebook’s algorithms can claim neutrality.
- Insurance claimants spend months in appeal loops while the systemmarks them “resolved.”
The design works because regulation hasn’t caught up; platforms sellautomation as inevitability and regulators let them. Resilience through outsourcing.(note 3)
Designing for Failure
Good design doesn’t promise perfection. It assumes failure and builds space to handle it.
That means visiblemechanisms: appeal routes, logs, human review paths.
It means acknowledging that harm will happen and creating ways to catchit early.(note 4)
Ethics isn’t supposed to be there for decoration; it ought to be a structure that absorbs shock.
When a system can’tadmit error, it exports the problem. When friction has nowhere to go, it finds a person—the human crumple zone.
Not everybend redistributes force cleanly; sometimes friction just means delay. But in systems meant to serve people, delay can be the cost ofgetting it right.
Putting the Break Where It Belongs
Mid-century engineers accepted the tradeoff. Steel would crumpleso people could walk away.
Software needs the same calculation.
Maintenance usually means preventing failure, but inoverstressed systems, it also means absorbing damage without collapse — handling failure well enough that repair stayspossible.
The goal shouldn’t be to last forever; it should be to survive the next impact.
Safety means knowingwhere to put the breaking point. You can see a system’s priorities in what it protects and what it lets take the hit.
With every crash comes a choice about who is built to break.
When the next impact comes,the machine should yield first.
And the human should stay standing.
Further Reading
Note 1.
For more on how physical design encodes morallogic, see Critical Bioengineering.
Note 2.
See Consensus Without Conflict Is a Lie for how“seamlessness” replaces accountability with control.
Note 3.
You can see this dynamic traced in Sanctiphagy, where endurance itself becomes fuel for broken systems.
Note 4.
See The Right to Fuck Up on failure as a civic right and the backbone of moral infrastructure.