Design used to be the thing that held a site together. Now it’s often the thing that broke it — applied in pieces, by different people across different teams, none of them responsible for how it felt as a whole.
The result is a site that looks considered but somewhat disconnected, one moves to wrong direction. Pages that don’t connect. Sections that were each optimized for something different — conversions, SEO, a product launch, a rebrand — without anyone asking what happens when a person passes through all of them in sequence.
Enterprise sites make this especially visible. The scale of the organization means more teams, more campaigns, more moments where someone added something without inheriting the context of what was already there. A company with twelve product lines and six regional markets ends up with a site that reflects the internal structure of the business rather than the experience of someone trying to understand it from the outside.
Users don’t experience a website as fragments of pages or micro-stories. They experience it as a single entity, and they form a judgment about it the same way. When that judgment is vague distrust, or mild confusion, or just a quiet decision to leave, no single page is to blame. The design didn’t fail. It was never unified in the first place.
That’s the problem most redesigns don’t fix, because they treat the site as a visual problem. New typography, updated colors, a reorganized navigation. The surface changes. The fragmentation stays.
The fragmentation happened gradually and for understandable reasons. A marketing team updated the homepage for a campaign. An SEO audit added new landing pages. A product update required new documentation. Each decision made sense in isolation. Nobody was responsible for the whole, so nobody noticed when the whole stopped functioning as one.
This is how most sites actually get built now — not through design, but through accumulation. The original structure, if there was one, gets buried under layers of additions that each followed their own logic. The user journey that someone once mapped out becomes theoretical. The real journey is whatever path a visitor can piece together from what’s actually there.
Fixing it requires something most organizations are reluctant to do: step back from the page level entirely and look at the site as a system. Not what each page says, but what the site does. How it moves people how it makes someone feel. Where it loses users. What it’s asking someone to understand before it asks them to act.
That work is harder to scope and put in the brief than a simple redesign and harder to sell internally than a visual refresh. It doesn’t produce dramatic before-and-after screenshots. What it produces is a site where things connect — where a visitor who arrives without context can follow the logic of the experience and arrive somewhere useful.
A refreshed surface visuals built on fragmented structure doesn’t resolve the underlying problem. It raises the cost of eventually fixing it.
The sites that work well right now are not necessarily the ones with the most beautiful aesthetic. They’re the ones where someone maintained a point of view about the whole experience, made decisions about what the site was for, and held that line as the site grew. That’s rarer than it sounds.
At some point the person who understood the whole thing left, or moved on to something else, and nobody replaced them. Not the role — the understanding. Getting that back isn’t a design project. It’s a decision about who is responsible for how the site feels to someone who doesn’t work there.
Users arrive without context, without patience for internal processes, and without interest in how the decisions got made. They want to get something done, find what they came for without effort, and understand what actually matters to them. Everything else is internal.