Every interface asks for something.
A click.
A decision.
A scroll.
A detail.
A wait.
A confirmation.
Even when an interface seems simple, it still imposes a certain amount of effort.
That effort is friction.
And friction is not necessarily a problem.
The problem appears when the effort we ask for is greater than the value the user expects in return.
01 / EVERYTHING HAS A COST
When someone visits a website, they do not start thinking in terms of interfaces.
They do not think:
“The system has too many steps.”
They think:
“This is getting complicated.”
The difference matters.
People do not directly experience our information architecture, components or design decisions.
They experience the effort required to achieve something.
Find.
Understand.
Compare.
Choose.
Buy.
Get in touch.
Each of those actions has a cognitive cost.
And that cost accumulates.
A poor experience rarely begins with one major problem.
More often, it emerges from a series of small points of resistance.
An unclear menu.
An ambiguous CTA.
An incomplete description.
A form that is too long.
A hidden delivery policy.
A variant that is difficult to select.
A page that takes too long to load.
Each element can seem insignificant on its own.
Together, they can change behaviour.
02 / FRICTION IS NOT ALWAYS VISIBLE
The most obvious friction is physical.
A button that does not work.
A page that takes too long to load.
A form that returns an error.
But there is another, more interesting kind:
cognitive friction.
It is the effort required to understand what is happening.
What am I looking at?
What can I do here?
What will happen if I click?
Which of these options do I need?
Is this product really right for me?
Can I return it?
When will it arrive?
Can I trust this store?
When an interface makes people answer too many questions for themselves, it shifts work from the system onto the person.
Design stops solving problems.
It starts creating them.
03 / WHEN THE USER HAS TO THINK
Not all thinking is bad.
Buying something important takes thought.
Comparing alternatives takes thought.
Evaluating a product takes thought.
The goal is not to eliminate thinking.
It is to eliminate unnecessary thinking.
There is a difference between:
“Which of these options best fits my needs?”
and
“What exactly does this option mean?”
The first question belongs to the decision.
The second belongs to the design.
When people spend mental energy deciphering the interface, that energy is no longer available to evaluate what we actually want them to consider.
The product.
The service.
The proposition.
The difference.
04 / FRICTION CAN BE USEFUL
Reducing all friction is not the answer either.
Some actions need friction.
A high-value purchase needs information.
An account registration needs security.
A return needs confirmation.
An irreversible action needs a second look.
Removing those steps just to make the experience faster can increase risk.
So the right question is not:
“How do we remove friction?”
It is:
“Where is friction worthwhile?”
Useful friction protects.
Unnecessary friction blocks.
Design means telling the two apart.
05 / TIMING MATTERS
The same friction can have different effects depending on when it appears.
Asking for an email address before explaining what we offer can feel premature.
Asking after demonstrating value can feel natural.
Showing twenty products at the start can create uncertainty.
Showing twenty products after defining a need can help people compare.
Asking for an address too early can interrupt intent.
Asking once someone has decided to buy is part of the process.
Friction does not exist in isolation.
It exists within a sequence.
And behaviour depends on that sequence.
06 / USERS DO NOT LEAVE ALL AT ONCE
In ecommerce, we often talk about abandonment as if it were a single moment.
The user leaves.
But something usually happens first.
A doubt.
A contradiction.
A wait.
A difficulty.
A loss of trust.
A decision that has become too complex.
An effort that no longer seems proportional to the benefit.
Abandonment may be the last symptom of an experience that has been accumulating friction for some time.
That is why looking only at the final conversion is not enough.
We need to observe where behaviour starts to deteriorate.
Where doubt increases.
Where interaction disappears.
Where steps are repeated.
Where errors appear.
Where people go back.
Behaviour leaves clues.
07 / DESIGN IS THE DISTRIBUTION OF EFFORT
An interface cannot remove all effort.
But it can decide who carries it.
We can make users compare.
Or we can help them compare.
We can make them interpret.
Or we can explain.
We can hide information.
Or we can place it exactly where it is needed.
We can offer twenty decisions at once.
Or we can organise the experience so each decision appears at the right moment.
In this sense, designing an interface also means distributing effort.
The question is:
Who is doing the work?
If the system is not doing it, the user probably is.
08 / SPEED IS ALSO A MATTER OF PERCEPTION
Friction is not limited to interaction.
Speed changes perception too.
A slow interface does not only take longer.
It makes people doubt.
Did it work?
Should I click again?
Has the page frozen?
Is it worth waiting?
Performance is part of the experience because it directly changes behaviour.
A fast interface reduces uncertainty.
A slow interface introduces it.
And uncertainty has a cost.
09 / LESS FRICTION DOES NOT MEAN LESS DESIGN
There is a paradox.
The simpler an experience looks, the more work may have gone into it.
A process feels obvious because someone previously decided:
what to show,
what to hide,
what to order,
what to explain,
what to ask,
what to automate,
and what to remove.
Visible simplicity is often the result of many invisible decisions.
That is why a good experience is not about adding fewer elements.
It is about asking for less unnecessary effort.
10 / THE RIGHT QUESTION
When an interface does not convert, the first reaction is often to add more.
More information.
More arguments.
More buttons.
More discounts.
More messages.
More trust signals.
But sometimes the problem does not need more.
It needs less resistance.
Before adding anything, we should ask:
What effort is the user making right now?
Then:
Does that effort add value?
And finally:
Can the system do it for them?
That is where designing friction begins.
11 / FROM DESIGN TO CONVERSION
Conversion does not happen just because an interface looks attractive.
Or because it has a good CTA.
Or because the product is competitive.
Or because there is a promotion.
Conversion happens when enough conditions allow an intention to move forward.
Understand.
Trust.
Decide.
Act.
Resistance can appear at every step.
And each point of resistance changes behaviour.
That is why UX and conversion are not separate disciplines.
They study the same thing from different perspectives:
what a person does and what gets in the way.
12 / FRICTION IS ALSO A DECISION
Designing an experience does not mean making everything instantaneous.
It means deciding where effort should exist.
Which information deserves attention.
Which decision needs context.
Which action needs confirmation.
Which process can be simplified.
Which question can be removed.
Which doubt can be resolved before it appears.
Friction is always there.
Even when we cannot see it.
The only difference is who has to bear it.
CONCLUSION
A good interface does not remove every difficulty.
It removes the difficulties that should not be there.
Because every step we ask users to take has a cost.
Every decision has a cost.
Every second has a cost.
Every doubt has a cost.
And when we design an experience, we are constantly deciding which costs the system will take on and which the person will bear.
Friction is also a design decision.
The question is:
what exactly is it designing?