How I Think About Website Redesigns Before Touching the Design

A website can need a redesign without needing a completely different look. It can also look painfully dated and still be doing a few things right. Before I start talking about layouts, colors, or photography, I want to know which parts are helping the business and which parts are getting in the way.

My career started in graphic design and art direction, so I care about how a website looks. I’m not going to pretend otherwise. But after launching more than 100 websites, I’ve learned that the visual problem is often easier to spot than the business problem.

If the phone isn’t ringing, a new homepage might help. It might also leave the actual problem untouched.

That’s why I approach a redesign as a business decision before I approach it as a design project. See examples of my website strategy and redesign work for a closer look at my approach in practice.

I Start With What the Business Needs More Of

“More leads” sounds like a clear goal until you start asking what counts as a useful lead.

A manufacturer might need quote requests from buyers with specific project requirements. An HVAC business might need service calls within a defined territory. A professional services firm might need fewer inquiries from people shopping only on price and more conversations with people who fit its expertise.

Those aren’t the same website assignment.

Before discussing design, I want to understand which services the business wants to grow, which customers it serves well, and what makes an inquiry worth pursuing. I also want to know what the business doesn’t want. That part gets skipped too often.

For a service company working around Jackson, Tennessee, a website that attracts calls from outside its service area can create activity without creating opportunity. Making the service area clear isn’t just a search consideration. It helps people decide whether to call.

I’d rather define a qualified inquiry at the beginning than celebrate a larger pile of unsuitable leads later.

I Separate a Traffic Problem From a Website Problem

Website lead generation depends on more than what happens after somebody arrives. It also depends on who arrives and what they expected to find.

I usually look at search traffic, paid traffic, important landing pages, and recorded inquiries before recommending a major rebuild. Not because those numbers tell the whole story. They help me ask better questions.

If very few potential customers reach the site, changing the design alone won’t solve the visibility problem. If Google Ads is sending people to a general homepage instead of a page about the service they searched for, there’s a mismatch to address. If visitors find the right page but can’t understand the offer, that’s a different issue.

It’s possible to have all three problems at once.

I also check whether the reporting deserves to be trusted. A click on a phone number isn’t necessarily a completed call. A form submission isn’t necessarily a qualified opportunity. Spam can make a report look healthier than the business feels.

Before setting a redesign target, I want a usable baseline: where inquiries come from, what people ask for, and whether those inquiries turn into real sales conversations.

I Look for the Questions the Website Isn’t Answering

One thing my design background taught me is that presentation directs attention. But you still need something useful to direct attention toward.

A website can have excellent photography and clean typography while leaving basic questions unanswered. What does the company actually do? Who is it a good fit for? Can it handle this particular job? What happens after someone reaches out?

I read the important pages with those questions in mind. Not just the homepage. Someone arriving from search may land directly on a service page and never visit the homepage at all.

For an industrial company, useful detail might include capabilities, materials, project requirements, or a clear explanation of the quoting process. For a home service business, it might be service availability, coverage, and how to request an appointment.

The content shouldn’t make people translate internal company language into an answer to their own problem.

I pay particular attention to claims like “quality service” and “customer-focused.” They’re easy to write and hard to use as a reason to choose someone. I want specifics the business can honestly support: relevant credentials, an understandable process, actual work examples, or experience that matters to the buyer.

I Walk Through the Next Step on a Phone

Looking at a website in a presentation isn’t the same as trying to use it.

I want to open it on a phone, find a service, locate the contact information, and work through the inquiry process. That simple exercise can expose problems that don’t show up in a desktop design review.

Maybe the phone number is difficult to tap. Maybe a popup covers the information. Maybe the form asks for details a prospective customer doesn’t have yet. Maybe the page takes long enough to load that I start wondering whether anything is happening.

Calls to action need judgment, too. “Request a Quote” makes sense when the visitor is ready to describe a project. It may be premature for someone who still needs to figure out whether the company offers the right service.

I don’t believe every form should be as short as possible. A few thoughtful questions can help qualify an inquiry and prepare the person responding. But every required field should have a reason to be there.

Then I check what happens after submission. Does the visitor get confirmation? Does the message reach the right person? Is someone responsible for responding? A redesigned form won’t fix an unattended inbox.

I Decide What Needs to Survive the Redesign

A redesign shouldn’t erase useful work just because everyone is tired of looking at the old website.

Before replacing pages, I want to know which ones attract relevant search traffic, generate inquiries, or answer questions customers regularly ask. Sometimes an awkward-looking page contains exactly the information a buyer needs.

That doesn’t mean leaving it untouched. It means understanding its value before changing it.

My SEO work makes me cautious about unnecessary URL changes and broad content cuts. If page addresses need to change, I plan redirects to the appropriate replacements. If pages are being combined, I check that useful information isn’t disappearing along with the old layout.

I also want tracking and form testing included in the launch plan, not treated as cleanup work.

The goal isn’t to preserve everything. It’s to avoid starting over in places where the business has already made progress. A cleaner navigation menu isn’t much of a win if customers can no longer find the service information they came for.

I Write Down the Decisions Before Reviewing Designs

After that initial work, I want a short, plain-language brief. Not a large document nobody will read.

It should identify the priority audience, the services that matter most, the questions the site needs to answer, and the actions visitors should be able to take. It should also name the current problems, the content worth keeping, and how performance will be evaluated.

This gives design decisions something firmer to stand on than personal taste.

Different people inside a company naturally want different things from the website. Leadership may be thinking about reputation. Sales may want better inquiries. Operations may be worried about promises the company can’t consistently fulfill. Those concerns need attention before they become competing requests on a homepage draft.

I still want room for creative judgment. The brief isn’t supposed to design the site in advance. It’s supposed to establish what the design needs to accomplish.

I also set expectations for the first stretch after launch. I’d look at whether forms and calls are being recorded, whether important pages remain accessible through search, and whether inquiry quality is moving in the right direction. A new website needs observation, not just a launch announcement.

Bottom Line

I don’t start a redesign by asking what the new website should look like. I start by asking what the current website is failing to help people do.

Before approving a new design, define a useful lead, walk through the customer’s next step, and identify what already works. Those decisions won’t pick your colors or typography. They’ll give those choices a purpose—and give you a better way to judge whether the redesign was worth doing.

Brian "JR" Williamson

Founder & Marketing Director

20+ Years in Marketing Strategy • SEO • Websites • Brand & Digital Growth

Florence / The Shoals, Alabama

Jackson, Tennessee

jr@limegroupllc.com

BrianJRWilliamson.com

Brian Williamson

Creative and strategic Website & Graphic Designer with 15+ years of experience in design,
branding, and marketing leadership. Proven track record in team management, visual
storytelling, and building cohesive brand identities across print and digital platforms. Adept at
developing innovative solutions that enhance efficiency, drive sales, and elevate user
experiences.

https://www.limegroupllc.com/
Previous
Previous

Why Good Design Should Make Marketing Easier to Understand

Next
Next

Why Cheap SEO Usually Becomes Expensive Later