About the Author:
Quincy Samycia is Head of Brand and Growth at The Branded Agency, a branding, creative, website and growth agency working with ambitious companies across Canada, the United States and international markets. He helps organizations connect brand strategy with the creative, digital experiences and marketing systems responsible for measurable growth.
Website redesigns fail when teams change the interface before they settle on audience priorities, positioning, content, customer journeys and measures of success. A strong website redesign strategy defines those foundations first, then uses UX/UI design, development and testing to turn them into a clearer, more useful experience.
A dated interface, crowded navigation and slow publishing are symptoms. At The Branded Agency, our website strategy, UX/UI design and development work starts with a different question: what decision should this website help the right person make?
That question shifts the conversation from preference to purpose. It makes us define the audience, the value of the offer, the evidence needed to believe it and the path from interest to action. It also shows that many apparent design problems are unresolved business, brand or content problems.
A website redesign brief usually describes symptoms
“Make it modern” may signal outdated positioning. “Simplify it” may point to an undefined priority audience. “Improve conversion” may mean the offer lacks proof. “Make it easier to update” may mean no one owns the content.
Moving to Webflow or Shopify doesn’t answer any of those questions. Platform requirements should come out of the diagnosis, not stand in for it. When we skip that step, design inherits decisions the business has avoided, and the result is a polished website that is still hard to understand.
Brand, decision and operations: the three jobs of a website
We treat a website as three connected systems:
- Brand: makes the company recognizable and communicates a distinct point of view.
- Decision: helps visitors judge relevance, credibility and the next step.
- Operations: lets marketing publish, sales share useful destinations and internal teams keep content accurate.
When one system dominates, the trade-offs are predictable: memorable but vague storytelling, interchangeable conversion tactics, or efficient but uninspiring templates. Our goal is a website strategy that links expression, action and operation in one customer experience.
Six questions every website redesign should answer
Before we sketch a wireframe, we want clear answers to these questions:
- Who is the priority audience?
- What are they trying to accomplish?
- What makes this offer meaningfully different?
- What must they understand before they can act?
- What proof will reduce their doubt?
- Which action represents real business value?
Vague answers produce generic hero copy, navigation organized by department and competing calls to action. That is why we let positioning and messaging shape the sitemap: they decide what matters, in what order and to whom.
The website redesign process
When copywriters fill predetermined boxes and analytics arrives near launch, teams lose the chance to shape the experience. We start the website redesign process by mapping the visitor’s decision.
- Start from where the visitor is
Visitors may be researching a category, comparing options, validating a recommendation or getting ready to buy, and each stage needs a different path. Someone arriving from a specific campaign may need product evidence right away, while someone researching the category may need context first. The content sequence should account for those entry points. - Name the decision they are trying to make
Vague goals such as ‘learn more’ become a concrete question: does this product fit my workflow? Can I justify its price? The page is then built around the answer. - Sequence claim, meaning and proof
“Faster” invites “compared with what?” “Trusted” invites “by whom?” We explain what each benefit means and place supporting evidence next to the claim. - Remove friction and keep the character
Clarity depends on hierarchy. Cutting words or colours alone rarely achieves it. We keep the next step visible and preserve a distinctive voice and visual identity. Then we test whether someone can identify the offer, find relevant evidence and locate the next step without help from the project team. If they can’t, revisit sequence and emphasis before adding content or stripping back the identity. - Define success before choosing the solution
We define the intended outcome before selecting platforms, components and analytics. What success looks like depends on the business: an enterprise site may prioritize publishing workflows, an eCommerce site may need strong product discovery, and a lead generation site may need qualification and sales follow-up. We choose Webflow, Shopify or another platform against those requirements, not the other way around.
Proof should be part of the design system
Proof belongs where visitors encounter doubt, not on a disconnected testimonial page. We match the evidence to the claim:
- Performance: benchmarks, results or demonstrations.
- Expertise: relevant case studies, credentials or process.
- Trust: reviews, recognizable clients and transparent policies.
- Usability: an experience that is easy to complete.
- Brand: consistency between the promise and the experience.
We map proof during wireframing because evidence changes layouts and content requirements. Sometimes an unsupported claim has to change as well.
Build a content system, not a collection of pages
A refined homepage must eventually support dozens of less prominent pages, and reusable components alone won’t make that system scale.
A content system defines page purposes, field relationships, content limits, reusable proof patterns and rules for variation. Ownership is assigned so teams know who creates, approves and maintains content, and each element is marked as mandatory or optional, with a clear link between proof and products or services. A content model should reflect how the organization actually creates and updates information.
Whether you hire Webflow designers or Shopify designers, make sure templates are tested with real content and with the people who will publish it.
Flexibility should support informed choices without breaking hierarchy. The best handoff isn’t a library of blocks; it’s a set of choices the internal team can make with confidence.
What this looked like for Milton Coffee Co.
Milton Coffee Co. came to us with a specific eCommerce website redesign problem: the site did not communicate the value of its premium, customizable coffee machines clearly enough.
We began with discovery and creative exploration, kept the existing branding and photography, and refined the homepage and section copy. A customized Shopify template, dynamic product templates and a third-party “design your own” integration supported the buying journey.
Behind the screen, the templates also simplified future product uploads. The work connected what customers needed to understand with what the internal team needed to maintain, which took the project beyond a visual refresh.
Performance and accessibility are design requirements
We treat speed, stability, responsiveness and accessibility as design inputs from the start of the project.
Google’s Core Web Vitals guidance focuses on loading performance, interactivity and visual stability, because these are measurable parts of the experience real users receive. The Web Content Accessibility Guidelines are organized around content being perceivable, operable, understandable and robust.
In practice, that means budgeting for media and animation, protecting contrast, using meaningful headings and supporting keyboard interaction. These decisions affect both comprehension and usability. A website that promises simplicity but loads slowly or excludes visitors contradicts its own message.
Treat launch as the start of learning
Launch begins observation of the complete website; it doesn’t end the redesign. Prototype testing reduces risk, but real behaviour will still raise questions the project team didn’t anticipate. The Nielsen Norman Group’s iterative homepage redesign case study is a useful illustration of design improving through rounds of prototyping, testing and refinement rather than a single reveal.
We set baseline measures before launch, then review:
- Can priority visitors find the information they need?
- Which messages and proof encourage useful action?
- Where do qualified visitors hesitate or leave?
- Can the team publish without weakening the system?
The answers set improvement priorities. Qualified inquiries, completed purchases and publishing efficiency deserve a look alongside conversion rate, since not every click carries equal weight.
Settle the foundations before you approve a mockup
Before approving a mockup, confirm the audience, positioning, offer, proof, content model and success measures, and include performance, accessibility and measurement in the brief.
A successful website redesign makes the business easier to understand, the next decision easier to make and the system easier to improve. Those outcomes begin with choices made before the first screen.
Find more Community stories on our blog Courtside. Have a suggestion? Contact stories@dribbble.com.
