What you'll understand by the end of this lesson
- Why defaults shape decisions far more than people realise
- The difference between a nudge and a restriction
- How CRO teams use defaults to increase revenue without forcing a choice
- Where helpful defaults end and dark patterns begin
The principle in plain English
A nudge is a small design choice that makes one option easier, more visible, or more obvious than others — without removing the alternative.
The nudge doesn't force anything. It just makes one path the path of least resistance. And because most people follow the path of least resistance, that one design decision ends up shaping the majority of outcomes.
The concept comes from behavioural economists Richard Thaler and Cass Sunstein, who argued that "choice architecture" — the way options are presented — has enormous influence over what people choose. The default isn't neutral. It's a choice. And whoever sets the default holds a lot of power over what happens next.
A simple example
A new employee joins a company. The pension plan has two options:
- Option A: Opt in to employer contributions (employee must tick a box to join).
- Option B: Opt out of employer contributions (employee is enrolled automatically; they must tick a box to leave).
Studies consistently show that Option B leads to dramatically higher enrolment rates — not because employees value it more, but because it's the default. Doing nothing means staying enrolled. And most people do nothing.
The nudge didn't change the options. It changed the default — and changed the outcome.
How nudges appear in CRO
Pre-selected options
You've seen this on every pricing page: the annual billing toggle is already switched on when the page loads. Monthly is available — you can switch to it — but annual is the default.
The user can override it with one click. But the majority don't. They accept the default, pay annually, and improve the company's cash flow and churn rate in one move.
This is a nudge. It steers without forcing. The user always had a choice — they just weren't given a neutral starting point.
The "recommended" label
On a three-tier pricing table, one plan has a badge: "Most popular" or "Recommended for most teams."
Nothing is locked. All three plans are fully available. But the label nudges attention and social proof toward one option simultaneously. The recommended plan converts disproportionately — not because it's necessarily the best choice for every buyer, but because it's been positioned as the safe, obvious choice.
Pre-applied discount codes
A checkout flow where a discount code has already been applied — "Your 10% welcome discount has been added" — removes the friction of searching for a code and creates a small reciprocity moment. The user didn't ask; the site just helped. That nudge changes the emotional register of the checkout.
Suggested quantities or upgrades
A subscription box that defaults to "Deliver every 2 weeks" rather than "Deliver once." A hosting provider that defaults to a 12-month term. A software tool that defaults to the team plan rather than the individual plan.
Each one can be changed. Most users don't change them.
Before testing a new CTA or copy variation, check your defaults. What plan does the page load on? What billing period is pre-selected? What quantity, tier, or option is the starting point? Defaults often have a larger effect on conversion than any headline or button colour change.
The ethical line
Nudges exist on a spectrum. At one end: genuinely helpful defaults that match what most users would choose anyway if they thought it through. At the other end: dark patterns — defaults designed to extract money from inattentive users.
The difference comes down to intent and transparency.
Helpful nudge: Annual billing is pre-selected because it saves the user 20% and you genuinely believe it's the better deal for most customers. The price difference is clearly shown. Switching to monthly is a single click.
Dark pattern: A free trial pre-selects a paid add-on with a small monthly fee, displayed in a font that matches the background colour. The add-on can be removed, but the opt-out is buried in a sub-menu three clicks deep.
Both are "technically" a choice. Only one respects the user.
Regulators in the UK, EU, and US are increasingly treating dark patterns — including deceptive defaults — as consumer protection violations. A nudge that misleads users or hides costs is not just ethically wrong; it's a growing legal risk. Before shipping any pre-selected option, ask yourself: "If this was explained clearly to the user, would they feel helped or tricked?"
The CRO audit
Look at every form, checkout, and pricing page and ask:
1. What are the defaults on this page?
List every pre-selected option, pre-filled value, or pre-toggled switch. For each one, ask: is this default in the user's interest, the company's interest, or both?
2. Does the default match what most users would want?
If the majority of users who complete this flow end up on the annual plan, and most of them are satisfied — the default is probably working as a nudge. If you're seeing high cancellation rates, chargebacks, or complaints about unexpected charges, a "default" may have become a dark pattern.
3. Is the override obvious?
A nudge is only ethical if the alternative is genuinely easy to choose. If switching from annual to monthly requires finding a tiny toggle hidden below the fold, that's not a nudge — that's friction used as a trap.
A SaaS pricing page loads with the annual billing toggle already switched on. Monthly billing is available one click away. The annual plan saves users 20%. Is this a nudge or a dark pattern?
You've seen how defaults steer calm, attentive users. But what about users who arrive stressed, distracted, or in a hurry? Most checkout flows are designed for a relaxed shopper who doesn't exist.