Complexity

Summary

Complexity is the work a system cannot avoid. It can live in the interface, the organisation, the user's head, or the machinery underneath, but it always lives somewhere. Design is the act of deciding where that work belongs, who can see it, and who has to carry it.

Framing

The easiest mistake is to confuse a simple surface with a simple system. A clean interface can hide messy rules, brittle operations, invisible labour, or assumptions the user never gets to inspect. That may be the right trade. Not every detail deserves attention. Not every choice should be pushed to the surface. But displaced complexity still has a life. It returns as maintenance, support debt, fragile defaults, confused users, or misplaced confidence. A system can feel effortless at the point of use because the difficulty has been moved somewhere else: into process, policy, infrastructure, or someone else's judgement. Simplicity becomes theatre when no one is responsible for the complexity it conceals. Designing with complexity means staying honest about the remainder. Sometimes the right move is to reveal more. Sometimes it is to absorb difficulty on behalf of the user. Sometimes it is to make the system's limits visible before they become consequences. Complexity is not the enemy of good design. Unowned complexity is.

Core tensions

• Simplicity vs honesty
• Surface clarity vs systemic cost