Good UX is not just about clarity.
It is about pressure.
Because a lot of interfaces are not neutral. They push. They rush. They corner. They bury the exit. They make one path feel obvious and the other one feel like a mistake.
If you want privacy-first, offline health tech to exist without surveillance funding it: sponsor the build → https://paintracker.ca/sponsor
That might look efficient on a dashboard.
It is not efficient in real life.
Especially not when the person using the system is tired, overwhelmed, grieving, under financial stress, dealing with pain, or trying to make a decision while their nervous system is already overloaded.
That is where coercion resistant UX matters.
Not as a soft preference.
As a standard.
The interface is part of the environment
When people talk about UX, they often act like it exists in a vacuum.
It does not.
An interface is part of the pressure around the user. It can reduce stress, or it can amplify it. It can make choice easier, or it can make compliance easier.
Those are not the same thing.
A coercive interface usually does a few familiar things:
It makes one path look obviously correct and the other one look risky or stupid.
It hides consequences behind soft language.
It uses timers, interruptions, and guilt to force a decision.
It makes the safe option feel like the wrong one.
It removes recovery after the user has already made a mistake.
That is not good design.
That is manipulation with rounded corners.
Stress changes how people decide
This is the part designers love to ignore.
Under stress, people do not process information the same way. Attention narrows. Memory gets worse. Reading gets shallower. People miss details. They click the first thing that seems available, especially when the interface is impatient.
So if your system assumes calm, focused, fully resourced users all the time, it is already failing the moment reality enters the room.
A trauma informed interface does not just look friendly.
It expects compromised cognition.
It assumes people may be tired, confused, dysregulated, distracted, or scared. That means the interface should slow down where it matters and stop demanding perfect conditions from imperfect humans.
Defaults are policy
Defaults are one of the most powerful coercion tools in product design.
People like to pretend defaults are just convenience. They are not. They are policy disguised as convenience.
A good default reduces load.
A bad default steers behavior.
That difference matters.
A real example is account setup screens that preselect marketing consent,
data sharing, or "personalized experience" options by default. The user
is tired, trying to get in, and the safest choice is not visually
privileged. The product is not helping the user decide. It is helping
itself collect permission.
A coercion resistant system should ask:
Who benefits from this default?
Can the user understand the consequence before accepting it?
Can they change it later without punishment?
Is the default reversible?
Is it serving the user's goal, or the system's agenda?
If the answer is unclear, the default is doing too much hidden work.
Nudging can become manipulation fast
Nudging sounds innocent until you inspect the machinery.
A nudge is only ethical when the user can see it, understand it, and move around it without penalty.
The second the nudge becomes opaque, hard to escape, or intentionally loaded, it stops being guidance and starts being coercion.
You see this everywhere.
A subscription flow where canceling takes ten more steps than buying.
A checkout where the "recommended" shipping option is preselected because it is better for the company, not the customer.
A banking app that places "defer payment" in bright color while the safer option is buried.
A consent dialog that makes refusal look like a mistake.
This is where good design becomes moral design.
Because an interface always reveals what it respects.
If it respects autonomy, it stays legible, reversible, and calm.
If it respects conversion above all else, it becomes loud, sticky, and suspiciously hard to leave.
Recovery is part of dignity
People make bad decisions.
They mis tap.
They rush.
They misunderstand the screen.
They panic.
They are human.
So a coercion resistant system does not just prevent mistakes. It assumes mistakes will happen and makes them survivable.
That means:
Undo should exist where possible.
Destructive actions should have clear recovery windows.
Dismissed states should not vanish forever without warning.
Deleted content should have a restoration path if the cost of loss is high.
Critical flows should let the user pause and return without punishment.
A good example is a message app that lets you undo send for a few seconds. That is not a gimmick. That is a recognition that human judgment is not always clean in the moment of action.
Recovery is not a bonus feature.
It is a respect feature.
If the interface only works when the user is calm and perfect, then it is not built for humans. It is built for idealized compliance.
Calm beats urgency
Urgency is one of the easiest ways to coerce someone.
Countdowns.
Flash warnings.
Deadline banners.
"One time only" language.
"Act now" pressure.
Visual noise that makes hesitation feel dangerous.
Sometimes urgency is real.
Most of the time it is manufactured.
The design question is simple: is the urgency there because reality requires it, or because the system wants the user to move without thinking?
A protective interface should never fake emergency energy to force behavior.
If something is truly time sensitive, say it plainly. Give the reason. Give the consequence. Give the next step. Then get out of the way.
No panic theater.
No fake red alarms.
No emotional blackmail disguised as product design.
Honest language matters
A lot of coercive UX is just dishonest language wearing a suit.
"Optimize your experience" often means "let us collect more data."
"Recommended for you" often means "profitable for us."
"Continue" often means "accept the thing we hid earlier."
"By using this feature, you agree" often means "we buried the terms in a wall of text and made the button larger than the exit."
If the language is vague, the system is usually trying to smuggle in consent.
That is exactly what protective UX should reject.
Say what the action does.
Say what gets stored.
Say what changes.
Say what can be undone.
Say what cannot.
People do not need more persuasion. They need less ambiguity.
Good friction is not bad UX
This is where a lot of teams get lazy.
They think all friction is bad.
No.
Some friction is protective.
Friction is good when it slows irreversible actions, creates room for reflection, or stops accidental harm.
Friction is bad when it blocks legitimate use, punishes tired users, or makes safe choices harder than unsafe ones.
The difference is intent.
A protective system inserts friction to preserve autonomy.
A coercive system removes friction from the action it wants and adds friction to the action it does not.
That is the pattern.
Once you see it, you see it everywhere.
Design for the worst day
Most interfaces are designed for the happy path.
That is why they fail when life gets ugly.
Real people use software while overloaded. Underfunded. Sleep deprived. Angry. Scared. Grieving. Sick. Distracted. Disoriented.
If your interface only works when someone is at full capacity, it is not robust. It is decorative.
A better standard is this:
Would this interface still feel fair if the user is exhausted?
Would it still feel legible if they are panicking?
Would it still feel humane if they are making the decision at 2 a.m. on a bad phone screen with a bad battery and a bad week behind them?
That is the test.
Not whether the design looks clean in a demo.
Not whether the funnel converts in the lab.
Whether it still protects the user when they are least able to protect themselves.
What coercion resistant UX looks like
It is not flashy.
It is not a conversion machine.
It is calm, clear, reversible, and honest.
It offers sensible defaults without hiding the cost.
It makes the safe path visible.
It lets the user back out without shame.
It avoids dark patterns, guilt cues, and fake urgency.
It preserves agency even when the user is under strain.
That is the protective computing version of UX.
Not just usable.
Not just polished.
Protective.
Because interfaces are not innocent.
They either make room for human dignity or they compress it for efficiency.
And once you understand that, the question changes.
Not how do we get users to comply faster.
Not how do we keep them from hesitating.
Not how do we make the preferred path feel inevitable.
The real question is this:
Does this interface stay respectful when the person using it is tired,
stressed, and easiest to pressure?
Support this work
- Sponsor the project (primary): https://paintracker.ca/sponsor
- Star the repo (secondary): https://github.com/CrisisCore-Systems/pain-tracker
- Read the full series from the start: (link)