“We need a new website” sounds like a clear problem.
Usually it isn’t.
It’s a proposed solution.
The important question is what happened in the business that made a new website feel necessary.
Because businesses rarely wake up one morning and suddenly need a different website. Something usually changes first — and the website becomes the place where that change is most visible.
Something usually changed first
Maybe the company has grown.
Maybe the positioning changed.
Maybe the business is pursuing larger clients and the current website no longer creates the level of confidence those conversations require.
Maybe marketing can’t easily create new pages or publish the content it needs.
Maybe the website generates traffic but not meaningful inquiries.
Maybe a rebrand exposed how poorly the current site represents the company.
Maybe new services, markets or audiences have made the existing structure difficult to navigate.
Or maybe leadership simply realizes the business has become more sophisticated than its digital presence.
Those are different problems.
They shouldn’t automatically produce the same website.
A company struggling with positioning has a different challenge from one struggling with content management. A business moving into a more competitive market needs something different from one whose primary issue is converting existing traffic.
That distinction matters because the reason behind the redesign should determine what gets redesigned.
Ask what isn’t working
Before discussing visual direction, establish the actual constraint.
Ask:
- What does the existing website prevent the business from doing?
- What do prospects misunderstand?
- What does the sales team repeatedly have to explain?
- What content is difficult to create or manage?
- Where do users struggle to find what they need?
- What opportunities are being missed?
- Has the audience changed?
- Has the business moved into a different market or price point?
- What would success look like twelve months after launch?
Those answers are more useful than a folder of websites someone likes.
Visual references can help establish taste and direction later. They cannot tell you what the website needs to accomplish.
That requires understanding the business first.
Separate symptoms from causes
This is where redesign projects can easily go in the wrong direction.
“The homepage feels dated” is a symptom.
The underlying problem might be weak positioning, unclear messaging or a visual identity that no longer represents the company.
“People can’t find anything” could be a navigation problem. But it could also be an unclear service architecture that makes the navigation difficult to organize in the first place.
“We need a more premium design” might really mean the company has moved upstream and needs its digital presence to establish a different level of credibility before a sales conversation ever happens.
“Our website is hard to update” might sound like a CMS problem. But the deeper issue could be that the content model was never designed around how the marketing team actually works.
Fixing the symptom can make a website look different without making it substantially better.
A good discovery process keeps asking until the underlying problem becomes clear.
That’s why our approach begins with Understand, not Design.
Understand what has changed around the website
A website doesn’t exist independently from the business.
It sits between the company and the people the company wants to reach.
When either side changes, the website may need to change with it.
A business that has grown from a small local provider into a regional organization may need stronger proof, clearer capabilities and a different level of polish.
A company introducing several new services may need to rethink its information architecture before it thinks about colors or typography.
A business that previously relied almost entirely on referrals may need a website that does more of the early work of establishing credibility and explaining its value.
Sometimes the website itself isn’t broken.
The relationship between the website and the business is.
That is an important distinction.
Define what should be different afterward
Once the problem is understood, define what success actually means.
Not:
We want a better website.
Something closer to:
A prospective client should understand our three core capabilities within a few minutes and see evidence that we can handle work at their scale.
Or:
Our marketing team should be able to launch a new service page without needing a developer to rebuild the layout.
Or:
The website should make our positioning clear enough that qualified prospects arrive at the first conversation already understanding what makes us different.
Those are useful objectives.
Now strategy has direction.
Design has something to solve.
Engineering has requirements.
And after launch, the business has something more meaningful to evaluate than whether everyone likes the new homepage.
Don’t redesign what doesn’t need redesigning
Understanding the problem also tells you what not to change.
Not every website needs to be rebuilt from the ground up.
Sometimes the technology is perfectly capable, but the messaging needs work.
Sometimes the brand is strong, but the website architecture has become confusing after years of adding pages.
Sometimes the website needs substantial change, but a particular integration, content system or technical foundation is worth preserving.
Starting with the assumption that everything needs replacing can create unnecessary cost and complexity.
The better question is:
What needs to change for the website to support where the business is going?
The answer may lead to a complete redesign.
It may also lead to a much more focused intervention.
Either outcome is better than deciding on the solution before understanding the problem.
Then make the website
Once the problem is understood, the website becomes easier to reason about.
Content has a purpose.
Architecture has a rationale.
Design has criteria.
Technology has requirements.
Features can be evaluated against actual needs rather than added because they seem useful.
And stakeholders can evaluate decisions against an agreed objective instead of personal preference.
That doesn’t remove subjectivity from the creative process.
It gives that creativity a reason to exist.
Before redesigning the website, understand why the business needs it to change.
The answer should shape everything that follows
