How to Test Your Customer Journey Before a Website Redesign

Before rebuilding your website, walk the path a customer takes. Find the broken step, fix one thing, and check what actually changed.

By Patrick Grabbs · November 18, 2026

How to Test Your Customer Journey Before a Website Redesign

To test your customer journey before a website redesign, choose one customer task and follow it from the first page to the real outcome. Find the first broken or confusing step, change that step, and run the same task again before changing anything else.

A website can look finished while the customer is still wondering what to do. The button works. The page loads. But the request lands somewhere nobody checks, or the confirmation leaves the customer unsure whether anything happened.

That is a different problem from needing a new website. Find out which problem you have before rebuilding the whole thing.

How to test your customer journey before a website redesign

Start with a sentence a customer would actually say: "I want to ask whether you can help with this job."

Not "I want to engage with the brand." Not "I want to explore the solution." A person needs something done and wants to know whether you are the right person to do it.

Pick the path that serves that task. It might be an enquiry page for a service business or a request for help from an expert. Keep this first test narrow. You are not trying to inspect every page, every offer and every possible visitor at once.

Write down the starting point and the finish. For example: a person opens the service page on their phone, understands the service, sends an enquiry, sees a confirmation, and the right person receives the details.

That last part matters. A working button is not the finish.

Walk through as someone who does not know your business

Use your phone. Start from the actual link a prospective customer would open, not a saved page halfway through the process. If the enquiry usually begins from an email or profile link, start there.

Before touching anything, ask:

A useful second pair of eyes is someone unfamiliar with the page. Give them the task, then let them try. Do not narrate where the button is. The moment you need to explain the page is worth noting.

Keep the notes factual. "They scrolled past the enquiry button twice" is useful. "The design feels dated" may be a preference, but it does not identify the failed task.

Check the handoff, not just the screen

For a test on your own business, use clearly marked test details and warn whoever receives enquiries. Do not place a paid order, make a real appointment or trigger customer messages just to see what happens. Use an existing safe test route where those actions are involved.

For a normal enquiry test, check both sides: what the visitor sees and what your business receives. Does the message arrive? Does it include the question the person typed? Can the person responsible tell that it needs their attention?

Then look at the visitor's confirmation. The W3C's guidance on form notifications, checked November 18, 2026, recommends clear feedback after submission, including understandable errors and confirmation of success. The practical question is simple: can the person tell whether the request went through?

A confirmation should not promise a response time your business cannot keep. Tell the truth about what happens next. If a request fails, the person needs a usable way forward, not a silent button.

Fix one observed problem first

Here is a hypothetical example, not a client result.

A service owner thinks the site needs a redesign because enquiries seem hard to manage. During a walk-through, the enquiry reaches the correct inbox with all the details. But the confirmation only says "Done," and nobody has a clear responsibility for answering.

There are two observations here. The visitor gets little reassurance, and the business has an ownership gap. Neither observation proves the entire website needs replacing.

The owner could first assign responsibility for incoming requests and confirm that the receiving person can act on them. Then they could improve the confirmation as a separate change. Each repair gets its own check.

Why separate them? If you change the page, the offer, the form and the person answering all at once, you may produce a better experience. But you will have a harder time explaining which change helped or finding the cause if something breaks.

This is a diagnostic habit, not a promise that one small repair will produce more customers.

Keep a short before-and-after record

You do not need a new dashboard to record a broken handoff. A plain note can hold the essentials:

Separate a completed test from a business result. Receiving a marked test enquiry shows that particular request reached its destination. It does not show that more visitors will enquire or that an enquiry will become a customer.

If you later compare real enquiries, keep the definition consistent. A question, a suitable opportunity and a completed sale are different things. You can track them separately without calling them all conversions.

When a redesign makes sense

A walk-through is not an argument against redesigning. It helps make the redesign brief specific.

You may find that your service has changed but the page still describes the old offer. You may find that the main task is buried under unrelated choices. Or you may find that ordinary edits cannot fix the experience because the site itself is too difficult to maintain.

Now you can describe the work in customer terms: "People need to understand this service, send these details and know what happens next."

That is a better starting point than asking for something modern. It gives the person building the site a task to support and gives you a way to check the finished work.

Questions owners ask

Do I need analytics before I start?

Not to check whether a specific task works. Analytics can help you decide where to investigate, but walking through a request can reveal an obvious failure without a traffic report. Neither method, by itself, explains every reason someone leaves.

Does one successful test prove the whole website works?

No. It confirms one path under the conditions tested. Other devices, pages or customer tasks may still have problems. Record what you checked instead of declaring everything fixed.

What should I do first today?

Pick the enquiry path that matters most to your business. Follow it, check who receives the request, and write down the first thing that needs attention. Get that step working before ordering a new collection of pages.

If you want a partner beside you on that decision, describe the broken handoff in the enquiry form below. Start with what you sell and what you want the customer to be able to do.

About Patrick Grabbs

Patrick Grabbs, known as "the Internet's Middle Brother," is a Dallas entrepreneur and the founder of DRiPGATE. He partners with founders, experts, creators and local business owners who have the skill or the audience but not the business behind it, and builds the offer, the sales and the customers with them.

Where does the next step break in your business?

Tell Patrick what you sell and where people get stuck. Use the enquiry form to describe the handoff you want help with.

By submitting, you agree Patrick can contact you about your request.
Apply to partner with Patrick ↗