Your UI Is Exhausting

A user opens your product with a task in mind. They hit one small ambiguity, then another. A label that needs a second read. A button whose purpose isn’t obvious until they click it wrong. A flow with one extra step more than it should have. Nothing breaks. Everything costs. The mental effort adds up, and at some point the cost exceeds what the task is worth to them. They close the tab. They don’t file a report, they don’t leave a review, they just stop.

You’ll read it in your analytics as abandonment. What it is, is exhaustion.

The brain has a budget. You’re spending it whether you mean to or not. And you never see the bill.

Four slots. That’s it.

For decades, designers quoted a single number: seven. George Miller published a paper in 1956 suggesting people could hold about seven items in short-term memory, plus or minus two. The design world turned it into a rule. Menus got capped at seven. Forms got structured around seven fields. The number stuck. What didn’t stick was the caveat: Miller himself called it rhetorical. He was pointing at a general limit, not measuring an exact one. Designers took a ballpark and built an orthodoxy around it.

Nelson Cowan reviewed the evidence in 2001 and found the real ceiling is closer to four. Four chunks of information, held and worked with at the same time, before things start falling out. Not seven. Four. Which means the interface you designed assuming users could track seven things in parallel was already over budget before anyone touched it.

That’s the container your interface is filling with every label, every choice, every element on the screen.

John Sweller studied how people handle mental effort and described three types of cognitive load. Intrinsic load is the real difficulty baked into the task itself. Filing taxes is hard, and design can’t change that. Germane load is the useful thinking: a user working something out, building understanding, moving forward. Both of those are load you want happening. They’re the point of the interaction. The third type is where design goes wrong.

Extraneous load is the effort caused by how information gets presented. Unclear hierarchy. Redundant steps. Labels that made sense in a ticket but not to a person trying to do a thing. This load is the designer’s creation, and it occupies the same working memory as everything else. The Nielsen Norman Group said it straight: “When the amount of information coming in exceeds our ability to handle it, our performance suffers.” The brain doesn’t distinguish between effort that serves the user’s goal and effort that doesn’t. It just keeps a running total. And when the total gets too high, the task stops.

Spend it on your navigation, and there’s less left for the decision.

They slow down. They guess. They leave.

One question at a time

TurboTax became the dominant consumer tax filing product in the United States and held that position for decades. The task it helps people do is one of the most demanding things a civilian has to sit down and complete. IRS forms are dense, conditional, full of instructions that assume the reader already knows what the instructions mean. TurboTax didn’t simplify the tax code. It simplified the experience of moving through it. One question per screen. Plain English everywhere it could be cut to plain English. A progress bar. Defaults that removed decisions the user didn’t need to make from scratch.

The design insight wasn’t clever. It was just honest: the task is already hard. Don’t add to it.

Competing products that stacked questions on a single screen, used technical terms without explanation, or left users to navigate between sections without clear guidance saw more people drop off. The task was the same. The extraneous load wasn’t. Users weren’t making a judgment about features or pricing. They were running out of capacity before they got to the end.

Intuit is not a company with a clean record. Their lobbying against free federal tax filing and their deceptive practices around the free tier are well documented. But a design principle doesn’t need a virtuous company to be true.

The extraneous load audit

Pull up your most-used screen and look at it like someone who has never seen it before.

Count what you’re asking a user to hold in mind before they can complete the thing they came to do. Count the labels that need interpretation. Count the steps that don’t serve the user’s goal but exist because someone asked for them at some point, or because removing them felt riskier than leaving them in. Each one is a withdrawal from an account that holds four things. Some of those withdrawals are the real cost of a real task. Most aren’t. Most are residue: things that got added because adding felt like progress, and nobody went back to ask what each one was costing the person on the other side.

One question decides it: does this require effort from the user that serves the user’s goal? If the answer is no, it goes. Not because minimalism is a virtue or sparseness is an aesthetic. Because your user has four slots in working memory and every slot you fill with your interface is a slot they can’t use for the task. The next hour you spend on a screen is better spent removing something than adding it.

Your users aren’t failing because they aren’t paying attention. They’re failing because you spent their attention before they got to the part that mattered.