Ethical Design & Avoiding Dark Patterns

Ethical Design & Avoiding Dark Patterns

A "dark pattern" (Harry Brignull's 2010 coinage; the field now prefers deceptive pattern, and Brignull's reference library lives at deceptive.design) is an interface deliberately crafted to trick users into doing things they would not have chosen freely — spending more, sharing more, staying subscribed. They are not bad UX by accident. They are good UX turned against the user: the same craft that makes a flow feel effortless is pointed at extraction instead of service. Use this skill to recognize all of them, to refuse to build them, and to ship the honest alternative without losing the business goal.

How to use: when designing a flow, run each consequential moment (defaults, declines, costs, exits, consent, permissions) against §6's asymmetry rule. When auditing, name the pattern with its canonical term from §2, rate severity (§7), and cite the legal exposure (§8) — that converts "this feels manipulative" into a prioritized, defensible finding a PM and a lawyer both act on.

1. Why ethics is a design-system concern

Ethics lands in design systems because systems codify defaults, and defaults shape behavior at scale. A design system is the set of pre-made decisions a thousand screens inherit. Decide once that the "subscribe to marketing" checkbox component ships pre-checked, or that the destructive-confirm dialog styles "Cancel" as the loud primary button, and you have manufactured a dark pattern in every product that consumes the library — automatically, invisibly, forever.

• Defaults are decisions made for the user. ~95% of users never change a default (the "default effect" / status-quo bias). A pre-ticked box is a choice you made and attributed to them.
• Components encode ethics. Button hierarchy, toggle default states, banner layouts, and copy templates are where deception lives or dies. Govern them at the component level, not per-screen, or every team re-litigates it.
• It is cheaper upstream. One ethical <ConsentBanner> with symmetric Accept/Reject is cheaper than 200 teams each shipping a "Reject all" buried two clicks deep — and than the regulator who finds it.
• Trust compounds; so does its loss. A single discovered dark pattern ("I got auto-charged," "I can't cancel") is a churn-and-review-bomb event. The design system is the cheapest place to make the honest path the default path.
• The designer is on the hook too. "The PM asked for it" is not a defense the FTC, the public, or your own conscience accepts. Brignull built deceptive.design partly as a hall of shame so the people who ship these are named. As the person who controls the component defaults, you are the last line — log the objection, propose the honest variant, and escalate rather than ship silently.

The test that drives this whole skill: would I be comfortable explaining this design, out loud, to the user it affects? If the honest explanation embarrasses you, it is a dark pattern.

The cognitive levers dark patterns pull

Every deceptive pattern exploits a known, hard-wired bias. Naming the lever tells you both why it works and why it's unfair — it bypasses deliberate reasoning rather than informing it.

The same biases power ethical persuasion too — anchoring on a genuinely good deal, real social proof. The lever isn't the problem; using it on a false premise, or to override the user's actual interest, is.

Encode the ethics into the system, not the screen

Because the design system is the leverage point, the controls below belong in the library and its governance — not in a per-team checklist nobody reads:

• Ship honest component defaults. Toggles and consent checkboxes default off. Confirm dialogs default focus to the safe action and never style the destructive/business-favorable option as the primary CTA. Banners ship with symmetric Accept/Reject.
• Provide the ethical primitive so the dark one is the harder path. A vetted <ConsentBanner>, <CancelFlow>, and <PriceSummary> mean the easy, paved road is also the honest one. Don't ship a component whose default configuration is a dark pattern.
• Add a deception gate to design review. Before a flow ships, run §7's checklist; a finding blocks the same way a contrast failure does. Keep an ETHICS.md log of patterns the team has rejected and why, so they aren't re-litigated.