A website transformation is an operating change, not a redesign
New templates and a fresh palette are the visible part. The part that decides whether a large firm's website stays good is ownership, governance and a content model the organization can keep up.
Every few years, a large firm decides its website no longer reflects who it is. A redesign gets scoped, an agency gets hired, and eighteen months later there is a beautiful new site. Two years after that, it has drifted back to where it started: outdated project pages, orphaned service lines, a news section nobody owns.
The redesign wasn't the problem. Treating it as a redesign was.
The site is a mirror of how content gets made
A website decays at exactly the rate the organization behind it produces and maintains content. If nobody owns a practice area's pages, they rot. If project descriptions come from proposals, they read like proposals. If publishing requires three approvals and a ticket, people stop publishing. No template fixes any of that.
What a transformation actually changes
A real web transformation changes the operating model, and the design follows:
- Ownership. Every section has a named owner and a review cadence — not a committee.
- A content model. Projects, people, services, markets and insights are structured so they connect to each other. A project page knows which experts worked on it and which services it demonstrates; a service page pulls its proof automatically.
- Governance that enables. Clear standards, templates and training so subject-matter experts can contribute without breaking the brand.
- Measurement tied to goals. Not just traffic — inquiries, applications, time with the content that matters to business development.
Design for the second year
The test of a website isn't launch day. It's the second year, when the launch team has moved on and the site is running on whatever systems were built underneath it. Build those systems first, and the site stays good because the organization keeps it good.
A scalable digital ecosystem is less about technology than about making the right thing the easy thing.
That's what "scalable" should mean: not that the site can hold more pages, but that the organization can keep every page worth reading.
Sources and further reading
- Content design: planning, writing and managing content — GOV.UK
- Creating helpful, reliable, people-first content — Google Search Central
- WCAG overview — W3C Web Accessibility Initiative