Introduction

The most common portfolio evaluation mistake is treating redesign portfolio review the same as new product design portfolio review. A new product design portfolio is evaluated primarily for visual quality, design system maturity, and the sophistication of the interaction design. A redesign portfolio must be evaluated for something more specific: evidence that the agency understood an existing product’s problems through behavioral diagnosis, made design decisions grounded in that diagnosis rather than in aesthetic preference, validated those decisions against the existing user population, and can document the metric improvement that resulted. Visual quality without this evidence base indicates an agency that produces excellent new design — not necessarily an agency that produces excellent redesign. Figma case study walkthroughs where the agency shows the before-and-after of specific interaction decisions are a meaningful differentiator between agencies that understand redesign as a diagnostic discipline and those that treat it as a visual update exercise. WCAG 2.1 accessibility improvement documented in redesign case studies is a signal that the agency applies a systematic quality standard rather than a subjective one. The Nielsen Norman Group’s framework for evaluating UX work products provides the evidence quality standard against which redesign case study depth should be assessed.

How Evaluating a Product Redesign Agency Portfolio Works

Definition. Evaluating a product redesign agency portfolio is the process of reviewing case studies for evidence that the agency applied a diagnostic, evidence-grounded approach to improving existing products — including documented problem definition, behavioral audit findings, design decisions traceable to those findings, validation with existing users, and post-launch metric outcomes — rather than for visual quality alone.

What to look for in each redesign portfolio case study

• Documented problem statement — a specific description of what the existing product was failing to do, grounded in behavioral data, user research findings, or support ticket evidence rather than in a general description of poor user experience
• Audit methodology evidence — documentation of how the agency diagnosed the existing product’s problems, including what data they reviewed, what research they conducted, and how they prioritized findings before any design decision was made
• Design decision rationale — an explanation of why specific design choices were made in response to specific findings, establishing the connection between the diagnosis and the solution rather than presenting the solution as self-evidently correct
• Current user validation evidence — documentation that the structural redesign decisions were tested with users who had prior experience with the existing product, not only with new users or team members
• Post-launch behavioral outcomes — specific metric changes — activation rate, support ticket volume, task completion time — measured after the redesign launched, compared against documented pre-redesign baselines

What Portfolio Evidence Distinguishes Redesign Specialists from General Design Agencies

The portfolio evidence that distinguishes agencies who specialize in product redesign from those who apply general design methodology to redesign contexts is visible at four specific levels of case study analysis.

The problem definition level is the first distinguishing point. An agency with genuine redesign methodology defines problems in terms of documented user behavior failures — the specific steps where users are abandoning, the specific interactions generating support tickets, the specific flows where time-on-task exceeds what the task warrants. A general design agency defines problems in terms of subjective quality assessments — the product “felt dated,” the navigation was “confusing,” the visual design was “inconsistent.” The first definition can generate a measurable success criterion. The second cannot. When reading a case study, the specificity of the problem description predicts the specificity of the solution and the measurability of the outcome.

The design decision rationale level is the second distinguishing point. A redesign specialist explains why each significant design decision was made in response to the behavioral evidence the audit produced. The navigation was restructured to reflect the task frequency pattern revealed by analytics data. The onboarding flow was shortened by removing the steps that had the highest drop-off rates without producing the activation behaviors those steps were intended to generate. These rationales connect design decisions to behavioral evidence in a way that makes the case study instructive rather than merely impressive. A general design agency presents the design decisions as the output of a design process without connecting them to the specific evidence that justified each choice.

The validation evidence level is the third. Redesign case studies that document testing with current users — specifying that participants had prior experience with the existing product — are demonstrating the methodology that most reliably prevents the most expensive redesign failure mode: structural changes that improve the new-user experience while conflicting with the existing user base’s mental models. Case studies that describe “user testing” without specifying the participant profile have not demonstrated this methodology. Ask directly whether the case study’s testing involved current users of the existing product and what was found.

Common Mistakes to Avoid

Mistake: evaluating redesign portfolio visual quality rather than evidence quality. A beautifully presented case study with polished before-and-after screens and a coherent visual narrative demonstrates that the agency can produce attractive portfolio content. It does not demonstrate that the redesign produced measurable behavioral improvement or that the design decisions were grounded in behavioral evidence. Evaluate the evidence quality — the specificity of the problem definition, the documentation of the diagnostic methodology, the rationale for design decisions, and the post-launch metric data — not the visual sophistication of the portfolio presentation.

Mistake: accepting percentage improvement claims in portfolio case studies without asking how the metric was measured. A case study that claims “we improved user engagement by 47%” without specifying which engagement metric, over what time period, against what baseline, and using what measurement methodology is presenting a number without evidence. Ask how the metric was defined, what the pre-redesign baseline was, how the measurement was conducted, and what the measurement interval was. Agencies whose metric claims can withstand these questions have conducted genuine post-launch measurement. Agencies that cannot answer these questions produced a case study narrative rather than a documented outcome.

Mistake: treating a portfolio of visually diverse redesigns as evidence of broad capability rather than as a potential signal of shallow methodology. An agency whose redesign portfolio spans consumer apps, enterprise SaaS, healthcare platforms, fintech products, and e-commerce without documented specialist depth in any category may have a process that produces visually consistent quality across categories without the domain-specific knowledge that produces functionally superior redesigns in regulated or specialized sectors. Breadth of portfolio categories is a positive signal only when each category is represented by case studies with the problem definition, diagnostic methodology, and post-launch metric documentation that indicates depth of engagement rather than breadth of client acquisition.

Conclusion

In a product redesign agency portfolio, the evidence that predicts redesign quality is not visual — it is the specificity of the problem definition, the documentation of the diagnostic methodology, the rationale connecting design decisions to behavioral findings, the evidence of current user validation, and the post-launch metric documentation that confirms the redesign produced its intended behavioral improvement. Agencies whose case studies demonstrate all five of these evidence levels have built and applied a genuine redesign methodology. Agencies whose case studies demonstrate visual quality without this evidence have not demonstrated redesign methodology — they have demonstrated design quality in a context where the problem was predetermined. For companies evaluating redesign agencies with an unclear picture of their product’s actual problems, our UX audit service establishes the behavioral baseline that makes any agency’s redesign case studies directly comparable to your product’s situation. For teams ready to evaluate the full engagement, our product redesign service is backed by case studies that document the problem, the diagnosis, the validation, and the post-launch metric outcomes for each engagement.