Cognitive Load: Why Simplifying the Customer Journey Isn't About Fewer Clicks

Picture a customer three screens deep into a mortgage application, holding a passport number in one mental slot, an income bracket in another, and staring at a dropdown of employment categories that doesn't quite describe what they do. They don't abandon because the interest rate is uncompetitive. They abandon because their head is full.

Cognitive load is the mental effort a customer must spend to complete a task — recalling information, comparing options, or decoding an unfamiliar interface. When that effort exceeds what a person's working memory can comfortably hold, they don't push through with extra willpower; they disengage, procrastinate, or quit. Simplifying a customer journey, properly understood, means stripping out the decisions and demands the business didn't need to impose in the first place — not making the product simpler, making the thinking simpler.

This is the argument the CX industry keeps circling without quite landing on: most "friction" audits catalogue clicks, form fields, and page loads, and miss the heavier cost sitting underneath them — the mental arithmetic a customer performs at every decision point. You can remove three clicks and still exhaust someone if the fourth click asks them to hold four variables in mind at once. Cognitive load, not click count, is the real currency of journey design.

What is cognitive load in a customer journey?

Cognitive load theory comes from educational psychology, not marketing. John Sweller's 1988 paper, Cognitive Load During Problem Solving: Effects on Learning, published in the journal Cognitive Science, described how working memory has a limited capacity, and how instructional material that overloads it impairs learning regardless of how well-intentioned the material is. Sweller split load into three types: intrinsic (the inherent difficulty of the task itself), extraneous (load created by poor presentation — bad layout, unclear instructions, unnecessary steps), and germane (the productive effort of actually processing and understanding).

Applied to a customer journey, the translation is direct. Intrinsic load is unavoidable — a customer genuinely needs to decide how much cover to buy, or which flight to book. Extraneous load is everything else: unclear labels, redundant confirmation screens, jargon, a form that asks for information out of logical sequence, a call centre script that makes the customer repeat details they already gave the chatbot. Extraneous load is the only kind a business controls, and it is almost always the kind that kills conversion. Good journey design doesn't eliminate difficulty; it eliminates the difficulty that was never the customer's to carry.

Why do customers abandon journeys that aren't actually hard?

Because "hard" is subjective and cumulative, not objective and isolated. Working memory, per the psychologist George Miller's influential 1956 paper The Magical Number Seven, Plus or Minus Two in Psychological Review, can hold roughly seven items — later research narrowed the practical figure closer to four — before errors and fatigue set in. A journey rarely fails at one brutal step. It fails from accumulation: a login that requires switching to email for a code, a form that resets after a session timeout, a policy explained in three different ways across three touchpoints. Each moment is individually survivable. Stacked together, they exceed capacity, and the customer's brain does what tired brains do — it defers, defaults to "no," or hands the decision to a competitor with a shorter path.

This is why customer effort, not customer delight, tends to predict loyalty more reliably. The Corporate Executive Board's research, published by Matthew Dixon, Karen Freeman and Nicholas Toman as Stop Trying to Delight Your Customers in Harvard Business Review (July–August 2010), found that reducing customer effort was a stronger driver of repeat business and reduced switching than attempts to exceed expectations. Their Customer Effort Score has since become a standard CX metric precisely because it measures the thing cognitive load theory predicts matters most: how much work the customer's mind had to do, not how delighted they felt about doing it.

How is cognitive load different from friction?

Friction is the observable obstacle — the extra field, the broken link, the slow page. Cognitive load is the internal cost that friction produces, but it can exist without any visible friction at all. A beautifully designed app with instant load times can still overload a customer if it presents twelve equally weighted options with no hierarchy, or if it uses internal jargon the customer has to translate. Richard Thaler's distinction between ordinary friction and sludge — friction deliberately or carelessly left in a process that benefits the business at the customer's expense — is useful here, but it only captures the structural half of the problem. The other half is presentational: how much a customer has to hold in their head, not just how many steps they have to click through.

This distinction matters for where you intervene. A friction audit fixes broken forms and slow checkouts. A cognitive load audit asks a harder question: at each step, how many things is the customer being asked to compare, remember, or decide simultaneously — and how many of those could the business decide, default, or recall on the customer's behalf?

Where does cognitive load hide in a typical journey?

It rarely announces itself. It accumulates in places journey maps often treat as neutral or administrative. The most common sources include:

• Choice overload — presenting more options than the decision warrants. Sheena Iyengar and Mark Lepper's well-known 2000 study in the Journal of Personality and Social Psychology, often referred to as "the jam study," found that shoppers offered a smaller selection of jams were substantially more likely to purchase than those offered a much larger array — more choice, past a certain point, suppressed action rather than encouraging it.
• Redundant recall — asking a customer to re-enter information the business already holds, forcing them to remember and retype rather than simply confirm.
• Sequence mismatch — collecting information in an order that matches internal systems rather than how the customer naturally thinks through the task.
• Terminology load — internal or legal language ("beneficiary designation," "tenure segment") that forces a translation step in the customer's head before they can even begin deciding.
• Channel-switch cost — moving a customer from app to email to phone mid-task, each switch demanding they re-orient and re-explain themselves.
• Unbounded decisions — asking a customer to decide something with no reference point, no default, and no sense of what "normal" looks like.

None of these show up as an error in an analytics dashboard. They show up as a slow decline in completion rates, a rise in "I'll come back to this later," and contact-centre calls that begin with "I just need someone to explain this to me."

How do you simplify a journey without stripping out necessary choice?

Simplification is not minimalism for its own sake — removing a genuinely needed step just to shorten a form usually creates a different problem downstream. The discipline is to distinguish intrinsic difficulty the customer must carry from extraneous difficulty the business imposed. A practical sequence for doing that:

