Phases of a Website Redesign Explained

The phases of a website redesign determine whether a project delivers predictable results or spirals into revisions and missed deadlines.

Clients who understand the phases before the project starts ask better questions and move faster through approvals.

Understanding what happens in each phase helps you recognize when something is out of sequence.

A designer who starts work before discovery is complete, or a developer building before designs are approved, is creating expensive rework that compounds quickly.

Key Takeaways

• Six defined phases: Discovery, UX, visual design, development, launch, and post-launch each produce specific deliverables that gate the next phase.
• Sequence protects the budget: Running phases in parallel creates rework that costs significantly more than the time saved by starting early.
• Client input peaks early: Discovery and design require the most client involvement; development and launch require prompt responses more than active participation.
• Content spans multiple phases: Content strategy starts in discovery, copy is written during design, and content loads during development.
• Post-launch is a phase: The 90 days after launch are a defined project phase with monitoring, iteration, and performance review responsibilities.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

How the Phases Form a Complete Process

A website redesign is not a series of independent tasks. It is a chain of phases where how phases connect as a process determines the quality of every decision downstream.

Each phase produces outputs that the next phase requires as inputs. Skip a phase, rush through it, or bypass its sign-off requirement, and the errors from that phase carry forward into every phase that follows.

The Phase Dependency Chain

Discovery produces a brief. Design requires that brief. Design produces approved mockups. Development requires those mockups. Breaking the chain forces the team to work from assumptions rather than decisions.

• Brief before design: Without documented goals and audience profiles, every design decision is based on preference rather than strategy.
• Approved wireframes before visual design: Structural problems caught at the wireframe stage cost a fraction of what they cost in high-fidelity design.
• Signed-off designs before build: Development that starts before design approval creates rework when revisions arrive during the build phase.
• QA before client preview: Clients reviewing a site with unfixed bugs waste review time on issues the agency should have caught internally.

Why Phase Gates Matter

A phase gate is a formal sign-off where the client approves a phase's output before work continues. Without gates, directional errors from Phase 1 compound through Phase 6 and become expensive to unwind.

The Client's Changing Role Across Phases

In discovery, the client is highly involved: providing information, attending interviews, making key decisions. In design, the role shifts to active feedback. In development, availability for questions and content delivery matters most.

Phase 1: Discovery

Discovery is the research phase. It defines the goals, audience, competitive context, technical requirements, and success metrics that guide every decision in every subsequent phase.

Clients who underinvest in discovery typically face the most expensive redesigns. Every decision made in the absence of discovery data is a guess that eventually needs to be corrected.

What Discovery Includes

Discovery is not a kickoff call. It is a structured research process with defined outputs.

• Analytics audit: Understanding what the current site does well, and where it loses users, provides the data foundation for redesign decisions.
• Stakeholder interviews: Aligning internal stakeholders on goals, priorities, and success metrics early prevents conflicting directives later.
• Competitor analyzis: Mapping competitor positioning, content structure, and UX patterns informs differentiation decisions during design.
• Audience research: Understanding how target users currently find, evaluate, and engage with the site defines conversion architecture requirements.
• Goal documentation: Agreed, prioritized business goals and measurable success metrics are the outputs that close the discovery phase formally.

Reviewing the steps within the discovery phase helps teams allocate the right time and stakeholder access to this critical stage.

The Discovery Phase Deliverable

The output of discovery is a documented, approved brief: goals, audience profiles, competitive context, scope, technical requirements, and success metrics. This document is signed off before Phase 2 begins.

What Makes Discovery Succeed or Fail

Discovery succeeds when clients are available, prepared, and willing to prioritize decisions over discussion. It fails when key stakeholders are unavailable or sign-off is deferred indefinitely.

Explore the discovery phase in depth to understand what to bring to discovery workshops and how to prepare your team for fast, effective decision-making.

Phase 2: UX and Information Architecture

UX and IA phase structures the site before any visual design begins. The sitemap, wireframes, and conversion flows are all established here, at the cheapest possible point in the project.

Research consistently shows that fixing a design error in development costs 10x more than fixing it at the wireframe stage. Phase 2 exists to find and resolve structural problems before they become expensive ones.

Sitemap and Navigation Architecture

The sitemap defines every page, its position in the hierarchy, and how users navigate between them. It must be approved before wireframing begins.

• Page inventory: Every page on the new site is named, categorized, and mapped to a user need before any wireframe is drawn.
• Navigation structure: Primary navigation, footer navigation, and internal link architecture are agreed at this phase and validated against user journey requirements.
• Content consolidation decisions: Pages that overlap in purpose are identified and merged, reducing duplicate content risk and improving crawl efficiency.

Wireframes for Key Templates

Wireframes are low-fidelity layouts that define content blocks, primary actions, and layout structure. They are reviewed for function, not aesthetics.

Conversion Flow Validation

Key user journeys are mapped and stress-tested at this phase.

How a visitor moves from landing on the homepage to completing the primary conversion action should be traceable, friction-free, and validated by the client before design begins.

Phase 3: Visual Design

