Good UX often means hiding the mess, not exposing it

One of the most common mistakes is trying to surface that complexity in the name of transparency. Every step gets 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→. Every decision becomes visible. Every piece of logic confronts the user directly. The logic is understandable: if users can see what's happening, they'll understand it.

In practice, the opposite tends to happen. The more a user has to processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→, the harder the experience becomes to move through. Transparency about systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ complexity isn't the same as a clear experience.

Good UX rarely removes complexity altogether. What it does is manage it: deciding what the user needs to see, what can be handled invisibly, and how the experience can be shaped to feel 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.

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 journeys. None of that could simply be switched off. But the experience didn't need to surface all of it at once. Structuring flows more carefully and introducing information at the right moments made the processglossary×ProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term→ feel lighter without removing what was required underneath.

Across the NHS, the challenge was complexity 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 inconsistent approaches had created an environmentglossary×EnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term→ where users were regularly presented with more than they needed. Simplifying that wasn't about deleting content. It was about organising it so people could find what they needed without being confronted by everything else first.

With Travelbag, the complexity was commercial. Booking a holiday involves a lot of moving parts: pricing, availability, options, and decisions stacked on top of each other. Showing everything upfront creates hesitation. Breaking it into manageable steps and introducing detail only when 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→ rather than 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→.

Expose too much, and the experience feels heavy. Hide too much, and it feels untrustworthy. Good UX sits between those two, revealing just enough at the right moment. That's less about visual design than it is about structure: 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 given point.

Users rarely want to understand how a systemglossary×SystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term→ works. They want to complete a task. The more effort that requires, 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 at once, but revealing it in a sequence that feels natural.

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. When that's done well, the complexity doesn't disappear. It just stops being the user's problem.