/ Library/ Need to Act Fast/ Delmore Effect
Decide Bias № 041 · Last updated 6 June 2026

Delmore Effect.

"We dodge the hard decision by optimising an easier one nearby — and call it progress."

01Overview

The Delmore effect describes preferring to make comparisons on simpler or less important dimensions instead of tackling harder, more consequential ones. Faced with a difficult career choice, someone might obsess over office chair colour. In product flows, users optimise trivial preferences while leaving high-stakes defaults untouched.

Designers often misread this as engagement. Users spend minutes customising themes while keeping privacy defaults they never opened. They compare shipping speeds but not return policies. The UI invited comparison where comparison was easy — not where it was important.

02Detailed explanation

Delmore behaviour appears when interfaces expose many comparable low-stakes controls alongside hidden or complex high-stakes ones:

  • Signup flows with rich avatar customisation and collapsed data-sharing settings.
  • Configurators that highlight colour trims while bundling finance terms in PDF links.
  • Settings screens with dozens of notification toggles and one opaque "personalisation" master switch.
  • A/B tests that optimise button copy while checkout legal consent remains untested.

Easy comparisons feel like control. Hard comparisons feel like work. Users satisfice on what the UI makes satisfice-able.

03Why it exists

Cognitive effort is budgeted. When a flow surfaces trivial pairwise choices, the brain spends its budget there and preserves energy on consequential defaults.

Designers enjoy building delightful micro-preferences — they ship comparability. Legal, financial, and privacy choices stay dense because they are hard to design, not because users do not care.

The short version

If users customise everything except the thing that affects them most, your comparability map may be inverted.

04Effects on users

Users leave harmful defaults in place while personalising superficial layers — then feel ownership over the product they never fully configured.

They report satisfaction with "choice" while misunderstanding the terms they did not compare — Delmore plus omission bias.

05Effects on designers & teams

Teams accidentally cultivate Delmore:

  • Preference theatre in onboarding. Delightful customisation screens before consent and permissions.
  • Flattening important choices into advanced settings. Hard decisions buried; trivial ones on the home tab.
  • Metrics that track engagement with easy toggles. "Users love personalisation" — they love the easy part.
  • Decision fatigue misdiagnosed. Users aren't tired of choosing; they're tired of choosing the wrong things.

6Introspective view

Look inward. Teams set more articulate goals for trivial areas than for the important-but-hard ones.

From an introspective perspective, ask how Delmore Effect may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

Prioritisation

What the roadmap protects

Roadmap conversations about Delmore Effect often overweight what is already shipping and underweight what is merely possible. Teams set more articulate goals for trivial areas than for the important-but-hard ones.

Planning

The first estimate in the room

Sprint planning around Delmore Effect is vulnerable to whichever number is spoken first — story points, dates, or effort — because later estimates adjust from that anchor rather than from zero. Teams set more articulate goals for trivial areas than for the important-but-hard ones.

Strategy

The brief you inherited

Strategy work on Delmore Effect often starts from a problem statement someone else wrote — and that opening frame limits which solutions feel in scope. Teams set more articulate goals for trivial areas than for the important-but-hard ones.

User Interviews

What you hear first sticks

In early interviews about Delmore Effect, the opening participant can set the frame for everyone after — which pains feel central, which workflows seem broken, which quotes get repeated in synthesis. Teams set more articulate goals for trivial areas than for the important-but-hard ones.

7Extrospective view

Look outward. Users compare easy-to-judge attributes over harder, more important ones, shaping how options are framed.

From an extrospective perspective, Delmore Effect is a property of the product experience itself — visible in pricing, copy, defaults, layout, and the moments where users decide whether to continue, convert, or leave.

Comparison

Side-by-side framing

Feature tables are built for Delmore Effect: whichever column you highlight, sort, or place centre becomes the mental baseline for judging the rest. Users compare easy-to-judge attributes over harder, more important ones, shaping how options are framed.

Forms

Placeholders and suggested values

Form fields are quiet anchors for Delmore Effect — pre-filled amounts, placeholder text, and chip suggestions pull answers toward what the interface shows first. Users compare easy-to-judge attributes over harder, more important ones, shaping how options are framed.

Decisions

Choice architecture

When users must choose under uncertainty, Delmore Effect shows up in how options are ordered, labelled, and defaulted — the interface is never neutral. Users compare easy-to-judge attributes over harder, more important ones, shaping how options are framed.

Consideration

Comparing options

During consideration, Delmore Effect steers how alternatives are weighed — feature matrices, reviews, and "most popular" badges all tilt the comparison. Users compare easy-to-judge attributes over harder, more important ones, shaping how options are framed.

08Practical takeaways

  • Map stakes vs comparability. Audit where you make comparison easy — align with what matters most.
  • Elevate consequential choices. Plain language, progressive disclosure for complexity — not burial.
  • Reduce trivial choice where it distracts. Sensible defaults for theme beat twelve colour pickers before consent.
  • Measure comprehension, not clicks. Customisation rate is not informed consent rate.
  • User test high-stakes understanding. Ask what users think they agreed to — not only whether they finished onboarding.
  • Design guided comparison for hard domains. Insurance, privacy, and pricing need structured compare tools, not PDFs.

09Design examples

Onboarding

Avatar before analytics

Users spend four minutes choosing profile themes. Analytics opt-in defaults to on; 2% open the panel. Delmore engagement masks consent failure.

E-commerce

Trim packages

Buyers compare three delivery windows in detail. Extended warranty terms sit in collapsed legal text. Claims data shows warranty misunderstanding, not delivery dissatisfaction.

Settings

Notification maze

Users fine-tune 22 notification types. "Partner data sharing" lives under Advanced once. Support tickets show users shocked by sharing they never compared.

Enterprise

SSO after sidebar colour

Admin setup wizard highlights UI white-labelling. SSO security config is step nine, optional. Breaches trace to defaults admins never reached.

10Ethical risks

Surfacing easy choices to distract from hard ones is a dark pattern cousin — users perform autonomy while losing it on defaults.

Vulnerable users with less time compare what is visible; harm hides in what required expertise to evaluate.

Self-test: Where does your product invite comparison that does not matter — while the consequential choice stays hard to find?

10Suggested reading