The Questions We Ask Before a Redesign.
Most redesigns fail before a single pixel is drawn. The business knows it wants something new, fresher, faster, more modern, but nobody has agreed on what the new thing is meant to do. So the project becomes a matter of taste, opinions pile up, scope creeps, and the budget quietly doubles. The fix is simple and unglamorous. Ask the right questions first.
Who is this actually for?
Every site serves someone, but most try to serve everyone and end up speaking to no one. Before we touch a layout, we want to know who the priority visitor is. The cautious first-time buyer comparing three options? The returning customer who just wants to log in and reorder? The procurement lead who needs to forward a credible-looking page to a boss? Each of those people needs a different journey. When you name the one or two that matter most, a hundred design decisions answer themselves.
What decision do we want them to make?
A page is a tool for moving someone toward a decision. Book a call. Request a quote. Start a trial. Add to cart. If you cannot say the single action you want a visitor to take, the design has no job to do, and a design without a job becomes decoration. We push hard on this one because clarity here is what separates a site that performs from a site that merely looks good.
What happens after they convert?
This is the question that gets skipped, and it costs the most. A beautiful enquiry form that drops leads into an inbox nobody checks is worse than no form at all. We want to see the whole chain. Where does the lead go? Who responds, and how fast? What system records it? Often the real problem was never the website. It was the broken handover behind it, and a redesign that ignores that just makes the leak prettier.
What is breaking right now?
Before improving anything, we map what is actually failing. Maybe the mobile experience loses half the traffic. Maybe the team cannot update content without calling a developer. Maybe three tools each hold a different version of the truth. We sit with the people who use the current setup every day, because they know exactly where it hurts. Their frustrations are the brief.
How will we know it worked?
Success has to be something you can point at later. More qualified enquiries. Fewer support emails. Faster load times. A team that can publish without help. We agree on these measures up front so that, months on, the conversation is about evidence rather than opinion.
Discovery saves money
None of this is busywork. Every hour spent answering these questions removes days of expensive rework later. The most costly decisions in any project are the ones made on assumption, then unwound after launch when the data finally arrives. Discovery front-loads the thinking while it is still cheap to change your mind.
We treat this stage as the real start of the work. By the time we open a design tool, we know who we are serving, what we want them to do, what happens next, what is broken, and how we will measure the result. The design becomes the answer to a question we have already agreed on, and that is why it tends to land the first time.