For a long time, one of the most repeated recommendations in product design was simple:
reduce friction.
Fewer steps.
Fewer fields.
Fewer clicks.
Less effort.
In many contexts, this makes sense.
No one should have to go through five screens to perform a simple action. A sign-up form shouldn't request information the product doesn't yet use. A recurring flow shouldn't force users to confirm decisions they already make every day.
The problem begins when making something “faster” becomes the primary goal of every interface.
Because not all friction is a flaw.
In some cases, it is precisely what prevents a bad decision.
Friction isn't the same as difficulty
A difficult interface requires effort because it was poorly designed.
The copy isn't clear.
The actions look the same.
The system provides no context.
Users have to figure out for themselves what happens next.
This type of friction should be removed.
But there is another kind.
Intentional friction appears when a product slows down an action to ensure that users understand its consequences.
It might be a confirmation before deleting data.
A review step before publishing something.
An additional step when changing an important permission.
An explanation before subscribing to a plan.
A waiting period before carrying out an irreversible operation.
These steps increase the immediate effort required.
But they can also reduce regret, errors, and loss of trust.
This is an important distinction.
Difficulty makes users work to understand the product.
Intentional friction makes the product work to protect users.
Fewer clicks don't necessarily mean a better flow
It is common to evaluate an experience by the number of steps required to achieve a result.
When an action used to take four screens and now takes two, there is a sense that the product has improved.
But click count is an incomplete metric.
A short flow may hide important information.
It may prompt a decision before users have enough context.
It may combine choices that should be considered separately.
It may make a dangerous action so easy that mistakes become inevitable.
Consider changing an administrative permission in a SaaS product.
It is possible to allow that change to happen with a single click. Technically, the flow would be fast.
But users may need to know which data that person will be able to access.
Which actions they will be able to perform.
Whether the change will be recorded.
Whether it can be reversed.
The additional step isn't delaying the task.
It is giving weight to a decision that already carries weight.
The goal of a good experience isn't to make everything feel inconsequential.
It is to help users move forward with a level of clarity proportional to the risk.
Different products require different paces
Not every part of a product should operate at the same speed.
Frequent, predictable, and reversible actions should usually be fast.
Filtering a list.
Saving a draft.
Duplicating a document.
Updating a visual preference.
In these cases, any unnecessary interruption quickly becomes frustrating.
But some actions are different in nature.
Deleting a workspace.
Canceling a subscription.
Transferring ownership of an account.
Sending a proposal to a client.
Publishing a change that affects other people.
Granting access to sensitive information.
Here, absolute speed shouldn't be the only criterion.
The greater the consequence, the greater the need for context, confirmation, and recovery options.
The problem is that many interfaces treat every action as though it were equivalent.
The same button.
The same hierarchy.
The same level of ease.
The same lack of context.
Then, when something goes wrong, it seems as though the user was responsible.
But perhaps the product made a decision too easy when it should have been handled more carefully.
Removing friction may simply transfer the cost
One fewer step in an interface doesn't necessarily mean less work.
Sometimes, it simply means that the work has been transferred to another moment.
Users perform an action quickly but later need to contact support to reverse it.
They complete a sign-up process without understanding a setting, only to encounter problems when they start using the product.
They subscribe to a plan without understanding its terms, only to become frustrated when they discover a limitation later.
They grant a permission without realizing its scope, only to have to review every access level when something gets out of control.
The initial flow appears efficient.
The operation that follows absorbs the cost.
This is a common pattern in products that optimize only for the moment of conversion.
Everything is designed to make moving forward easier.
Very little is designed to ensure that moving forward actually makes sense.
In the short term, this may improve a metric.
In the long term, it may lead to cancellations, support requests, rework, and loss of trust.
An experience doesn't end when users click the primary button.
It continues through the consequences of that click.
Friction needs a purpose
This doesn't mean adding confirmations everywhere.
Excessive warnings also lose their effectiveness.
When a product asks, “Are you sure?” before every action, users learn to confirm without reading.
When every decision appears critical, none of them truly do.
Friction only works when there is a clear reason for it.
Before adding or removing a step, it is worth evaluating four points.
Can the action be reversed?
The harder a decision is to undo, the more context the product should provide beforehand.
Does the mistake have a real impact?
Accidentally changing a visual preference has a low cost.
A permanent deletion or permission change may affect data, people, and operations.
Does the user understand the consequence?
Knowing the name of an action doesn't mean understanding its full impact.
“Remove access” may sound simple, but what happens to the associated documents, integrations, and responsibilities?
Is the action frequent?
Interrupting a task performed several times a day creates frustration.
Interrupting a rare and critical decision can create a sense of safety.
These questions help move the discussion beyond the superficial issue of how many steps a flow contains.
The point isn't to decide whether the flow should be short or long.
It is to decide how much attention that action deserves.
Design also defines where users should slow down
There is an idea that a good interface is one that disappears completely.
In many situations, that is true.
Users shouldn't have to think about the mechanism when all they want is to complete a simple task.
But some decisions shouldn't disappear.
They need to be understood.
A good interface knows when to get out of the way.
And it knows when it needs to remain present for a few seconds longer.
It doesn't create arbitrary obstacles.
It creates pauses proportional to the consequences.
This may happen through clear copy, hierarchy, review steps, feedback, intermediate states, or the ability to undo an action.
Opening a confirmation modal won't always be necessary.
In many cases, making an action reversible is better than asking a question beforehand.
In others, showing the impact before execution will be safer than trying to fix the consequences later.
There is no universal component that solves this problem.
There is judgment.
The best flow isn't always the fastest
Mature products don't treat speed as an absolute value.
They understand that people need different paces at different moments.
Speed for what is recurring.
Clarity for what is new.
Context for what is complex.
Protection for what is irreversible.
The experience improves when a product stops removing steps automatically and starts evaluating the purpose of each one.
Some friction exists because the system was poorly designed.
Other friction exists because the decision matters.
Knowing how to distinguish between the two is part of the work of design.
In the end, a good interface doesn't make every action easier.
It makes the right action easier, with the right level of awareness.
Share on:
No spam. Only content worth opening.