The Clarity Problem
Most design failures aren’t failures of aesthetics. They’re failures of communication.
A button that looks beautiful but doesn’t clearly say what it does.
A flow that is technically complete but leaves people unsure if they’ve finished.
A dashboard that surfaces every metric except the one someone needs to act on.
Clarity is difficult because it requires understanding three things at once:
What the user already knows
What they’re trying to do
What they’re worried might go wrong
Good design sits at the intersection of all three.
What I’ve Learned Building Across Industries
Context shapes clarity more than any design system ever will.
At General Motors, clarity meant communicating emotion through form.
A hood line had to signal power before anyone even drove the car.
At Fi Life, clarity meant reducing a legally complex insurance purchase into a decision a first-time buyer could make in under ten minutes.
The Baymard Institute has documented the cost of getting this wrong. Around 18% of users abandon checkouts because the process feels too long or complicated.
At Carsome, clarity means something harder: showing used-car buyers exactly what they are getting.
In a market where buyers often enter with high anxiety and low information, we publish detailed inspection reports with every listing.
Not because it’s simple.
Because it’s transparent.
In an opaque industry, transparency becomes the product.
The principle stays the same.
The execution changes completely.
The Trap
Teams often mistake simplicity for clarity.
They aren’t the same thing.
Don Norman captured the distinction well:
“Complexity is a property of the world; confusion is a failure of design.”
The goal isn’t to eliminate complexity.
It’s to make it navigable.
Three Questions I Ask on Every Project
1. What does the user need to know right now?
Not everything. Just enough to take the next step.
2. What are they afraid of?
When users hesitate, it’s rarely because they don’t want the product.
Something introduced uncertainty. Find it. Remove it.
3. What happens if they get it wrong?
The best flows turn mistakes into detours, not dead ends.
Clarity Scales
When an interface is obvious, everything downstream improves.
Onboarding gets faster
Support tickets drop
Conversion improves
Not because you added features.
Because the existing ones finally make sense.
Design isn’t a finishing touch.
It’s a business function.