Good UX feels obvious, but it rarely is

You move through something without stopping. You don’t question it. You don’t notice it. It just works.

That’s usually when people assume it must have been easy.

It never is.

I’ve worked on journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ where the end result looked incredibly simple. A few steps, clear progression, nothing unnecessary. The kind of thing that feels like it could have been sketched out in an afternoon.

What that hides is everything that came before it.

The decisions that were challenged.

The steps that were removed.

The points of frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→ that had to be understood before they could be fixed.

Getting to something that feels obvious usually means working through a versionglossary×VersionA version is a specific iteration of software or a product at a point in time.Open glossary term→ that wasn’t.

I’ve seen this most clearly on projects where the starting point was anything but simple.

On work with the NHS, the scale alone made things complex. Hundreds of sites, different structures, different teams, and no consistent way of organising information. From the outside, it felt fragmented. From the inside, it had evolved that way over time.

The end goal wasn’t to make everything minimal. It was to make it make sense.

That meant rebuilding the structure, aligning teams, creating reusable patternsglossary×PatternA reusable solution to a common design problem.Open glossary term→, and putting a consistent approach in place so that users didn’t have to work out how each part of the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ behaved every time they moved through it.

When it worked, it felt straightforward.

Getting there wasn’t.

I saw a different versionglossary×VersionA version is a specific iteration of software or a product at a point in time.Open glossary term→ of the same challenge at Co-op Bank.

Here, the complexity came from legacy systemsglossary×Legacy SystemA legacy system is an outdated system that is still in use, often due to its critical role.Open glossary term→ and the way processesglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ had built up over time. You couldn’t just remove steps or start again. The constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→ were real. But that didn’t mean the experience had to feel heavy.

The work was in reshaping how those steps were presented, what users saw at each stage, and how the journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ flowed within those constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→. When that was done well, the experience felt easier, even though much of the underlying complexity still existed.

And I’ve seen it in smaller, faster-moving environmentsglossary×EnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term→ as well.

On eCommerce journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ like Travelbag, simplicity often comes down to confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→. Users are making decisions that carry weight, and the experience needs to guide them without overwhelming them. Too much information too early creates hesitation. Too little creates uncertainty.

Finding that balance so the journeyglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ feels natural, not forced, is where the real work sits.

That’s usually the part that doesn’t get seen.

Good UX isn’t about removing everything until nothing is left. It’s about making the right decisions at the right time, so the user doesn’t have to think harder than they need to.

It’s about sequencing, not just simplifying.

What feels obvious to the user is usually the result of a lot of iterationglossary×IterationIteration is the process of repeatedly improving a product through cycles of testing, feedback, and refinement.Open glossary term→ behind the scenes.

Journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→ being reworked.

Assumptions being challenged.

Details being adjusted until the whole thing holds together.

None of that is visible in the final experience, but it’s what makes it work.

That’s why make it simple is rarely a useful instruction on its own.

Simplicity isn’t something you apply at the end. It’s something you uncover by working through complexity properly.

In my experience, the best outcomes come from spending time understanding where the frictionglossary×FrictionFriction refers to anything that slows users down or makes it harder for them to complete a task. It can be caused by poor design, unnecessary steps, unclear messaging, or technical issues.Open glossary term→ actually is, what’s causing it, and what needs to change to remove it.

Sometimes that’s obvious.

Most of the time, it isn’t.

Because when UX is done properly, it doesn’t feel designed.

It just feels right.

And that’s what makes it look easy.