Dark Patterns and the Trust Tax
Featuring Harry Brignull
Booking.com once showed fake scarcity counters, "Only 2 rooms left!", on listings where dozens of rooms sat available. It worked, until regulators started paying attention. Designer Harry Brignull coined "dark patterns" around 2010 for UX that tricks users into things they never meant to do: subscriptions that convert silently, confirmshaming buttons ("No thanks, I don't want to save money"), checkout flows that hide costs until the final step, and cancellation paths built like roach motels. Through the 2010s these were everywhere, and on the metrics, they worked.
For anyone building a product, this is a case about anything in your signup, billing, or cancellation flow that you would not want a journalist to see. It sharpens a concrete test: time how long it takes to cancel versus how long it took to sign up, and sit with the gap. What these tricks quietly cost you on the metrics you are not watching, and why the regulators are now closing in, is the part the app saves for you.
Frequently asked questions
What are dark patterns in UX design?
Dark patterns are interface choices that trick users into doing things they never meant to do, a term designer Harry Brignull coined around 2010. Examples include subscriptions that convert silently, confirmshaming buttons, fake scarcity counters, hidden costs at checkout, and cancellation flows built like roach motels.
Why do companies use dark patterns if they harm users?
On the short-term metrics, they work: Booking.com's fake "Only 2 rooms left!" counters boosted bookings even when dozens of rooms were available, and through the 2010s these tricks were everywhere because they moved the numbers. The catch is that they impose a hidden trust tax that does not show up on the metrics teams usually watch.
What is an example of a dark pattern and its outcome?
Booking.com showed fake scarcity counters on listings with plenty of availability, which worked until regulators started paying attention. Confirmshaming ("No thanks, I don't want to save money") and roach-motel cancellation flows are other common examples, and regulators such as the FTC are now closing in on them.
What can product and design teams learn from dark patterns?
Audit anything in your signup, billing, or cancellation flow that you would not want a journalist to see, and run a concrete test: time how long it takes to cancel versus how long it took to sign up, then sit with the gap. Short-term wins from manipulation come with a long-term cost in trust. CaseBook turns this into a move you apply to your own product, with an AI coach that reads your answer.