A redesign will not fix a weak offer

Which problems belong outside the redesign?

A website redesign feels like a concrete solution.

• The project has a start date.
• There will be new screens.
• The team gets something visible to review.
• At the end, the business has a new site.

That makes redesign an easy answer to a vague problem.

• "We need more leads."
• "The site feels weak."
• "Competitors look better."
• "The homepage is not converting."

Some of those problems belong to the website.

Some do not.

A redesign improves how the business explains, presents, organizes, and delivers the digital experience.

• It does not rewrite the economics of a weak offer.
• It does not turn poor traffic into good traffic.
• It does not create real proof that does not exist.
• It does not fix a sales process that ignores good enquiries.
• It does not repair a product people do not want.

That distinction matters because a strong redesign starts with diagnosis.

Separate the problems

I usually think about the journey in four parts.

Acquisition.

Who arrives, from where, and with what intent?

If the business attracts the wrong audience, a cleaner homepage will still receive the wrong audience.

Offer.

What is being sold, to whom, for what outcome, and why should somebody choose it?

If the offer feels generic, the website has nothing strong to explain. Better copy helps, but the business still needs a real reason to choose the service or product.

Conversion path.

Does the website explain the offer, build trust, answer doubt, and make the next action clear?

This is where design has a direct role.

The hierarchy, page structure, proof placement, mobile experience, CTAs, forms, and interaction design all shape how easy the decision feels.

Follow up.

What happens after the visitor acts?

If the lead lands in an inbox nobody checks, the conversion problem sits after the page.

A redesign should focus on the parts it is responsible for.

That sounds obvious, but projects often blur all four together.

• Traffic is low, so the company asks for a redesign.
• Leads are weak, so the company asks for a new hero.
• Sales is slow, so the company asks for a shorter form.

The requested solution is not always the real problem.

Separate the website from the offer

Before approving a redesign, write the problem as an observable sentence.

Not: "We need a modern website."

Try: "Visitors reach the homepage but do not understand our main service."

Or: "Organic traffic reaches our blog but rarely moves into service pages."

Or: "People request quotes, but our team loses track of follow up."

Or: "Our product changed and the website still explains the old version."

Those statements point toward different work.

• The first might need messaging and homepage structure.
• The second might need content paths and internal links.
• The third might need CRM and lead flow.
• The fourth might need a wider website redesign.

This is also where a smaller project sometimes beats a full rebuild.

• A focused homepage rewrite.
• A new service page.
• A pricing page restructure.
• A form and follow up fix.
• A set of stronger case studies.
• A mobile conversion review.

If those changes solve the real bottleneck, rebuilding the whole site would add cost without adding enough value.

I still care about visual quality.

A strong visual system affects trust, clarity, and how seriously a business is perceived.

I do not want visual quality to become the explanation for every business problem.

The best redesign projects I work on have a clear reason to exist.

• The business knows what changed.
• The website has a specific job.
• The page structure supports that job.
• The launch has a way to measure whether the work helped.

Start there.

Then design.