A7.13.4Convention-breaking cost-benefitdesign

Deliberately breaking a common convention needs a matching payoff, or the net loss exceeds the differentiation gain

Aliases: switching cost · differentiation cost · breaking convention

What it is

When a team wants to break a common convention users have carried over from other products in favor of its own distinct interaction, that decision needs a clear, measurable payoff — differentiated positioning, an efficiency gain, brand recognition — large enough to offset the relearning cost imposed on users. Breaking a convention purely for the sake of being different produces an adaptation cost that outweighs the differentiation gain — a net loss.

Why it happens

The cost of breaking a convention isn't a one-time charge — every new user who arrives with the old model has to pay it again, so the total cost is the learning-curve cost multiplied by the ongoing stream of new users, which grows linearly or even cumulatively as the product's user base grows. The differentiation payoff, by contrast, usually plays out at the level of marketing or brand perception — a comparatively fixed or diminishing one-time gain that rarely scales up in proportion to user volume. Breaking the convention is only a net win when the differentiation's perceptible value (efficiency gains, higher task completion, the stickiness a distinctive experience creates) is large enough to outweigh the ongoing learning cost. In most cases, teams overestimate the differentiation payoff and underestimate how the cost keeps accumulating as the user base scales.

Where it stops holding

  • This rule presumes a common convention actually exists to be broken — in a brand-new category, there's no prior user model to fight, so the design choice in question isn't "breaking a convention" at all; it's innovation with no baseline cost to offset.
  • The payoff isn't necessarily visible in the short term: some convention-breaking designs really do raise adaptation cost early on, while the brand recognition or efficiency advantage they build only shows up over a longer horizon. Evaluating with short-term metrics alone invites a wrong call.

Applying it

  • Before deciding to break a common convention, quantify both sides: the expected number of affected users multiplied by their average learning cost (estimable from the convention's own transfer strength — breaking a platform-level convention costs far more than breaking your own brand-level one), weighed against the differentiation's specific, measurable payoff, rather than waving it off with something like "more distinctive."
  • How to check: ship the convention-breaking design to a small gated rollout and compare first-completion time and support/help-seeking volume on the key task between old and new versions. If the adaptation cost hasn't dropped to an acceptable level within the expected window, roll back rather than keep waiting for the payoff to materialize.

Related

  • Same group: A7.13.1 Users transfer platform-level and brand-level conventions with different strength · A7.13.2 The first tool of a kind a user learns carries the greatest weight in later transfer · A7.13.3 Users apply the model of one interaction style to a product in a different modality · A7.13.5 Similar appearance paired with different behavior produces the strongest negative transfer
  • Nearby: A7.01 A mental model is a user's internal explanation of how a system works
  • Search terms: convention breaking · switching cost · differentiation · interface consistency

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/A7.13.4