UX
Simplicity is not removing things, it is organising them
Simplicity is often treated as reduction. That's rarely where the real gains come from.
Why simplicity usually comes from sequencing, hierarchy and structure rather than stripping features away.
In short
Why simplicity usually comes from sequencing, hierarchy and structure rather than stripping features away.
Why reduction often misses the point
Projects where simplicity was interpreted as cutting things out would often look cleaner, but not necessarily work better. In some cases, they created new problems: information people relied on had disappeared, or decisions became harder because glossaryContextContext is the set of surrounding conditions that shape how someone behaves and decides, including their goal, their environment, their time pressure, and what happened immediately before. The same action can mean different things in different contexts.Open glossary term was missing. What looked simple was actually incomplete.
Most products aren't simple because the problems they solve aren't simple. Pricing glossaryModelA model is a system or representation used to process data and generate outputs, often trained to perform specific tasks.Open glossary term, compliance requirements, different user needs, glossaryEdge CaseAn edge case is a rare or extreme scenario that falls outside typical user behaviour.Open glossary term, glossarySystemA system is a collection of interconnected components that work together to achieve a specific function or outcome.Open glossary term constraints: none of that goes away because you want a cleaner interface. Trying to remove it entirely usually just pushes the problem somewhere else.
The removed detail also tends to reappear somewhere less convenient. Cut it from the page and it turns up in a support call, a follow-up email, or a help article nobody finds. 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 got simpler and the overall experience got more expensive to run.
Where simplicity actually comes from
On one project, users were being shown too much too early, with multiple decisions presented upfront. The instinct was to remove options. What actually helped was reorganising the flow so those decisions appeared when they were relevant, not all at once. Nothing was removed, but the experience became easier because it was better sequenced.
In another, content had grown over time and become difficult to navigate. The answer wasn't to delete large parts of it, but to restructure how it was organised so users could find what they needed without being overwhelmed by everything else.
That's usually where simplicity comes from. Not from taking things away, but from putting things in the right place.
Sequencing does most of the work here. The same set of questions can feel trivial or exhausting depending only on the order they arrive in and whether each one is asked at a point where the person can actually answer it. Almost nothing about the content changes.
Simplicity usually comes from putting things in the right place, not just taking things away.
What this looks like at scale
Working with the NHS, hundreds of sites, different teams, and inconsistent approaches had created an experience that felt complex and fragmented. The solution wasn't to strip content back indiscriminately. It was to rebuild the structure so it was consistent, reusable, and aligned to how users actually looked for information. Once that was in place, the experience felt simpler without losing what was important.
With Travelbag, booking a holiday involves a lot of detail: options, pricing, availability, choices that affect the outcome. Removing those things isn't realistic, but presenting them all at once creates hesitation. Breaking that complexity into stages, and introducing information at the right moment, makes the experience far more manageable. Nothing disappears. It's just organised properly.
glossaryConsistencyConsistency is the use of uniform patterns, behaviours, and visual elements across a product to create familiarity and predictability. It helps users learn once and apply that knowledge throughout the experience.Open glossary term is the other half of it at that size. Repetition is what lets somebody learn a glossaryPatternA pattern is a reusable solution to a design problem that recurs across products and contexts. It captures an approach already shown to work, so a team solves the problem once rather than every time it appears.Open glossary term once and stop reading carefully, and a structure that behaves the same way in every section can carry far more content than an inconsistent one carrying half as much.
Key takeaway
Users experience simplicity when complexity is structured well, not when detail is removed indiscriminately.
What users actually experience
What users experience as simplicity is usually just glossaryClarityClarity is how easily users can understand what is happening and what they need to do.Open glossary term. They know what to do. They understand what's happening. They aren't being asked to glossaryProcessA process is a defined sequence of steps used to achieve a specific outcome.Open glossary term more than they need to at any one time. That's what makes something feel easy.
The biggest gains rarely come from removing things. They come from stepping back and asking how everything fits together, what needs to be seen when, and how the experience can be shaped so it supports the user rather than overwhelming them. Because simplicity isn't about having less. It's about making what's there work properly.
This is also why simplicity cannot be assessed from a single screen. It is a property of the journey, and the only reliable way to judge it is to watch somebody attempt the whole task and count the moments where they stop to work something out.
