So for whatever reason you have decided you need a complete redesign of your massive website.
Maybe the site looks like it was built during the Obama administration. Maybe your bounce rate is so brutal that visitors leave before the page finishes loading. Maybe the brand evolved and the site did not. Maybe the last PM duct-taped a redesign onto a redesign onto something a contractor built five years ago and then vanished.
Whatever the reason, if you are knocking on my door, something is not "a little off." Something is broken enough that you are considering tearing the whole thing down.
Which means the first question you need to ask — before mood boards, before sitemaps, before anyone opens Figma — is:
Is a redesign what we actually need?
Ask it out loud. Ask every stakeholder. Ask every designer, every engineer. Ask your spouse at the dinner table. Ask your dog. Ask the question until the answer stops sounding emotional and starts sounding like insight.
Then ask it again.
Because here is the truth: massive sites carry years of legacy decisions, technical debt, broken SEO hacks, mismatched content, and entire sections of the business that nobody wants to claim anymore. The worst thing you can do is sprint into wireframe mode without understanding the beast you are about to wake up.
Any time I take on a large rebuild — tens of thousands of pages, cross-functional teams, surprise stakeholder fly-bys, a backend glued together by someone who left the company in 2019 — the first thing I focus on is not wireframes. It is insight. This is how I do it.
Step 1: Validate the Redesign (Skip This and You Will Pay for It Later)
Before I run a single stakeholder interview, I form my own opinion. That means rolling up my sleeves and crawling through the data myself. Every keyword the site ranks for. Every orphaned page. Every broken redirect. Every user dead-end. Every outdated category and rogue content that might have made sense three years ago but absolutely does not today.
And in 2026, this audit is not just about traditional SEO metrics anymore. You need to know how your content performs in answer engines — ChatGPT, Perplexity, Google AI Overviews. Is your site being cited? Is it being surfaced? Or is it invisible to the entire AI discovery layer? Because if your redesign does not account for AEO, you are rebuilding a house on a foundation that is already cracking.
While I research, I am not just cataloging issues. I am contextualizing the entire experience from the user’s behavior. Tracing their actions to understand their intent so I can write user stories that actually set up the production team for success. In most of my work, that intent starts at the open mouth of a sales funnel.
Massive redesigns rarely fail because the design team was bad or the dev team could not code. They fail because nobody actually understood what they were supposed to do. Poor communication. Poor assumptions. No alignment. Insufficient insight. That is where projects die.
Step 2: Stakeholder Alignment (This Is Where the Chaos Starts)
Before a redesign kicks off, everyone believes they want the same thing. They do not. All previous conversations have been ambiguous at best. So you need to run a very simple, very effective alignment session and ask three questions that will determine the entire project.
Question 1: Why do you want to redesign the website right now?
There is always a real reason behind the official reason. Your job is to find the one everyone can rally around. Run a MoSCoW exercise — Must, Should, Could, Won’t. Watch what magically drops into MUST when people have to actually choose. It is eye-opening every single time.
Question 2: What can go wrong?
This question reveals everything. Social hurdles. Political landmines. Technical limitations nobody wants to admit. Team size issues. Shared Slack channels with way too many cooks. This is where you uncover the things that will actually derail the project — and none of them have anything to do with the redesign itself.
Question 3: What is the actual timeframe?
Every client on earth believes their website can be redesigned in about half the time it actually takes. This needs to be grounded in reality, not optimism. And in 2026, the math has changed. AI tooling made the unambiguous parts of a build dramatically faster and cheaper. A basic Next.js app that used to take three months and twenty-five grand now takes a day or two for a couple thousand. But the ambiguous parts — the KPIs, the UX strategy, the content architecture, the stakeholder alignment — those still take exactly as long as they always did. AI cannot do that work for you. People like me can.
Once those three answers are clear, break the redesign into three dimensions. Because the word "redesign" is useless without specificity:
Look and Feel: same, minor tweaks, or full overhaul? Functionality: same, small adjustments, or major rebuild? Target Audience: same, updated, or totally different?
If leadership cannot agree on those three sliders, the redesign is already doomed. No matter how stunning the comps look.
Step 3: Talk to Real Users (Not the Persona You Built in 2016)
Got the green light? Good. Now go external. Talk to actual humans who use the product. I have never once walked away from a user interview without learning something new. If you have, you are not doing it right.
The bottom line is simple. Stakeholders tell you what they want. Users tell you what they need. Keep the interviews dead simple and actually listen:
Why did you choose this product over others? What do you love about it? What do you hate about it?
Those three questions uncover more truth than all the internal strategy work combined. The answers almost always reveal priorities that are completely different from what the team believed. This is where the redesign either gets smarter or gets riskier.
Once you hear from users, remap the audience fast. No overthinking. Who are they? What job are they hiring this product to do? Why this product and not the competitor? How do they actually use it? When and where? That becomes the lens for every major decision — navigation, search, content hierarchy, component behavior, conversion strategy, success metrics. Without that shared understanding, every team makes decisions based on preference instead of evidence. And that is when redesigns drift off the rails.
Step 4: Be Honest About the Size of the Monster
Massive redesigns are massive. Like, actually massive. Legacy tech nobody volunteers to touch. Outdated frameworks. Plugin and dependency sprawl. Poor indexing. Broken mobile experience. Years of "temporary fixes" that became permanent. Pages created for campaigns nobody remembers. Content that ranks for keywords you do not even want to rank for anymore.
That is the real work. Not the shiny new UI. Big redesigns are not visual refreshes. They are new products. And once it drops, everyone wants to play with the shiny new toy. So I hope you budgeted for QA, because if you did not acknowledge the monster upfront, you will hit the wall by month three when every hidden problem surfaces at the same time.
Step 5: If You Are Not Ready, Do Not Redesign. Improve.
I have had companies come to me dead set on blowing everything up. Half the time, they do not need to. Sometimes the smarter move is to improve page structure. Fix indexing. Modernize templates. Clean taxonomy. Consolidate pages. Start following an actual design system. Improve speed and performance. Focus on the most critical user paths first. Get your content structured for answer engines so AI systems can actually find and cite you.
Not glamorous. But it can yield a massive return with a fraction of the commitment. A massive redesign should be a last resort — a decision made with evidence-based research and projected results, not emotion.
The Real Truth Behind Big Redesigns
Here is my honest take. A massive redesign is not a design project. It is a change event that will completely alter the company’s trajectory over time, for better or worse. If the business is not aligned, the product is not aligned. And if the product is not aligned, any investment is a waste. Period.
When you get insight and alignment right, the project runs smoothly. And dare I say it — on time.
My Final Advice
Before you touch a single pixel, ask yourself:
Do we need a redesign, or do we need clarity?
If it is clarity, solve that first. If it is truly a redesign, go in with an open mind, your data in hand, and your people aligned.
That is the difference between a successful product and a really expensive digital souvenir.
If you want to talk about what this looks like for your project, hit me up. But come with your data. I do not do guesswork.