Why your users feel exhausted before they finish signing up

Cognitive load is a concept from educational psychology, developed by John Sweller in the late 1980s. His original research showed that learning breaks down when working memory gets overwhelmed — and the same principle applies directly to how people use software.

Working memory is limited. Humans can actively process around four pieces of information at a time. When a product asks users to handle more than that simultaneously — new terminology, unfamiliar patterns, ambiguous choices — something gets dropped. Usually the task they came to complete.

Not all cognitive load works the same way, and the distinction matters for how you address it:

• Intrinsic load is the complexity inherent to the task itself. Configuring a payroll integration is genuinely complex — you can't reduce intrinsic load without simplifying the underlying domain.
• Extraneous load is complexity introduced by the design — unnecessary steps, unclear labels, poor grouping, inconsistent patterns across screens. This is what UX exists to eliminate.
• Germane load is the mental effort users spend on actually building understanding. This is productive. Users should be investing effort here, not in figuring out where to click.

The job of product design is to minimise extraneous load so users can handle the intrinsic load without burning out before they get there.

SaaS products accumulate extraneous load the same way they accumulate {{LINK:ux-debt}} — incrementally, feature by feature, sprint by sprint. Each individual decision looks fine in isolation. The aggregate is a product that feels exhausting.

Common sources:

• Settings pages that mix unrelated options across the same screen
• Onboarding flows that ask for information before users understand why it's needed
• Dashboards with twenty data points and no visual hierarchy to guide attention
• Tooltips and inline help that appear before users have tried anything
• Interaction patterns that change from one section of the product to another, forcing relearning on every new screen

The Nielsen Norman Group's research on minimising cognitive load identifies consistency as one of the highest-leverage interventions — because every deviation from an established pattern costs users mental effort, even if they can't articulate why.

Reducing cognitive load isn't about making a product 'simpler' in a vague sense. It's about removing the work the product is unnecessarily offloading onto users.

Progressive disclosure — show only what's needed at each step. Let users go deeper when they choose to, not before they're ready. A complex settings panel doesn't need to surface 40 options upfront.

Chunking — group related information together visually and spatially. Don't make users assemble the picture across the screen on their own.

Defaults that actually work — pre-fill options based on context. The fewer choices users have to make before getting value, the better. Every unnecessary decision is friction.

Pattern consistency — once a user learns an interaction in one part of the product, it should transfer everywhere. If it doesn't, you're making them pay a cognitive cost every time they encounter something new.

The products that feel effortless aren't always simpler underneath. They've done the work to absorb complexity on behalf of the user — and that work is intentional, not accidental.

When onboarding completion stalls, when support tickets cluster around specific screens, when users say 'I couldn't figure out how to...' — cognitive load is almost always part of the diagnosis. A {{LINK:ux-audit}} can surface where it's concentrated and what's driving it.

Related: {{LINK:information-architecture}}, {{LINK:progressive-disclosure}}, {{LINK:ux-debt}}