Designing for trust: the real cost of dark patterns
A dark pattern is an interface designed to get from the user what they wouldn’t have chosen knowingly: a pre-ticked box, a labyrinthine unsubscribe, artificial urgency. It works, in the short term. That’s why it’s a trap: the metric goes up, and trust goes down, without showing up on the same dashboard.
Why it’s tempting
A dark pattern is a local optimisation: it lifts the number you’re watching today, sign-up, opt-in, conversion. The cost is deferred and diffuse. Someone who felt tricked comes back less, recommends less, distrusts the next screen. That cost exists, but it isn’t in the next column, so we forget it.
Trust is a slow metric
Conversion is a fast metric; trust is a slow one. The job is not to sacrifice the second for the first. A good design constraint guides without deceiving, the way tying the number of campsites to the length of stay helps the user instead of trapping them. The line between guiding and manipulating is sharp: guiding serves the user’s decision, manipulating bypasses it.
The simple test
Before signing off on a screen, one question is enough: if the user clearly saw what I’m doing here, would they still agree? If the answer depends on them not noticing, it’s a dark pattern. Designing honestly leaves all the room for persuasion, with arguments rather than hidden friction.
In short
- A dark pattern is a local optimisation. It wins the metric of the day and loses trust.
- Trust is a slow metric. It doesn’t show on the conversion dashboard.
- Guiding isn’t manipulating. One serves the user’s decision, the other bypasses it.
- The test: transparency. If you’d have to hide it for it to work, it’s a dark pattern.