Most Products Don't Fail From Missing Features — They Fail From Demanding Too Much Thinking.
I was waiting at the train station.
My daughter was coming home from Joensuu for the holidays.
A couple stood nearby on the platform. The woman was holding her phone toward her husband, jaw tight, arm extended like she was presenting evidence in court.
He leaned in. Frowned. Tapped something. Frowned again.
They weren't fighting.
They were buying a train ticket.
I've watched interfaces do this to people for nearly three decades. Turn ordinary moments into friction. Turn patience into frustration. Turn a simple task into something that looks, from the outside, like a domestic dispute.
There's something we don't talk about enough in product design.
Not tools. Not trends. Not AI.
Energy.
Every product session begins with a finite amount of cognitive energy. And most interfaces spend it carelessly.
Products rarely fail because they lack features. They fail because they demand interpretation.
The user arrives mid-task. Mid-conversation. Mid-notification stream.
And we greet them with dashboards, badges, secondary CTAs, and optional everything.
We design as if users arrive fresh.
They don't.
They arrive exhausted.
Your Users Have a Cognitive Budget. Most Interfaces Blow It in Seconds.
I've started thinking about this in terms of cognitive budget.
Every session has one.
It's limited.
It's fragile.
And it compounds.
Interfaces either waste it, preserve it, or multiply it.
Most waste it.
Not maliciously.
Just habitually.
01 — Entry State
Your Users Don't Start From Zero. They Start From Chaos.
Users don't arrive focused.
They arrive mid-notification. Mid-context-switch. Mid-burnout.
If your interface assumes they have mental bandwidth, you've already lost them.
Clarity starts by designing for reality, not for ideal conditions.
02 — Signal
If Users Need to Interpret Your Interface, You've Already Failed
Primary intent must be instant.
The moment users pause to figure out what to do, you're burning their cognitive budget.
Explanation is not clarity. It's a symptom of bad design.
Good design makes the right action obvious. It doesn't add microcopy to apologize for confusion.
03 — Load
Complexity Doesn't Break Products. Overload Does.
Every badge, secondary CTA, and decorative element competes for attention.
Modern interfaces rarely break from being too simple.
They break from trying to show everything at once.
Complexity is additive. Clarity is subtractive.
Not minimal for aesthetics.
Minimal because cognition has limits.
04 — Outcome
When Cognitive Load Drops, Everything Else Goes Up
- Decision speed increases.
- Confidence increases.
- Retention increases.
Not because it looks better.
Because it performs under pressure.
Clarity compounds.
This Is the Foundation.
Not the Ceiling.
I hear this often: "But we want the product to feel magical."
Good. So do I.
But magic doesn't work on a broken foundation.
The moments users remember — the ones that feel effortless, even delightful — only land when cognitive load is already gone.
You can't wow someone who's confused.
Clarity first. Then magic.
When "Beautiful" Design Cost Hundreds of Millions in Lost Revenue
Early 2000s. A colleague built one of the most elegant navigation systems I'd seen — layered drop-down menus for one of the world's largest brokerage firms.
Beautiful. Structured. Sophisticated.
A senior stakeholder called it slow. Wanted the menus gone.
We knew removing layered visibility would increase cognitive load. We were trained to believe interfaces should stay out of the way.
He implemented the change anyway.
Orders executed faster. Transaction volumes increased by hundreds of millions.
That's when I understood: we weren't wrong about cognitive load. We were measuring the wrong kind.
We optimized for structural clarity. The market optimized for execution speed.
In high-pressure environments, the real cognitive cost isn't visual density.
It's hesitation.
He wasn't killing elegance.
He was removing delay.
This Isn't About Design Taste. It's About Survival.
In an exhausted digital environment, the product that requires less thinking wins.
Not the one that does more.
Taste is subjective. Cognitive cost is measurable.
And right now, your users are running on empty.
After 27 Years, Here's What Actually Matters
We talk endlessly about tools, trends, frameworks, AI, velocity, growth loops.
We rarely talk about reducing thinking.
That's strange.
Because that's what determines whether a product feels usable or exhausting.
Early in my career, I cared about elegance.
Later, I cared about systems.
Today, I care about cognitive cost.
Not because I've become less ambitious.
Because I've seen what breaks.
It's never the missing feature.
It's the accumulated friction.
The interpretation tax.
The small, repeated decisions that drain users dry.
Clarity isn't aesthetic minimalism. It's discipline.
The willingness to remove options that don't serve primary intent.
To say no to features that look impressive in demos but confuse in reality.
To resist compensating for unclear structure with more explanation.
Good products don't explain themselves.
They make the right thing obvious.
In most organizations, clarity gets negotiated away.
Sacrificed for speed, stakeholder compromise, "just in case" flexibility, feature parity.
Clarity requires authority.
And authority is uncomfortable.
I've Been Doing This Long Enough to Notice the Shift
When I started in 1998, the open office experiment felt like peak distraction.
It wasn't.
Today, my Slack averages one message per minute. Spread across 7 AM to 11 PM. The volume shifts depending on project phase, and there are always multiple projects running simultaneously.
Email hasn't decreased — it's multiplied.
Messenger. WhatsApp. SMS.
Bing bong this, ding dang dong that.
Some days it feels like I'm in the fields of Normandy.
And I'm the designer.
I control my environment more than most.
Why Now?
We're no longer designing for calm environments.
We're designing for cognitive exhaustion.
And here's what most people miss:
While the world gets noisier, human cognition stays the same.
Technology changes.
Trends change.
Tools change.
People don't.
When overload increases, the brain doesn't expand.
It narrows.
It filters harder.
It shuts down options faster.
This is why the same principle works in marketing, messaging, and product design.
StoryBrand built a framework on it.
Don Miller made millions teaching it.
Make thinking unnecessary.
It's not a UX principle.
It's biology.
In that context, clarity isn't polish.
It isn't style.
It's leverage.
The Teams That Win Don't Build the Most. They Remove the Most.
"Simplicity is the ultimate sophistication."
It's a da Vinci quote. Overused to the point of being a cliché.
But there's a reason everyone repeats it.
It's true.
My client Juha Ruokangas reminded me of this years ago, and I've watched it prove itself in every project since.
In product design, that line isn't poetry.
It's what Microsoft researchers had to learn in the early 2000s after discovering 90% of feature requests already existed in Word — just buried where no one could find them.
Sophistication isn't features.
It's restraint.
The discipline to cut what doesn't serve primary intent.
After nearly three decades, one pattern repeats:
The winners don't add capabilities. They eliminate decisions.
They make thinking unnecessary.
That's the work.
