design ethics
Forced action
What is the forced action dark pattern?
Forced action is a deceptive pattern that makes you do something unrelated before you can do the thing you actually came for. Forcing account creation to read an article, demanding data or permissions you don't need, or making you watch an ad or complete a survey to continue - the wanted task is held hostage to an unwanted one.
Also known as: forced action, forced enrolment, forced registration
Prefer to watch?
Watch the recap 1:02
The demo
You came for one thing: the free guide. Try to get it. First through the wall most sites throw up - then through a version that just gives you what you asked for. Notice the unrelated toll.
What this demo shows (text version)
You want a free guide. In the forced flow, before you can download it you're made to create an account, accept marketing emails and answer a survey - none of which the download actually requires. In the honest flow the guide downloads immediately, and only afterwards are you offered an optional "want to save your progress? create an account" that you can freely skip.
That's forced action: holding the task you came for hostage to unrelated steps the company wants. It's coercive because there's no real choice, and mandatory sign-up walls are a known conversion killer too. The honest standard is to require only what the task needs, make the rest optional and skippable, and let people get what they came for first.
Forced action bundles something the company wants with something the user wants, and won't release the second without the first. Create an account to see a price, hand over your contacts to use a feature, accept tracking to read the page - none of it necessary to the task, all of it mandatory. It's coercive because there's no real choice: comply or go without. The honest standard is to ask only for what the task genuinely requires, make everything else optional and clearly skippable, and let people use the core thing first and decide about the extras later (a guest checkout, a "maybe later", a skip link). If a requirement doesn't serve the user's goal, it shouldn't block it.
You just wanted the download, but first you had to make an account you didn't want - the real task held hostage to the company's. That's forced action, and the tell is that the demanded step has nothing to do with what you came for. The honest version asks only what the task needs and lets the rest be optional, so you get what you came for without paying an unrelated toll.
Forced action covers forced registration (must create an account to proceed), forced enrolment (auto-signing you up for something extra), gated content (hand over data or watch an ad to continue), and permission demands beyond what the feature needs. The pattern is coercive bundling: the thing you want is available only if you also do the thing the company wants, which often isn't required at all.
It exploits the fact that you're already committed to a goal - you came to read, buy, or download - so a barrier thrown up at that moment extracts compliance you'd never have offered cold. Mandatory account creation before checkout is the classic example, and a well-known conversion killer as well as an ethical problem: many people simply leave, and those who stay give up data under duress.
The fix is to require only what the task genuinely needs and make the rest optional and skippable: offer guest checkout, let people use core features before signing up, request permissions in context and only when needed (and degrade gracefully if refused), and provide clear "skip" or "maybe later" paths. Consent obtained by blocking the user's goal isn't freely given - and it usually costs you the conversion anyway.