When a Website Redesign Won't Fix the Business Problem

A redesign will not fix a problem caused by unclear positioning, an unconvincing offer, unsuitable traffic, poor lead handling or missing measurement. It can improve structure, usability and presentation, but it cannot repair every part of the commercial system around the website. Before commissioning a redesign, identify where the journey from attention to customer actually breaks.

“Low website performance” is a symptom, not a diagnosis.

Replace the proposed solution with an observable problem

“We need a new website” begins with a solution. Start by describing what is happening instead.

For example:

• visitors do not understand the offer;
• the website attracts enquiries that are a poor fit;
• sales staff rarely use the site in conversations;
• the same basic questions appear on every call;
• important pages receive traffic but few meaningful actions;
• the team cannot publish or update essential information;
• nobody knows which channel generated an enquiry.

Each symptom has several possible causes.

A low number of enquiries could result from an unclear call to action, a technical failure, insufficient relevant traffic or an offer that does not match what visitors need. Redesigning without separating those causes risks improving the appearance of the wrong system.

Diagnose five layers before changing the interface

A useful review moves from the business proposition through to operations and measurement.

1. Positioning

Can the company answer, in specific language:

• who the offer is for;
• which problem it solves;
• why this approach is appropriate;
• what makes it meaningfully different;
• when it is not the right fit?

A website cannot communicate a decision the business has not made.

A positioning problem often appears as a homepage trying to give equal weight to several audiences, markets and services. Every stakeholder wants their topic above the fold, so the resulting message becomes broad enough to offend nobody and useful to nobody.

A redesign can create hierarchy once priorities exist. It cannot independently decide which market, offer or customer matters most.

If the leadership team disagrees on the primary audience or value proposition, resolve that disagreement before treating page layout as the main obstacle.

2. Offer clarity

Visitors may understand the category but still be unable to choose.

Look for:

• overlapping services with no clear boundaries;
• internal terminology that buyers do not use;
• descriptions focused on capabilities rather than buyer needs;
• no explanation of what is included;
• unclear engagement or delivery process;
• a generic “contact us” action with no indication of what follows.

Ask whether a suitable visitor can answer three questions after reading the core pages:

1. Is this relevant to my situation?
2. What would I be engaging the company to do?
3. What is the sensible next step?

If the existing information architecture obscures clear answers that already exist, redesign is justified. If the company cannot yet provide those answers, offer definition should come first.

3. Traffic quality and intent

A website cannot turn every visitor into a suitable prospect.

Review where traffic originates and what those visitors were promised. An article attracting early research traffic serves a different role from a service page reached through a high-intent search or a referral from a sales conversation.

Questions to investigate include:

• Which sources bring visitors to the important pages?
• Do those sources reach the intended market?
• Does the entry-page promise match the offer?
• Are visitors researching, comparing or ready to contact?
• Are campaigns attracting people with the right problem?
• Do regional and language versions match the audience?

A new design may help the right visitors navigate and act. It cannot make an unsuitable audience develop a need, authority or budget it does not have.

For companies entering several EU markets, this distinction matters: translating a website does not automatically create local demand or make the same proposition equally persuasive in every market.

4. Lead handling

Sometimes the website generates a legitimate opportunity and the process fails afterwards.

Trace what happens after a form submission or booking:

• Does the message reach the correct person?
• Is there a clear owner?
• Does the enquiry contain enough information?
• Is the next step defined?
• Is the source recorded?
• Can the team distinguish suitable from unsuitable leads?
• Are unavailable team members covered?

A redesign is relevant if the form is unreliable, asks the wrong questions or creates unnecessary friction. It is not a substitute for internal ownership and a consistent follow-up process.

Before adding more fields, decide which information the team genuinely uses. A longer form is not automatically better qualification; it may simply transfer an unresolved internal process to the visitor.

5. Measurement

Without measurement, the reason for a redesign is often built on anecdote.

Start by defining what improvement would mean. Depending on the website’s job, that could involve more suitable enquiries, fewer irrelevant submissions, better completion of a booking flow, easier publishing or fewer repetitive questions for the sales team.

Then identify what can currently be observed:

• visits to priority pages;
• use of key calls to action;
• successful and failed form submissions;
• enquiry source;
• device-specific problems;
• recurring questions in sales conversations;
• feedback from internal users.

Not every interaction needs to become a dashboard metric. The aim is to gather enough evidence to distinguish content, usability, technical, traffic and operational problems.

If basic measurement is missing, instrumenting the existing journey and observing it for an appropriate period may be more informative than immediately replacing it.

Check the operating model behind the website

A redesign request may conceal an internal workflow problem.

For example, a team may ask for a new content management system because the website is out of date. The real obstacle may be that nobody owns publishing, approvals require several unavailable people, or source material never arrives.

Technology can reduce friction. It cannot create editorial responsibility.

Before specifying a new publishing system, ask:

• Who will update the website?
• Which tasks must they complete?
• How often will they do so?
• Who approves changes?
• Which other teams provide the source material?
• What currently prevents publication?

The answers should shape the system. Otherwise, the new website may reproduce the old bottleneck with a different interface.

When redesign is the right intervention

A redesign has a clear purpose when the current website:

• no longer represents the actual offer;
• has a confusing information structure;
• makes important tasks difficult on mobile devices;
• cannot support required languages or content types;
• prevents the team from maintaining essential information;
• relies on unreliable forms or obsolete integrations;
• cannot support useful measurement;
• introduces technical or accessibility barriers.

Even then, “make it look more modern” is not a sufficient success definition. The project should connect design changes to specific user and operational needs.

When discovery should come first

Run a focused discovery phase before scoping a full redesign when:

• stakeholders disagree about the primary audience;
• the offer is still changing;
• nobody can describe the intended user journey;
• available data cannot distinguish traffic from usability problems;
• the team does not know what success means;
• several internal processes are being treated as website features.

Discovery can include content review, stakeholder conversations, journey mapping, measurement checks and an inventory of technical constraints.

Its outcome does not have to be a redesign. It may reveal that the first priority is refining the offer, correcting a campaign, repairing an enquiry workflow or assigning content ownership. It may also confirm that the website itself is the principal constraint.

Once the problem is understood, turn it into an actionable website brief and assess what the resulting scope will require.

If the diagnosis supports a custom website redesign, define the project around the identified constraint rather than appearance alone. Share the current situation through the contact section; I reply within 24 hours.

← Back to the blog