Good UX often means hiding the mess, not exposing it

From the inside, it usually makes sense.

From the outside, it rarely does.

One of the biggest mistakes I see is trying to expose that complexity in the name of transparency.

Every step is shown.

Every decision is surfaced.

Every piece of logic is pushed into the interfaceglossary×InterfaceAn interface is the point of interaction between a user and a system, where inputs are made and outputs are received. It can be visual, physical, or conversational.Open glossary term→.

The thinking is that if users can see what’s happening, they’ll understand it.

In reality, the opposite tends to happen.

The more you expose, the more the user has to processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→. And the more they have to process, the harder the experience becomes to move through.

Good UX doesn’t remove complexity altogether. That’s often not possible.

What it does is manage it.

It decides what the user needs to see, what can be handled behind the scenes, and how the experience can be shaped so it feels simple, even when it isn’t.

I’ve seen this play out across very different environmentsglossary×EnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term→.

At Co-op Bank, there were layers of checks, rules, and legacy constraintsglossary×ConstraintsConstraints are limitations or restrictions that impact how a product or solution can be designed or built.Open glossary term→ sitting behind even relatively straightforward journeysglossary×Pain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term→. None of that could simply disappear. But the experience didn’t need to expose all of it at once. By structuring flowsglossary×DelightMoments that exceed user expectations.Open glossary term→ more carefully and introducing information at the right moments, the process felt lighter without removing what was required underneath.

Across the NHS, complexity came from scale rather than systemsglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→. Different regions, different content structuresservice×Information ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service→, and different ways of doing things had created an environmentglossary×EnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term→ where users were often presented with more information than they needed. Simplifying that wasn’t about deleting content, it was about organising it in a way that made sense, so people could find what they needed without being overwhelmed by everything else.

And in eCommerce, with Travelbag, the challenge was slightly different again. Booking a holiday involves a lot of moving parts, pricing, availability, options, and decisions. Trying to show everything upfront creates hesitation. Breaking that down into manageable steps, and only introducing detail when it’s needed, buildsglossary×BuildA build is the process of compiling and packaging code into a runnable application.Open glossary term→ confidenceglossary×ConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term→ instead 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’s the balance.

If you expose too much, the experience feels heavy.

If you hide too much, it feels untrustworthy.

Good UX sits in the middle, revealing just enough at the right time.

This is where structure matters more than visuals.

Progressive disclosureglossary×Progressive DisclosureProgressive disclosure is a design technique that reveals information gradually as needed.Open glossary term→, clear sequencing, and reducing the number of decisions a user has to make at any one point all contribute to an experience that feels simple, even when the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ behind it isn’t.

It’s not about stripping things back for the sake of it. It’s about controlling how complexity is presented.

In most cases, users don’t want to understand how everything works.

They just want to get something done.

And the more effort it takes to do that, the more likely they are to stop.

That’s why good UX often involves doing the opposite of what instinct suggests.

Not exposing more, but less.

Not explaining everything, but guiding just enough.

Not showing the full picture all at once, but revealing it in a way that feels natural.

Because the goal isn’t to make the systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ understandable.

It’s to make the experience usable.

And when that’s done properly, the mess doesn’t disappear.

It just stops being the user’s problem.