Departing from convention requires a visible compensating gain
Aliases: convention tax · visible benefit · justified deviation
What it is
Every departure from platform convention is a tax: one more probe, one more wrong guess, one more “this app is not how this phone works.” The tax can be paid, but only with a visible gain tendered on the spot—the custom operation does something a system control cannot, and the user can feel that something at the moment the departure happens. A gain written into onboarding that will be skipped, or into an internal “it feels more like us,” does not settle the bill. If a custom switch and a system switch do the same job, there is no compensation, only tax.
This is when a departure is in surplus. Single-end learning bills, billing both platforms at once, and force accumulated elsewhere all describe where the tax comes from. This card asks only whether the compensation is present and whether the user can see it.
Why it happens
A departure interrupts a reflex. Once interrupted, attention asks why the extra step exists. If the answer is immediately true on the surface—direct manipulation on a canvas, gestural play on an instrument, two-finger rotate on a map—attention is paid in capability, and the tax is covered. If the answer waits on copy, or on a “it is actually more consistent” that will be felt three days later, attention records only friction. Visible means the gain and the departure co-occur in the same viewport in the same second, not that they coexist in the product narrative.
The compensation also has to be incremental for the task. Replacing a list with a horizontal cover wall, if the task is still “find yesterday’s item,” adds nothing and the tax has no counterparty. Replacing back with a bottom gesture bar that does no more than the edge-swipe collects a second tax on the same action. Departures that can actually settle tend to be operations the system never offered (a retouching brush, a musical performance, a 3D scene), not a reskin of an action the system already ships.
Where it stops holding
Assistive-tech users, people who just changed platforms, and one-time users are more sensitive to the tax; the same departure needs a larger visible gain to break even. Experts who spend eight hours a day on the canvas amortize the tax through practice; compensation can show up as throughput rather than first-glance delight. Confirmations required by law or safety look like departures but are a tax that cannot be bought off with “smoother.” An A/B test run only on retained users who already learned the product will measure the tax away—those users have paid tuition. First-task failures by new users have to be in the sample, or visibility of the gain cannot be measured.
Applying it
- For every departure, write one sentence: the increment the system convention cannot do, that the user can feel on this screen. If the sentence cannot be written, return to the convention.
- Put the compensation in the interface where the departure happens, not in launch onboarding, a help center, or a brand film.
- Do not rebuild switches, back, share, or payment as custom controls. Consider departure first on domain canvases that need direct manipulation.
- Verify with people new to the product. Stop at the departure, skip onboarding, and do not ask whether it “feels like the brand.” Ask what this step lets them do that the system control would not. No answer, or “it looks more distinctive,” means the tax was not paid. Then run the same task on a version that follows convention; if it is faster and less error-prone, the departure did not earn the increment.
Related
- Same group: R4.06.1 Breaking platform convention raises per-platform learning cost · R4.06.2 Cross-platform unification can violate both conventions at once · R4.06.3 Unify the conceptual model, not control appearance · R4.06.4 Convention draws its force from experience accumulated elsewhere · R4.06.5 Brand occupies the content layer; convention occupies the frame
- Adjacent: R1.07 Tension between design systems and brand expression · R4.14 The consistency cost of cross-platform frameworks
- Search terms:
compensating gain·convention tax·justified deviation·direct manipulation
Cards in the same group
- R4.06.1Breaking platform convention raises per-platform learning cost
- R4.06.2Cross-platform unification can violate both conventions at once
- R4.06.3Unify the conceptual model, not control appearance
- R4.06.4Convention draws its force from experience accumulated elsewhere
- R4.06.5Brand occupies the content layer; convention occupies the frame