1. Map the journey at the decision level, not the screen level. For each step, note not just what the customer sees, but what they must recall, compare, or decide before moving on. This is where structured journey mapping earns its keep — a map that only records touchpoints misses the cognitive demand sitting inside each one.
2. Classify each demand as intrinsic or extraneous. Ask plainly: does the customer need to make this decision, or could the business pre-fill, default, or infer it? Most extraneous load survives simply because no one asked this question of it directly.
3. Sequence by logic, not by internal process. Reorder steps so information flows the way the customer's mind already organises the task, even if that means restructuring backend workflows to match.
4. Replace open decisions with sensible defaults. Where a decision must remain the customer's, pre-select the option that fits most people, and let them override it rather than build it from nothing.
5. Compress recall to recognition. Show information back to the customer for confirmation rather than asking them to retype or remember it — recognition is a dramatically lighter cognitive task than recall.
6. Test with a stopwatch and a straight face, not a satisfaction survey. Time-to-completion and error rate expose cognitive load more honestly than a five-point happiness scale collected after the fact.

This is, in effect, a simplification audit rather than a redesign brief — and it belongs upstream of visual design, in service design and process work, not downstream in interface polish.

What role do defaults and choice architecture play in reducing load?

A central one. Choice architecture — the deliberate structuring of the options and defaults presented to a decision-maker — is the single most effective lever for cutting cognitive load without removing genuine choice. Every default a business sets is one fewer active decision a customer's working memory has to hold. This is dual-process theory in practice: Daniel Kahneman's distinction between fast, automatic System 1 thinking and slow, effortful System 2 reasoning explains why a well-chosen default lets most customers glide through on System 1, reserving their limited System 2 capacity for the one or two decisions that actually matter to them.

The cheapest way to remove cognitive load from a journey is not to redesign the screen — it is to decide, on the customer's behalf, the ninety percent of choices that don't need to be theirs.

This is also where Hick's Law earns its keep as a design heuristic: the time it takes someone to make a decision increases with the number and complexity of the options in front of them. A well-designed default doesn't manipulate the customer toward an outcome that harms them — that tips into sludge and erodes trust the moment it's noticed. Used ethically, a default simply reflects what the majority of similar customers would sensibly choose, with a clear and effortless path to change it. Renascence's behavioral economics work with clients across banking, retail and telecoms consistently returns to this same principle: reducing the number of active decisions a customer must make is more powerful, and more durable, than adding features designed to delight them once they've made it through.

How do you measure cognitive load before and after a redesign?

Cognitive load doesn't show up cleanly in NPS, but several proxies get close enough to act on. Task completion time and error rate are the most direct — both rise sharply once a step exceeds working-memory capacity. Drop-off location within a multi-step flow tells you precisely where load peaks, which is usually not where the map assumed. Contact-centre volume tied to a specific step is a strong signal too: a spike in calls asking "what does this mean?" is a cognitive-load symptom disguised as a support issue. Customer Effort Score, asked immediately after the specific task rather than about the relationship in general, remains one of the more reliable self-report measures, precisely because it asks about effort rather than sentiment.

The more rigorous approach treats this as ongoing diagnostics rather than a one-off audit. A CX maturity assessment that includes decision-complexity as an explicit criterion catches load creep before it shows up in churn figures — because complexity rarely arrives in one redesign. It accumulates one compliance requirement, one extra data field, one new product option at a time, until a journey that was simple two years ago is quietly overloaded today. Renascence's own CX Maturity Assessment is built to surface exactly this kind of accumulated complexity across an organisation's building blocks, rather than waiting for it to surface as an abandonment statistic.

It's also worth being honest about where load hides longest: in journeys involving multiple internal teams or external partners, where no single owner is accountable for the customer's total cognitive burden across handoffs. As explored in Measuring Partner-Delivered Customer Experience: Why It Fails, complexity compounds precisely at the seams between organisations — and those seams are where extraneous load is hardest to see from inside any one team's dashboard. The same is true of real-time systems: as covered in Real-Time Customer Data Platforms: Speed Over the Single View, more live data doesn't reduce a customer's mental burden unless it's translated into fewer decisions, not just faster ones.

What does a genuinely simplified journey look like in practice?

It looks quieter than most redesigns. Fewer fields, but each one exactly where the customer expects it. Fewer options, but the right one pre-selected and easy to change. Fewer handoffs, and where a handoff is unavoidable, no repetition of information already given. The customer rarely notices simplification as a feature — they notice its absence as friction, and its presence as an experience that felt, in their words, "easy," without being able to say precisely why. That inarticulate ease is the actual signature of good cognitive load design, and it's a far more reliable indicator of quality than praise for any single clever feature.

Journey redesigns that chase visual polish without addressing decision load tend to produce a familiar failure: a beautiful interface that customers still abandon at the same step, because the interface was never the problem. The fix sits earlier, in process design and in how a customer experience function decides what to ask of the customer's mind in the first place, not in how prettily the question is presented on screen.

The discipline this demands going forward

Complexity is not a one-time design flaw to be fixed and forgotten. It is a tax that compounds quietly with every new product, regulation, and system integration layered onto a journey that once felt simple. The organisations that stay easy to do business with are the ones that treat cognitive load as a metric to be monitored, not a problem to be solved once. Every proposed addition to a journey — a new field, a new option, a new step — deserves the same question asked of it before it ships: what is this asking of the customer's mind, and have we earned the right to ask it? Answer that honestly, every time, and simplicity stops being a redesign project. It becomes how the business thinks.