Introduction

A product redesign differs from a new product design in one fundamental way: it starts with an existing product that has real users, real data, and real constraints that a new product build does not carry. These existing conditions are the primary inputs to the redesign process — the behavioral data that documents where the current product is failing users, the design system audit that identifies what is worth preserving versus what needs to be rebuilt, and the technical constraints that determine which redesign approaches are feasible within the existing engineering architecture. Skipping the audit phase to reach visible design output faster produces a redesign that replaces the current product’s problems with a different set of problems rather than with validated improvements. Figma is the standard environment for the design phases. WCAG 2.1 accessibility audit and remediation is a standard component of any professional product redesign. The Nielsen Norman Group’s research on redesign success rates documents the audit-first approach as the primary differentiator between redesigns that improve product metrics and those that produce visual updates without measurable performance change.

How the Product Redesign Process Works

Definition. The product redesign process is a structured sequence of audit, definition, design, and validation activities that transforms a documented set of user experience failures and design debt issues into a redesigned product — grounded in behavioral evidence about where the current design is failing, validated through usability testing before engineering investment, and measured against defined baselines after launch.

What each stage of the product redesign process produces

• UX audit and baseline measurement — a prioritized list of specific interface failures ranked by user impact, accessibility compliance gaps, behavioral analytics baselines for the metrics the redesign will be measured against, and a design system audit documenting what to preserve and what to rebuild
• Redesign brief — a scoped definition of which specific problems the redesign will address, which flows will be restructured, which visual elements will be updated, and the success metrics that will indicate whether the redesign produced its intended outcomes
• UX architecture and validation — revised information architecture, restructured user flows, and low-fidelity wireframes for the highest-friction areas, validated through prototype testing with current users before visual design investment begins
• Visual design and design system rebuild — high-fidelity screens built on a rebuilt or significantly updated design system, covering all states and edge cases, validated through a final usability test before engineering handoff
• Staged rollout and post-launch measurement — phased deployment to user cohorts with behavioral monitoring, A/B comparison against the existing design where feasible, and a thirty and ninety-day measurement review against the defined baselines

What Is the Typical Product Redesign Process in 5 Steps

1. Conduct a UX audit and establish behavioral baselines before writing a single wireframe. The audit identifies which specific interface decisions are creating measurable friction — where users abandon flows, which interactions generate support tickets, which screens have the highest exit rates — and establishes the metric baselines that the redesign will be measured against at launch. The audit also produces a design system assessment that identifies which components, patterns, and styles are worth preserving and which need to be rebuilt. A redesign that begins without this audit replaces the current product’s documented problems with undocumented new ones. The audit investment — typically one to three weeks — produces the most valuable input the redesign will have: specific, evidence-based targets rather than visual preference.
2. Define the redesign brief from audit findings rather than from stakeholder aesthetic preferences. The brief specifies which flows will be restructured, which visual elements will be updated, which design system components will be rebuilt from scratch versus updated, the user research that needs to be conducted to fill gaps in the audit’s behavioral data, and the success metrics — activation rate, retention, support ticket volume, accessibility compliance — that will indicate whether the redesign produced its intended outcomes. The brief should explicitly list what is out of scope: flows or features not documented as causing friction should not be redesigned unless there is a positive reason — a new user segment, a changed business model — that justifies the additional scope.
3. Redesign the UX architecture before applying visual design. The audit’s highest-priority friction points identify where the information architecture, navigation structure, or flow logic needs to change. Rebuild these structural elements as low-fidelity wireframes and validate them through five-user prototype testing with representative current users before investing in visual design. This validation is more important for a redesign than for a new product design, because redesign users carry mental models from the current product that the new design must either match or deliberately override. A structural change that testers cannot navigate because it conflicts with their existing mental model of the product has not been designed for the actual user — it has been designed for a hypothetical user who does not carry the current product’s interaction history. Since 2019, the redesigns with the highest post-launch adoption among existing users are those where the restructured flows were tested with current users before visual design locked the direction.
4. Rebuild the design system and produce high-fidelity screens from the audit-informed design system assessment. Components identified as worth preserving in the audit are updated rather than replaced, preserving the implementation work already done and reducing engineering scope. Components identified as needing rebuilding are designed from scratch with documented tokens, variants, and interaction states. Produce high-fidelity screens for every flow in the redesign scope, covering every state — default, loading, empty, error, success — before engineering handoff. Run a final WCAG 2.1 accessibility audit against the high-fidelity designs before handoff to catch contrast failures, keyboard navigation gaps, and screen reader compatibility issues that are significantly cheaper to fix in Figma than in deployed code.
5. Roll out the redesign in stages rather than as a single full-deployment event, and measure against baselines at thirty and ninety days. A staged rollout deploys the redesign to a defined cohort — typically ten to twenty percent of active users — while maintaining the existing design for the remainder, enabling behavioral comparison between the two versions before full deployment. Monitor the rollout cohort’s behavioral metrics daily for the first two weeks, watching for unexpected abandonment increases or support ticket spikes that indicate the redesign has introduced new friction rather than eliminating existing friction. Expand to full deployment only after the staged cohort’s metrics confirm the redesign is performing at or above the baseline. Measure against all defined baselines at thirty and ninety days after full deployment and document the results as the post-launch evidence that the redesign initiative produced its intended outcomes.

Pro tip: Before presenting the redesign to existing users, map every significant navigation change to the behavior change it will require from users who have learned the current product. For each significant change, define whether the new pattern is sufficiently self-explanatory to be navigated without guidance, or whether an in-product tooltip, onboarding overlay, or change announcement is required. The users most likely to churn after a redesign are the power users who have built efficient workflows around the current product’s patterns and encounter the new patterns as disruption rather than improvement.

Conclusion

The typical product redesign process moves through UX audit and baseline establishment, brief definition, UX architecture validation, visual design and design system rebuild, and staged rollout with post-launch measurement — each stage grounded in the existing product’s behavioral evidence rather than in aesthetic preference, and each gate requiring validated evidence before the next stage’s investment is committed. The redesigns that produce measurable improvement in product metrics are those that begin with a documented audit of what the current design is failing to do, not with a blank-canvas visual exploration. For products showing the signals that indicate a redesign is warranted, our UX audit service produces the prioritized findings and baseline measurements that any redesign brief requires. For teams ready to execute a full redesign from an audit-informed brief, our product redesign service covers the complete process from audit through post-launch measurement.