877-540-7778 Start a conversation
Websites / Decision guide

How do you know whether your website needs a redesign or a structural rebuild?

The central idea

What this changes

The word redesign is used for almost every website initiative. That creates mismatched expectations. A company may believe it is buying a new visual experience while the real work involves information architecture, content models, integrations, governance and conversion logic.

01 / The argument

Choose a redesign when the model still works

If audiences can find the right information, services are organized accurately and systems support the required actions, the site may need stronger expression rather than structural change. Visual hierarchy, usability, accessibility and performance can improve within the existing model.

02 / The argument

Choose a rebuild when exceptions have become the structure

Repeated landing-page workarounds, duplicated services, broken navigation, manual lead routing and content that cannot be governed indicate a deeper problem. The site no longer has a stable way to represent the business, so presentation work will quickly inherit the same constraints.

03 / The argument

Define the intervention before estimating the page count

Scope should follow the decisions being changed: how audiences understand the offer, how evidence supports evaluation, how systems exchange information and how teams operate the site. Counting templates before resolving those questions produces a precise estimate for the wrong project.

Decision framework

Use four tests to determine the scope

01

Comprehension

Can customers understand the complete offer?

02

Action

Do conversion paths reach the correct system and owner?

03

Governance

Can teams update information without creating contradiction?

04

Growth

Can the structure absorb the next service, market or acquisition?

Do not commission a redesign to avoid a rebuild

The less expensive intervention is the one that addresses the actual constraint. Cosmetic progress becomes costly when the organization returns to structural workarounds immediately after launch.

Found something worth acting on?
Let’s turn it into momentum.

Partner OS