UX Redesign: Method, Goals and Key Steps

Many projects called a "redesign" amount to switching tools or refreshing the visual identity. A UX redesign asks a different question: do the people who use your website or application succeed at what they came to do? If the answer is no, a new technical platform or a new colour palette will not fix anything.

This guide treats UX redesign as a project approach. It gives the definition and scope, compares it with technical and UI redesigns, then describes a six-step method. For the fundamentals of the discipline, start with our UX design guide.

UX redesign: definition and scope

The definition of a UX redesign fits in one sentence: rebuilding the experience of using a digital product from the needs, tasks and constraints observed among its users. UX design, or user experience design, supplies the methods. The redesign applies them to a product already in service, with its history, its habits and its data.

The Nielsen Norman Group describes user experience as every interaction a person has with a company, its services and its products. This reference definition is a reminder that the experience goes beyond the screen: it includes content, delays, error messages and what happens after a form is sent.

What a UX design redesign includes

The scope covers information architecture, customer journeys, screen ergonomics, the wording of content and interface states: loading, error, success, empty. It also includes accessibility, framed by the WCAG 2.2 criteria and, for organisations operating in France, by the RGAA.

What it does not include

A UX redesign does not choose the CMS, the framework or the hosting. It may recommend a technical change when the existing platform blocks a journey, but that decision belongs to the technical redesign covered in the next section.

The scope is fixed in a UX brief. This document lists the journeys concerned, the target users, the non-negotiable constraints and the success indicators. Our website design guide details the deliverables expected at each stage.

UX redesign vs technical redesign: what changes

A technical redesign replaces or modernises the platform: CMS migration, new framework, code rewrite, change of hosting. Its trigger is internal: technical debt, security, performance, maintenance cost. A UX redesign starts from usage and can be carried out on the existing platform.

The two are often confused because they arrive at the same time. A migration is an opportunity to revisit the journeys. The risk is letting the technology dictate the experience: the old screens are reproduced in a new tool, and users meet the same obstacles with a different look.

Three questions to decide

First question: do users fail at specific tasks? If so, the UX redesign comes first. Second question: does the technical team spend its time working around the tool? Then the technical redesign is required. Third question: are both answers yes? In that case the UX redesign precedes the technical one, because it defines what the new platform must allow.

The table below summarises the differences with the third form of redesign, the UI redesign, covered later.

The goals of a UX redesign: business and usage

The goals of a UX redesign are written before the first mockup. They come in two families that must answer each other: what the company expects, and what the user must succeed at. A goal without an observable indicator is not a goal, it is a wish.

Business goals

On the company side, a redesign usually targets conversion on a specific journey, fewer support requests caused by the interface, fewer abandoned forms or checkouts, and the ability to sell an offer that has evolved. Each goal is tied to an identifiable customer journey and a measured starting value.

Usage goals

On the user side, the aim is completing a task without outside help, a reasonable completion time, a correct understanding of the offer and the ability to recover after an error. These goals are checked in user testing, not in a dashboard.

Talking about UX ROI without inventing a number

UX ROI exists, but it cannot be derived from a universal ratio. It is calculated project by project, from your own data: the cost of the redesign on one side, the measured gap on the chosen indicators on the other, across two comparable periods. Be wary of conversion percentages promised before any measurement.

Record the baseline values in the UX brief. Without a documented starting point, the redesign will never be able to prove what it changed.

A UX redesign method in six steps

The UX redesign method described here applies to a brochure website, an online shop or a business application. The steps keep the same order; their duration and depth vary with the scope. The shared principle: produce a screen only after observing use, and go live only after testing.

Each step produces a verifiable deliverable, which lets the team discuss decisions on facts.

UX redesign of a business application: what is specific

The UX redesign of a business application does not follow exactly the logic of an online shop. The users are known, few and captive: they will use the tool whatever happens. The cost of poor ergonomics does not show in a bounce rate but in lost hours, input errors and spreadsheet workarounds.

Start from real work

The UX audit begins by observing people in situation, at their workstation. You note the double entries, the information searched across several screens, the paper printouts that compensate for the tool.

Map the tasks before the screens

A business application concentrates dozens of functions. The redesign ranks them by frequency and criticality. Daily tasks get the shortest path; rare tasks can stay deeper. This map becomes the backbone of the UX brief and avoids redrawing screens nobody uses.

Manage the transition

Changing the ergonomics of a tool used every day disrupts habits. Plan tests with the most experienced users, a period of coexistence where possible, and a short briefing focused on what changes. Objections at the start of rollout are not all design flaws: separate a lost habit from a real blocker, with observations.

The UX redesign of a business application is often combined with a technical redesign, because older tools sit on platforms that are hard to evolve. The order stays the same: target journeys first, technology second.

UX vs UI redesign: where the line sits

A UX/UI redesign mixes two disciplines that overlap in practice but answer distinct questions. UX decides what the user must be able to do, in what order and with what information. UI decides the form those decisions take on screen: visual hierarchy, components, colours, typography, states.

The line in practice

One example: on a quote form, UX determines which fields are really needed, their order and the message that follows submission. UI makes each field readable, distinguishes the primary button and shows where to correct an error. If the form asks for useless information, a polished UI will not solve the problem. If the fields are unreadable on mobile, a well-designed journey will still fail.

When a UI redesign is enough

A UI-only redesign is justified when the journeys are validated by tests but the interface lacks consistency, accessibility or alignment with the brand. It then relies on a design system, reusable components and contrast rules that meet WCAG. Our UX vs UI design article details this complementarity.

In a full UX redesign, UI comes after the wireframes are validated. Doing the reverse means decorating journeys that have not been verified.

When to bring in a consultant or an agency

An in-house team can run a UX redesign if it has the time, access to users and someone able to run tests without bias. Three situations justify outside support.

The UX consultant

The consultant works on a bounded assignment: UX audit, test protocol, session facilitation, reporting. This suits a team that can produce the screens but lacks perspective or method. Our article on the UX consultant details the deliverables and the price ranges to check in a quote.

The agency

The agency takes on the whole chain, from audit to launch, with UX/UI designers and developers working together. This suits a UX redesign combined with a technical or UI redesign, when nobody in-house can coordinate all three. Ask for a test protocol and a measurement plan before talking about results.

Building the skill in-house

For a company planning regular iterations, having a designer on the team avoids starting from scratch on every project. Our guide to the UX designer role describes the profile to look for and how to assess a portfolio.

Whatever the choice, the selection criterion stays the same: the provider explains how they will observe users, how they will measure the gaps and what they will deliver at each step.