The Scoreboard problem

Slot machines are one of the most carefully designed objects in the world. The button placement, the near-miss frequency, the sound design, the variable reward intervals: all of it is the product of decades of iterative research into human psychology. The people who build slot machines are not guessing. They are applying a precise understanding of how attention and reward interact to produce a specific behaviour: continued play.

Nobody calls slot machine designers evil. The design is legal. The intentions behind it are transparent, at least internally. And the industry that produces them is regulated, studied, and widely understood to be engineered for compulsion.

What is harder to explain is why that same logic, applied to a subscription cancellation flow or a cookie consent banner, gets discussed as if it were a craft problem rather than a choice.

Dark patterns have been in the design conversation for years. The term has been around since 2010. But something shifted in the past twelve months. The UX community stopped treating deceptive design as a fringe concern and started naming it as a mainstream practice. The State of UX this year did not dance around it. Teams are building friction into cancellation flows, obscuring pricing tiers, and using pre-checked consent boxes not because they misunderstood good design, but because those choices move conversion metrics.

That is the part of this conversation that most design discourse still avoids directly.

Dark patterns are not a design failure. They are a measurement success. They work exactly as intended, on the metrics the team was optimising for. But the metrics were wrong, and the team either didn't know or didn't say so.

That is the distinction most design discourse still avoids.

I was part of a product review early in my career where a conversion optimisation team presented results from a redesigned checkout flow. The numbers were strong. Completion rate was up. Drop-off at the final step was down. The room responded the way rooms respond to good numbers: with approval and a discussion of what to test next.

One designer on the team raised her hand and asked what had happened to refund requests.

Nobody in the room had that number.

It turned out refund requests had gone up sharply. Users were completing the purchase flow at a higher rate. But a significant portion of them felt they had been misled about what they were purchasing. They completed the transaction and then immediately tried to undo it. The conversion metric looked like a win. The refund rate told a different story.

The checkout flow had been optimised for the wrong event.

This is the scoreboard problem. Not that designers are malicious. But that they are designing toward the metrics they are given, and the metrics they are given are often proxies for value rather than value itself. Clicks are not engagement. Completion is not satisfaction. Conversion is not retention.

When the scoreboard only shows the first number, that is what the team optimises for. And when a dark pattern moves the first number, it looks like good design work inside an organisation that is not looking at the second number.

The design community's conversation about dark patterns tends to frame this as an ethics problem. Which it is. But framing it only as ethics puts the burden on individual designers to resist commercial pressure, which is both unfair and practically ineffective. Individual conscience is a poor substitute for a better scoreboard.

The designers I have watched push back successfully on deceptive UX patterns did not do it by invoking ethics. They did it by expanding the measurement frame. They brought the second number into the room. They did it by expanding the measurement frame. They brought the second number into the room. Refund rates. Churn at 30 days. Support ticket volume. App store reviews mentioning confusion or frustration.

When you put the second number next to the first one, the dark pattern stops looking like a win. It starts looking like a short-term conversion trade against long-term trust. And that is a business argument, not a values argument. Which means it can be heard by people who are not yet willing to be moved by the values argument.

This is not cynicism. But it is strategy. You use the language that opens the door.

The slot machine designers are not in the dark about what they are building. But they have a regulatory framework that sets limits on how far the compulsion can go. Product teams designing consumer software have no equivalent constraint, which puts the work of limit-setting inside the organisation itself.

That is a structural problem. But until it gets solved structurally, the most useful thing a designer can do is make the second number visible.

The scoreboard cannot be fixed from outside the room. But it can be changed by the people already in it.