The visual design phase translates the approved UX and IA outputs into a visual language. It produces the design system and high-fidelity mockups that developers will build from.

How long each phase takes depends significantly on how efficiently client feedback is consolidated during the design review phase. Fragmented or delayed feedback extends design timelines more than any other single factor.

Design System Development

Before individual pages are designed, the design system is created: color palette, typography scale, spacing system, and component library. This ensures consistency across all templates.

• Color and type decisions: These are made at the system level, not page by page, so they apply consistently across all templates.
• Component library: Buttons, cards, forms, and navigation elements are designed once and reused across every page template.
• Responsive rules: How the design system adapts from desktop to tablet to mobile is documented at this phase, not improvised during development.

High-Fidelity Mockups by Template Type

Key page templates are designed at full fidelity in both desktop and mobile. These mockups are the direct reference for development. Ambiguity in the mockup becomes inconsistency in the build.

Design Review Protocol

Reviews should be consolidated: one round of feedback per design delivery, with all stakeholder input combined before submission. Multiple separate feedback streams cause conflicting direction and extend the phase.

Phase 4: Development and Quality Assurance

The deliverables from each phase of development include the built site, configured CMS, connected integrations, and a QA-passed staging environment that is ready for client review.

Development builds to the approved design. Nothing in development is an opportunity to revisit design decisions. The brief for this phase is the signed-off mockup, and the work is to build it precisely.

Building to Approved Design

Every page template is built to match the approved design, with the CMS configured for the client's content workflow. Building begins only after all design sign-offs are in place.

• CMS setup: The content management system is configured so the client can update copy, images, and content without developer involvement after launch.
• Template fidelity: Developers work to an approved spec. Design deviations should be flagged during QA, not discovered after client preview.
• Accessibility implementation: WCAG standards, alt text, keyboard navigation, and form labeling are implemented during build, not retrofitted after.

Integration Setup and Testing

All third-party tools (CRM, email, analytics, forms, tracking pixels) are connected, configured, and tested before the client sees the staging site. Integration failures caught at this stage save significant post-launch disruption.

QA Before Client Preview

Cross-device testing, cross-browser testing, form verification, performance testing, and redirect validation are completed before the client reviews staging. Client preview is not a substitute for agency-side QA.

Phase 5 and 6: Launch and Post-Launch

The final two phases are sequential and connected. Project planning from phases ensures that launch day tasks are documented in advance and that post-launch monitoring responsibilities are assigned before the site goes live.

No phase in the redesign process is more time-sensitive than launch. Every task on launch day should be on a checklist, and every contingency should be identified before the DNS is cut.

Launch Day Protocol

DNS cutover, SSL verification, redirect testing, analytics verification, and form testing are launch day tasks with a defined checklist.

• Redirect verification: A sample of redirects should be manually tested immediately after DNS propagation is confirmed, not the following day.
• Analytics confirmation: GA4 should be confirmed live within one hour of launch, before any traffic data is lost.
• Form testing: Every contact and conversion form should be submitted and verified against the receiving system on launch day.
• Launch timing: Launch should not happen on a Friday or before a public holiday. Support availability during the 24 hours after launch is a requirement.

30-Day Post-Launch Monitoring

Active monitoring of rankings, crawl errors, analytics, and form submissions for 30 days after launch catches issues before they compound. This is a defined project responsibility, not optional goodwill.

90-Day Performance Review Against Goals

The redesign's success is measured at 90 days, comparing conversion rates, traffic, and rankings against the pre-launch baselines documented in discovery. This closes the project formally and confirms whether the investment delivered the expected return.

Conclusion

The six phases of a website redesign are a connected system. Each phase depends on the previous one being completed and approved, and each produces the outputs the next phase requires.

Attempting to skip or overlap phases creates rework that costs more than the time saved.

Map your current project against these six phases. Identify any phase that lacks a defined output or a sign-off requirement. Those gaps are exactly where the project will stall.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Takes You Through Every Phase, With Clarity at Each Step

A redesign is only as good as the process behind it.

LOW/CODE Agency is a strategic product team, not a dev shop, and every project we run follows a six-phase process with defined deliverables, client responsibilities, and formal sign-off at each gate.

We don't start development until design is approved. We don't launch until QA is complete. And we don't close a project until the 90-day performance review confirms the redesign delivered what the business needed.

• Discovery and brief: Structured research, stakeholder interviews, and documented goals before any design work begins.
• UX and information architecture: Sitemap, wireframes, and conversion flow validation before any visual design is produced.
• Visual design and design system: Full-fidelity mockups and a documented component library built to approved brief specifications.
• Development to spec: Every page template built to match approved designs, with CMS configured for client self-management.
• Integration setup and QA: All third-party tools connected, tested, and verified before client preview of the staging environment.
• Launch with a defined checklist: DNS, redirects, analytics, and forms verified on launch day with full support availability.
• Post-launch monitoring and review: 30-day monitoring and 90-day performance review against the baselines set in discovery.

We've delivered phased redesign by LCA for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku, across more than 350 products built. Start with a scoping call