What are deceptive patterns?
Deceptive patterns are design choices that trick users into doing things they didn't mean to do, such as buying insurance they didn't want or signing up for a subscription they can't easily cancel.
For years, the industry called these "dark patterns," a term coined to describe interfaces crafted to benefit the business at the user's expense. The field has since moved to the clearer name "deceptive patterns," which describes exactly what they are: deception through design.
The key word is intent. A confusing checkout flow built by an inexperienced team is bad UX. A confusing checkout flow built on purpose, because confusion makes people spend more, is a deceptive pattern. The difference between a usability flaw and a deceptive pattern is whether the harm to the user is an accident or the goal.
-
keywords
- #DeceptivePatterns
- #DarkPatterns
- #Intent
Why they work
Deceptive patterns are effective because they run on the exact same psychology that good UX design uses. Defaults, visual hierarchy, loss aversion, social proof, friction: these are neutral tools. Every principle you learn to help users can be inverted to exploit them.
A well-placed primary button guides users toward the action they came for. The same button styling, applied to "Accept all cookies" while the decline option hides behind a grey text link, guides users toward the action the business wants. Defaults reduce effort when they match user intent, and quietly extract consent when they don't.
Users also skim. People read only a fraction of the text on a screen and rely on familiar patterns to move fast. Deceptive patterns weaponize that trust in convention: they place a checkbox where you expect an opt-out but make it an opt-in, knowing most people will never read the label.
-
keywords
- #Psychology
- #Defaults
- #LossAversion
Common types
You can't spot what you can't name. Here are the patterns you'll encounter most often, each with a concrete example.
Forced continuity
A free trial requires your credit card, then silently converts to a paid plan with no reminder, and cancelling takes a phone call during business hours. The signup took thirty seconds; the exit takes thirty minutes on hold. If cancelling a service is dramatically harder than starting it, that asymmetry is the design.
Sneaking
Items, fees, or add-ons appear in your basket without your explicit choice. A flight booking that quietly adds travel insurance, or a checkout where a "service fee" only appears on the final payment screen. The user discovers the true cost after they're emotionally committed to completing the purchase.
Confirmshaming
The decline option is worded to make you feel foolish or guilty: "No thanks, I hate saving money" or "No, I don't care about my family's security." It turns a neutral choice into a small public humiliation, hoping shame will do what the offer itself couldn't.
False urgency and scarcity
A countdown timer that resets when you refresh the page, or "Only 2 rooms left!" on a hotel that always has two rooms left. Real scarcity is useful information. Fabricated scarcity manufactures panic so users decide before they think.
Nagging
The app asks you to enable notifications, rate it, or upgrade, and asking once is fine. Nagging is when "Not now" means "ask again tomorrow, and the day after, forever." The design bets that exhaustion will eventually produce a yes that persuasion never earned.
Obstruction
Also called the roach motel: easy to get in, hard to get out. Deleting an account requires navigating five settings screens, typing a confirmation phrase, and sitting through a retention pitch, while creating that account took one tap with Google sign-in.
Interface interference
Visual tricks that manipulate the choice itself: pre-ticked boxes for marketing emails, a bright "Continue" button that accepts an upsell while the real "skip" is tiny grey text, or a close icon so small you tap the ad instead. The interface tells one story visually and another one legally.
-
keywords
- #ForcedContinuity
- #Sneaking
- #Confirmshaming
- #FalseUrgency
- #RoachMotel
Metrics vs. trust
Deceptive patterns trade long-term trust for short-term metrics, and the metrics always look great first.
This is what makes them tempting. A pre-ticked newsletter box lifts signups this quarter. A hidden cancellation flow flattens churn this month. Every dashboard says the design is working.
What the dashboard doesn't show is the user who felt cheated, disputed the charge, left a one-star review, and told friends to avoid the product. A conversion won through deception isn't a customer gained; it's a refund, a complaint, or a churned account on a delay. Trust compounds slowly and collapses instantly, and no A/B test measures resentment.
-
keywords
- #Metrics
- #Trust
- #Churn
The designer's responsibility
Sooner or later, someone will ask you to build one of these. It rarely arrives labeled as deception; it sounds like "let's reduce cancellation" or "make the decline option less prominent." Recognize the request and respond as a professional, not a lecturer.
Name the pattern. Saying "this is confirmshaming, a documented deceptive pattern" reframes the discussion from your opinion to an industry-recognized problem.
Argue with their metrics. Bring the costs the conversion number hides: refund rates, support tickets, app store ratings, and regulatory attention that deceptive practices increasingly attract.
Offer an honest alternative. If retention is the goal, propose a genuine win-back offer or a pause option instead of a hidden cancel button. Pushing back works best when you solve the business problem the deceptive pattern was supposed to solve.
-
keywords
- #Ethics
- #PushingBack
- #Alternatives
Audit your own product
Deceptive patterns don't only come from bad intentions. They accumulate through small "optimizations" that each seemed harmless. Audit your product regularly with a few honest tests:
The symmetry test. Is leaving as easy as joining? Compare the number of steps to subscribe with the number of steps to cancel.
The reading test. Would a user who reads every word make the same choice as a user who skims? If skimmers systematically end up opted in to things readers decline, your defaults are doing the deceiving.
The truth test. Is every urgency claim real? Check whether countdowns actually expire and stock counts reflect inventory.
The explanation test. Could you describe each flow to a user's face without being embarrassed? If a step only works because nobody notices it, it fails.
Takeaways
Deceptive patterns exploit the same psychology good UX uses, which is exactly why designers must know them by name.
Learn the catalogue: forced continuity, sneaking, confirmshaming, false urgency, nagging, obstruction, and interface interference. When asked to build one, name it, price its hidden costs, and offer an honest alternative. And audit your own product, because deception can creep in one small optimization at a time.
-
keywords
- #Audit
- #Honesty
- #UserTrust