UX
Good UX often means hiding the mess, not exposing it
Most systems are messy. Good UX is what stops that mess becoming the user's problem.
Why better user experience often comes from containing organisational complexity rather than surfacing it, and what it looks like to get that balance right.
In short
Why better user experience often comes from containing organisational complexity rather than surfacing it, and what it looks like to get that balance right.
Exposing complexity usually makes things worse
One of the most common mistakes is trying to surface that complexity in the name of transparency. Every step gets pushed into the glossaryInterfaceAn 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 glossaryProcessA 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 glossarySystemA 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.
The instinct usually comes from a good place, and often from a defensive one. Showing every step feels honest, and it means nobody can say they were not told. What it produces is an glossaryInterfaceAn 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 that has transferred the organisation's obligation to explain onto the user's obligation to read.
The more you expose, the more the user has to process. And the harder the experience becomes to move through.
Good UX manages complexity
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 glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term behind it isn't.
The judgement is about what the user needs in order to make the next decision, not what is true about the glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term. Those overlap less than they appear. Plenty of accurate information is irrelevant at the moment it is being shown, and being irrelevant is what makes it noise rather than transparency.
The test is whether hiding something would change what somebody chooses. If it would, it belongs on screen. If it only affects whether they understand the machinery behind the choice, it usually does not.
What this looks like in practice
At Co-op Bank, there were layers of checks, rules, and legacy glossaryConstraintsConstraints 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 glossaryProcessA 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 glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term. Different regions, different serviceInformation 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 glossaryEnvironmentAn environment is a specific configured setup where software runs, such as development, staging, or production, each with its own data and settings. Keeping them consistent is what makes behaviour in one predict behaviour in another.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 glossaryBuildA build is the process of compiling and packaging code into a runnable application.Open glossary term glossaryConfidenceConfidence is the level of certainty in a decision or outcome based on available evidence.Open glossary term rather than glossaryFrictionFriction 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.
Key takeaway
The goal isn't to remove complexity entirely. It's to control how and when users have to deal with it.
The balance
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: glossaryProgressive DisclosureProgressive disclosure is a technique that reveals information and options gradually, showing what is needed at each stage and keeping the rest one deliberate step away. It manages complexity without removing capability.Open glossary term, clear sequencing, and reducing the number of decisions a user has to make at any given point.
Where the line sits moves with the stakes. Somebody spending a few pounds wants to be left alone to get on with it. Somebody committing several thousand wants to see the working, and hiding detail at that point reads as evasion rather than simplicity.
What users actually want
Users rarely want to understand how a glossarySystemA 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 glossarySystemA 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.
None of this is an argument for concealment. Hidden and available are different things: a summary that can be expanded, a total that breaks down when tapped, a policy one link away. The complexity stays reachable for anyone who wants it, and stops being compulsory for everyone who does not.
