Buzzvel - Buzzvel • We design, we build & you scale
arrow-return

Good UX Doesn’t Always Mean Fewer Steps

Good UX Doesn’t Always Mean Fewer Steps
An image of Renato Rulli, the author of this post
5 min read

There’s a question that comes up surprisingly often during design reviews: “Can we reduce the number of steps?”

It’s a reasonable question. Nobody wants to make users go through five screens when they could accomplish the same thing in two. In fact, we have learned to associate good UX with speed, simplicity, and fewer clicks. However, somewhere along the way, “reduce friction” started becoming “reduce interactions.” And those aren’t necessarily the same thing.

A shorter flow can still be confusing and a longer flow can feel effortless. What really matters isn’t how many times a user clicks ‘Continue’, but how much effort it takes to understand what they need to do.

A step isn’t necessarily friction

Imagine a user needs to provide 30 pieces of information:

  • One approach is to put everything on a single page. There’s no navigation between steps, the user can see everything at once, and technically we’ve created a very short flow.

  • Another approach separates those same fields into four logical sections, showing one group at a time and clearly indicating the user’s progress. This requires more clicks and it might even take slightly longer. Although for many users, it will actually feel easier.

Breaking complex tasks into smaller pieces gives users room to focus on one decision at a time. It also gives designers opportunities to provide context exactly when it becomes relevant, rather than exposing every possible option from the beginning. This is why interaction count is such a poor proxy for usability.

Optimize decisions, not clicks

Consider two hypothetical flows:

  • In the first, there are only two screens, but each contains multiple sections, dependencies, actions, warnings, and decisions.

  • In the second, there are five screens. Each screen has a clear purpose and asks the user to make one or two related decisions before moving forward.

On paper, the first flow is more efficient. In reality, the second might require considerably less mental effort, which is paramount for complex products and to reduce mental load on the users.

Enterprise platforms, financial tools, healthcare systems, administrative portals, and other specialized software often deal with processes that are inherently complicated. There may be permissions, eligibility rules, documents, approvals, configurations, dependencies, and exceptions.

Sometimes friction is useful

There are also moments when users actually benefit from being slowed down, for instance, when submitting an important application, making a large payment, deleting information, publishing content, or sending something to hundreds of people.

Adding a review or confirmation step introduces friction, but that friction has a clear purpose. It gives users an opportunity to understand the consequence of an action and catch mistakes before they become difficult to reverse. Which is key with the increasing usage of AI in most processes.

If an AI system generates content, modifies data, or recommends an action, immediately applying its output might technically be the fastest experience. But speed isn’t always what the user needs. Showing the proposed change first and allowing the user to review, edit, approve, or reject it introduces another interaction. But it also gives the user control. This is the difference between unnecessary friction and intentional friction.

Unnecessary friction makes users work without providing meaningful value. Intentional friction creates clarity, confidence, safety, or control. The goal shouldn’t be to eliminate friction entirely. It should be to understand why it exists.

Of course, fewer steps can still be better

None of this means long flows are good by default. As a matter of fact, products constantly introduce steps that provide little or no value, such as: asking users for information the system already has, repeatedly confirming harmless actions, forcing navigation to another page for a closely related task, or splitting simple decisions across multiple screens. Those are exactly the kinds of interactions we should challenge.

But instead of asking only: “Can we remove this step?”. It can be more useful to ask: “What does this step do for the user?”

When reviewing a flow, I like to think about four questions:

  • Does it reduce cognitive load?

  • Does it prevent meaningful mistakes?

  • Does it provide necessary context?

  • Does it increase confidence or control?

If a step doesn’t accomplish any of these things, there’s a good chance it’s simply friction, and that’s when reducing the number of steps really does improve the experience. It's a balance of usability understanding and its tradeoffs.

The shortest flow isn’t always the best flow

When someone asks, “Can we do this in fewer steps?”, the answer shouldn’t automatically be yes. Instead, ask what would happen if those steps disappeared.

Would users make fewer decisions, or would the same decisions simply be compressed into a more complicated interface? Would the experience become easier, or just shorter? Would users move faster, or spend more time trying to understand what they’re looking at?

Ultimately, users don’t care how many screens a designer managed to eliminate. They care about whether they can accomplish what they came to do without confusion, unnecessary work, or unexpected consequences. The best flow is the one where every step earns its place.

Browse by Category

Subscribe to
Our Newsletter

Join 1,000+ people and receive our weekly insights, tips, and best practices.