Your website is underperforming. Traffic’s flat. Users bounce. You’re losing conversions you should be winning. So you call a designer, or you call a copywriter, or you call a marketing strategist. They’ll tell you the site needs a refresh. Better visuals. Stronger messaging. A rebrand.
They’re wrong.
Or rather, they’re looking at the symptom and calling it the disease. What you’re actually dealing with is an operational breakdown — the invisible machinery that keeps your website breathing. And no amount of redesign work fixes machinery that’s rusted out.
I’ve watched this pattern repeat across dozens of organizations. The website problem isn’t the website. It’s the system that’s supposed to maintain it.
The Fortune 500 That Rebuilt Components 21 Times
Here’s a real case: a large company’s web presence had sprawled into 21 separate web properties over ten years. Different domains, different hosting, different templates. They looked catastrophic — which was the problem everyone kept talking about.
“We need a redesign,” the leadership said. “We need one brand voice across all channels.”
But when we started digging into why each property looked different, it wasn’t creative rebellion. It wasn’t that one designer had a different aesthetic than another. It was that nobody could find the other designers’ work. There was no shared component library. No naming conventions. No documentation of what a button should look like or how a form should behave.
So when the fourth property launched, and it needed a dropdown menu, the team there built their own. They didn’t know there were three other versions already built. When a fifth team needed a modal dialog, same story.
Seventy percent of component rework was happening invisibly across that organization, year after year, because the operational infrastructure didn’t exist to prevent it.
The fix wasn’t a redesign. It was naming conventions. User stories. A unified system with clear governance. Once the operational layer was in place, the properties started to converge naturally. Quality went up. Build time went down. Brand consistency followed.
The Community Health Organization Hiding From Its Own Website
I’ll never forget the director who told me, flat out, “We stopped using our website three years ago.”
They were a community health nonprofit with about 50 staff and a meaningful mission. But their WordPress site had become unmaintainable. Adding an event took two hours. Updating a staff bio meant navigating a tangled post structure that nobody had documented. The database was so cluttered with old content, old plugins, old user roles, that even simple edits would break something.
So they did what made sense: they started directing people to their parent organization’s website instead. Not because it was better designed. Not because it had better messaging. But because it was operationally possible to use it.
Here’s what kills me about this story: the staff wanted to maintain their own site. They had energy for it. But the operational burden was so heavy that it crushed any energy they had. Every update felt like debugging code. So they gave up.
We spent maybe three days mapping their actual workflow. What content changes monthly? What changes rarely? Who owns what? What does a typical update look like? Then we rebuilt the operational layer. Simpler structure. Better templates. Clear ownership. Fewer decision points.
Within two months, they were maintaining their own site again. The content got fresher. The people got pride back. The site started performing because it reflected current reality instead of three-year-old decisions.
The Therapy Practice’s Taxonomy Problem
A therapy practice had two websites that both needed help. Users complained they couldn’t find information. Navigation was a maze. Search didn’t work.
The design firm they’d hired wanted to simplify the information architecture. Create a better navigation system. Make it more intuitive.
But here’s what actually happened: categories had accumulated like sediment. “Services” had become Services and Services-New and Services-Updated. “About Us” had grown to include pages about the mission, the team, the practice values, the team values, the clinical philosophy, and the history. Nobody had cleaned house in five years because there was no process for it.
When we walked through the site with the team, it became clear that the users weren’t confused by bad design. They were confused because the site reflected organizational confusion. The categories hadn’t been pruned because nobody owned the taxonomy. The decision-making process for what went where was invisible.
The fix wasn’t a new navigation design. It was operational: define a clear taxonomy. Own it. Make decisions about what stays and what goes. Create a simple governance process for new content. Then the navigation could be straightforward because the structure itself would be coherent.
The Pattern
You see it yet?
Every organization I’m describing thought they had a design problem or a marketing problem. Somewhere along the way, someone said, “We need a redesign.” But the redesign wouldn’t have fixed anything, because the underlying system was broken.
- The Fortune 500 didn’t need better-looking websites. They needed systems to prevent rebuilding the same component twice.
- The nonprofit didn’t need a better user experience. They needed operational simplicity so that maintaining the site didn’t feel impossible.
- The therapy practice didn’t need better navigation. They needed to own their taxonomy and make decisions about it.
The pattern is consistent: what looks like a design or marketing problem is actually an operational breakdown. The website isn’t performing because the machinery that runs it is rusty.
We Fix Systems, Not Surfaces
This is what separates some approaches from others. A lot of firms will come in, audit your website, deliver a report with recommendations, and leave. You get a PDF. You get a to-do list. Then you’re responsible for building your way out of it.
We don’t work that way.
We stay in the trenches. We map your workflows. We sit with your team and understand how content actually gets made, how decisions actually get made, how handoffs actually happen. Then we design the operational system that makes all of that possible. And we stick around until the system works.
This isn’t romantic. It’s not consultancy theater. It’s the kind of work that’s invisible to everyone outside your organization, but it changes everything about what you can actually ship.
Because here’s the thing: a better design won’t survive a broken system. Good copy won’t matter if nobody can keep it updated. The best information architecture in the world doesn’t help if you can’t decide what goes where.
But fix the system, and you suddenly have room to do good design work. You have bandwidth to write better copy. You can actually iterate and improve.
The Question You Need to Ask
Before you hire anyone to redesign your website, ask yourself this: Do I have the operational infrastructure to maintain whatever they build?
If the answer is no, a redesign won’t save you. You’ll end up in the same place in three years.
If the answer is yes, great. Then a redesign might help.
But if you’re honest with yourself, the answer for most organizations is no. Not because you’re lazy. Not because you don’t care. But because nobody built you the system to maintain the work.
That’s the real problem. And that’s where the actual work begins.
If your website feels like it’s constantly breaking down, like updates take forever, or like you’re always planning the next redesign instead of maintaining the one you have — that’s not a design problem. That’s an operational issue. At Johns & Taylor, we help teams build the systems that make continuous improvement possible. Learn more about operational support for your web presence.
