There is a complaint I hear in some version on almost every product team.
"There are too many steps."
"Why does this take so many clicks?"
"Can we just put everything on one screen?"
It usually comes from an executive looking at a flow and feeling like it is heavier than it should be. Sometimes it comes from a practitioner trying to figure out what feels off about an experience. And sometimes it comes from the practitioner on the other side of the argument, the one insisting that the number of clicks is not actually the problem.
Here is the thing. Both sides are partly right, and both sides are usually missing what is really going on.
Clicks are a symptom, not the disease
When someone says a flow has too many clicks, they are rarely upset about the clicks themselves. They are upset about how the experience feels. Slow. Effortful. Confusing. The click count is just the most visible thing to point at, so that is what gets blamed.
But counting clicks tells you almost nothing on its own. A five-click flow can feel effortless if each step is obvious and the path forward is clear. A two-click flow can feel terrible if either of those clicks makes the person stop and think about what to do next. The pain is not in the quantity. It is in the friction.
I learned this clearly on a project where, on paper, the product had everything. All the right features. All the things users had asked for. User testing confirmed it. And yet using the product was genuinely painful. The filters people needed were buried. Getting to them took effort. The experience was friction-heavy in a way that no feature list could capture and no click count could explain.
The features were not the problem. The number of steps was not really the problem either. The problem was that every step asked the user to work harder than they should have.
What friction actually is
Friction is the small moment of resistance between someone wanting to do a thing and being able to do it. It shows up as hesitation. As a pause where the person is not sure what to click. As a back button pressed because they ended up somewhere they did not expect. As a form field that asks for information they do not have on hand.
None of these are about quantity. They are about clarity, predictability, and effort. A flow can be long and have very little friction. A flow can be short and be full of it.
This is why "reduce the number of clicks" is often the wrong instruction. If you collapse five clear steps into two confusing ones, you have technically reduced clicks while making the experience worse. You optimized the metric and lost the point.
Seamless does not mean invisible work. It means invisible effort.
There is a line from Futurama that captures this better than most UX writing I have read. In the episode "Godfellas," a god-like entity tells Bender, "When you do things right, people won't be sure you've done anything at all."
That is the goal of good experience design.
When a flow is designed well, the person moving through it does not notice the design. They do not think about the steps. They do not count the clicks. They just accomplish what they came to do and move on. The work that went into making it feel effortless is invisible to them, and that is exactly the sign that it worked.
A seamless experience is not one with the fewest steps. It is one where the steps disappear from the user's awareness because none of them required stopping to think.
So how do you actually diagnose it?
When someone on your team says there are too many clicks, treat that as a starting question, not a conclusion. The real questions underneath it are:
Where in this flow does the person hesitate? Watch a real user move through it. Do not guide them. Notice where they slow down, where they look around the screen, where they pull back. Those are your friction points, and they may have nothing to do with the click that prompted the complaint.
Is each step clear about what it is asking and why? A step that makes sense is not friction, even if it is one more step. A step the user does not understand is friction, even if it is the only one.
Is the effort proportional to the value? People will happily take several steps for something that matters to them. They will resent a single step that feels pointless. The question is not how many clicks, it is whether each one earns its place.
Is the friction in the design, or is it behind the design? Sometimes the experience feels heavy because of a layout or interaction choice. Other times it feels heavy because of a deeper structural issue, a confusing information architecture, a process that genuinely is more complicated than it needs to be, or a feature trying to do too much. Cutting a click will not fix a structural problem. It just hides it for a moment.
The takeaway
The next time someone tells you a product has too many clicks, resist the urge to immediately start removing them. Ask what is actually creating the friction. The answer is usually not the count. It is something about clarity, effort, or structure that the click count was standing in for.
The real measure of a good experience is not how few steps it has. It is whether the person moving through it ever had to stop and think about the steps at all.
When you get it right, they will not notice you did anything at all. And that is the point.
