2026-02 · 3 min read
Where complexity ends up
Simplification is rarely neutral. Every workflow redistributes complexity somewhere — into the system, the organization, or the people using it.
Design does not remove complexity.
It decides who carries it.
That is one of the few patterns I've seen repeated across public services, enterprise software, and intelligent systems. The complexity rarely disappears. The real question is where it ends up.
Sometimes it remains visible. Sometimes it is pushed somewhere else and only discovered when something goes wrong.
A migration officer discovers a missing case-handling rule on the morning a deadline expires. A billing analyst realizes two reports calculate the same number differently during a board meeting. A clinician learns how a triage model prioritizes symptoms only after a patient challenges the outcome.
The complexity was always there. Someone simply moved it.
Complexity never disappears. Someone always carries it.
This is why many design problems become easier once you stop looking at screens and start looking at incentives.
A confusing form is rarely a typography problem. More often, it is a policy decision someone did not want to challenge. The interface is simply where the consequences become visible.
Somebody decided where the cost of that complexity should be paid. The applicant pays in time and uncertainty. The organization saves time in policy reviews. The complexity has not been removed. It has been redistributed.
This is one of the reasons enterprise and public-service design feel different from consumer products. The question is rarely whether something should be simplified. The question is for whom. And that question is usually organizational before it becomes visual.
Every workflow contains a model of how an organization believes work should happen. Reality is usually more complicated.
The model says a case moves through five steps. In practice, half the cases bypass step three because nobody can find the approver. The model says a second reviewer evaluates every comment. In practice, they trust the first reviewer's judgment most of the time and only investigate when something feels unusual.
The gap between process and reality exists in every organization. The interesting question is whether the system makes that gap visible.
A workflow tool that rigidly enforces the model often hides the gap instead of revealing it. The work still happens. It simply moves elsewhere — into spreadsheets, into chat messages, into side channels, into the unwritten knowledge of the people who have been there the longest.
The system reports a clean process. The clean process is fiction.
The more honest design question is: what workflow are people actually running? And what would it take to support that workflow instead?
Sometimes the answer is to formalize the workaround. Sometimes it is to expose the gap so the organization can address it. Almost never is it to enforce the model more aggressively.
Complexity has to live somewhere. Either it lives inside the system, where people can reason about it, discuss it, and improve it. Or it lives in the gap between the system and the work, where it quietly accumulates until nobody wants to touch it.
The decision about where complexity is allowed to live is one of the most consequential design decisions an organization makes. It is also one of the hardest to reverse.
Over time, I've come to think that much of Enterprise UX is exactly this. Not removing complexity. Deliberately deciding who carries it.