Website Redesign Discovery Questions That Clarify the Work

Website redesign discovery should explain what the business needs its website to do. Use these questions to guide a conversation, not as a script you must read from start to finish.

Begin with the reason for the change. Then follow the visitor journey and identify the decisions needed to build it.

Why are we redesigning now?

What has changed in the business since the current site was created?
What do customers misunderstand or struggle to find?
Which existing pages or features are useful and should stay?
What would make the new website more useful to your team?

Listen for: a specific problem you can address. If the answer is “it looks dated,” ask which parts feel wrong and what the business wants to communicate instead.

Who needs the website, and what are they trying to do?

Who are your most important visitor groups?
What do they need to know before contacting or buying from you?
What questions come up repeatedly in sales or support conversations?
What should their next step be?

Turn the answer into: page purposes and useful content, not a homepage that tries to answer every question at once.

What happens after someone clicks?

Walk me through a typical enquiry, booking or purchase.
What information does your team need at that point?
Are services or locations handled differently?
What should customers receive next?
Does anyone need an account or a private area on the website?

Turn the answer into: a complete flow you can review. “Add a booking button” is not enough if the real requirement is choosing the correct service and location.

What information and tools do we already have?

Where are service details, product lists, images and customer materials stored?
Which information is accurate enough to reuse?
Which business tools should the website work with?
Do you need a one-time import or an ongoing connection?
Who can authorize access?

Listen for: the source of current information. Avoid making a copied spreadsheet and an existing business tool compete as two different versions of the truth.

What should the brand feel like?

What must remain recognizable?
Which examples feel right, and why?
What would feel unlike your business?
Do you have real photos, customer feedback or work examples we can use?

Turn the answer into: a few clear design instructions. In Revamp, you can review the first redesign and change the visual direction before extending it across the other pages.

What needs to be preserved for existing visitors?

Which pages are important entry points today?
Are there links in campaigns, directories or customer emails that must keep working?
Which content is still useful?
Which page addresses are expected to change?

Record the answers in the content inventory. Use observed traffic and link information where available instead of assuming that an old-looking page has no value.

Who makes decisions and approves publication?

Who checks the accuracy of the content?
Who consolidates feedback?
Who approves the design and working features?
Is there a deadline that changes the launch priorities?
Who gives the final instruction to publish?

Turn the answer into: clear review points. A preview approval and permission to publish should not be treated as the same decision unless that is explicitly agreed.

Finish with a decision summary

Send a short recap:

The website will help [audience] do [main task]. We will retain [important content and brand elements], improve [specific problems] and build [working features]. [Person] will supply the missing information and [person] will approve the preview. The open decisions are [list].

Use the requirements checklist to organize the agreed work. If you need written answers before the meeting, send the client intake form.

Put the discussion into a working website

Bring the client’s URL, brand materials and discovery summary into Revamp. Ask for a design that reflects the direction you agreed, then refine the presentation by chatting or editing visually.

Use the first preview to make the conversation concrete. A client can point to a service section, explain how booking should work or ask for a different visual direction. Continue building those decisions into the same project through publication and later updates. Explore Revamp for agencies for the client workflow.

Frequently asked questions

How many discovery questions should I ask?

Enough to clarify the important decisions. Skip questions already answered and spend more time on uncertain workflows, content ownership or approvals.

Can I show a redesign during discovery?

Yes. Use it to make the discussion concrete, then relate feedback to the agreed visitor needs. Do not treat enthusiasm for the appearance as approval of every page and feature.

What if the client does not know what they need?

Walk through a real customer interaction. That often reveals useful requirements more clearly than asking for a list of features.