UX
Simplicity is not removing things, it is organising them
Simplicity is often treated as reduction, but that’s rarely where the real gains come from.
Why simplicity usually comes from sequencing, hierarchy and structure, not just stripping features away.
In short
Why simplicity usually comes from sequencing, hierarchy and structure, not just stripping features away.
Why reduction often misses the point
On the surface, that makes sense. Less to deal with should mean less effort.
But in practice, that’s rarely how it works.
I’ve seen projects where simplicity was interpreted as cutting things out. Content removed, options reduced, glossaryDelightMoments that exceed user expectations.Open glossary term shortened. The result looked cleaner, but it didn’t necessarily work better. In some cases, it created new problems because information people relied on had disappeared, or decisions became harder because glossaryContextThe surrounding conditions that shape behaviour and decisions.Open glossary term was missing.
What looked simple was actually incomplete.
The reality is that most products aren’t simple.
They carry complexity because the problems they solve are complex. 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 just because you want a cleaner interface.
Trying to remove it entirely usually just pushes the problem somewhere else.
Where simplicity actually comes from
I’ve worked on glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term where the instinct was to reduce steps, when the real issue was how those steps were structured.
In one case, users were being shown too much too early, with multiple decisions presented upfront. The thinking was to remove options to make it feel simpler. What actually helped was reorganising the glossaryDelightMoments that exceed user expectations.Open glossary term 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.
Simplicity usually comes from putting things in the right place, not just taking things away.
What this looks like at scale
I saw this at scale working with the NHS, where hundreds of sites, different teams, and inconsistent approaches had created an glossaryEnvironmentA specific setup where software runs, such as development, staging, or production.Open glossary term 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.
The same principle applies in more transactional glossaryPain PointA specific problem or frustration users experience when trying to complete a task.Open glossary term. 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 feel far more manageable.
Again, nothing disappears. It’s just organised properly.
Key takeaway
Users experience simplicity when complexity is structured well, not when detail is removed indiscriminately.
Where structure does the heavy lifting
This is where structure does the heavy lifting.
Clear sequencing.
Logical grouping.
glossaryProgressive DisclosureProgressive disclosure is a design technique that reveals information gradually as needed.Open glossary term.
All of these help reduce the effort required to understand and move through something, without sacrificing the detail that sits behind it.
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.
In my experience, the biggest gains don’t 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.