User Research for Product Redesign: How to Validate Before You Rebuild

User Research for Product Redesign: Validate Before You Rebuild

The short answer: User research for product redesign is the process of gathering customer insights before, during, and after a major product overhaul. It prevents redesigns that look good internally but confuse or alienate existing users. With AI interview platforms like Koji, research teams can run 20+ redesign validation interviews in days rather than weeks.

Why Redesigns Fail Without Research

Product redesigns have a 60–70% failure rate when measured by user adoption metrics post-launch. The most common causes:

Internal echo chamber: Teams design for their own mental models, not users' mental models
Aesthetic over functional: Beautiful redesigns that break familiar workflows
Assumption of equivalence: Assuming the new design solves the same problems as the old one
Missing the mental model gap: Users have deeply ingrained patterns; redesigns that ignore these create friction

The solution is not to avoid redesigning — it is to ground every significant redesign decision in research.

When to Run Redesign Research

Before the Redesign: Discovery Research

This is the most important phase. Before touching a single wireframe, you need to understand:

Why users do things the way they currently do
What is broken about the current experience (in their words, not yours)
What they wish they could do that they currently cannot
Which parts of the current design they would never give up

During the Redesign: Concept Testing

As you develop design concepts, test early. Key questions:

Do users understand the new navigation model?
Does the new information architecture match how they think about tasks?
Are they confused by changes to familiar workflows?

Before Launch: Regression Validation

A final round of research to confirm that redesign goals have been met and no critical regressions have been introduced in workflows users rely on.

Phase 1: Discovery — Understanding the Current Experience

Start by interviewing current users about their existing experience. Critically: do not lead with questions about the redesign. You want unbiased insight into how they actually use your product today.

Key Discovery Questions

"Walk me through how you typically use [product] in a given week."
"What do you spend most of your time doing in [product]?"
"What frustrates you most about your current workflow?"
"Have you ever felt lost or confused in [product]? Tell me about that."
"Are there things you wish you could do in [product] that you currently cannot?"

Use open-ended questions with AI probing enabled (set maxFollowUps to 2) to draw out the nuanced stories behind these answers. See how Koji's AI probing works for details.

What You Are Looking For

Jobs to be done: What are users actually trying to accomplish?
Workarounds: How are they compensating for current design limitations?
Anchor points: Which UI elements or workflows do they rely on most?
Pain points in their words: The exact language they use to describe friction

Phase 2: Mental Model Mapping

Before sketching wireframes, map user mental models. This is the step most redesign teams skip — and the most valuable.

Mental Model Questions

"If you were explaining [product] to a new colleague, how would you describe what it does?"
"When you think about your work, how does [product] fit into your day?"
"How do you think about the different parts of [product]? Do you think of them as separate tools or one connected thing?"

Use structured question types to test categorization assumptions:

Single choice: "Which of these best describes how you primarily use [product]?" [Offer your assumed segments]
Ranking: "Rank these features in order of how often you use them." [Your navigation items]
Yes/No: "Do you use [product] as part of a team workflow, or primarily on your own?"

Phase 3: Concept Testing the Redesign

Once you have early designs (even wireframes), bring users back for concept testing. This should be a separate Koji study.

Framing: "We are working on a new version of [product]. I would like to share some early concepts and get your honest reaction. There are no right or wrong answers — your first impressions are exactly what we are looking for."

Concept Testing Questions

Open-ended: "Looking at this screen for the first time, what is your first impression?"
Open-ended: "What would you expect to happen if you clicked [X]?"
Scale (1–5): "How intuitive does this feel compared to your current experience?" (1 = Much harder, 5 = Much easier)
Yes/No: "Would you be able to find [core task] on this screen without help?"
Open-ended: "What is confusing or unclear about this design?"
Single choice: "How does this design compare to what you use today?" [Better / About the same / Worse]
Open-ended (probed): "What specifically gives you that impression?"

Phase 4: Regression Validation Before Launch

The final research phase checks for regressions — places where the redesign accidentally broke things that worked before.

Key questions:

"Was there anything in the new design that felt different or confusing compared to what you are used to?"
Scale (1–10): "How confident are you that you could find [specific feature] in the new design?"
Yes/No: "Does the new design feel faster or slower than the current one for your typical tasks?"
Open-ended: "Is there anything from the current design that you would miss in this new version?"

Structured Questions That Unlock Redesign Insights

Koji's six question types are particularly powerful for redesign research:

Question Type	Best Use in Redesign Research
Open-ended	Discovery stories, first impressions, confusion capture
Scale	Benchmarking old vs. new intuitiveness (1–5 or 1–10)
Single choice	Navigation categorization, design preference
Yes/No	Quick hypothesis checks ("Is it clear what this does?")
Ranking	Information architecture — rank menu items in expected order
Multiple choice	Identify which areas feel most outdated or frustrating

See the structured questions guide for detailed setup instructions for each type.

Analyzing Redesign Research Data

Koji automatically surfaces:

Theme detection: Patterns across multiple interviews. If navigation confusion appears in 8 of 12 interviews, it surfaces as a primary theme in the themes dashboard.

Sentiment analysis: The emotional tone of responses to specific design choices. Negative sentiment on specific screens is an early warning signal.

Individual insights: Per-respondent summaries showing how each user responded to specific design elements.

Research report: An aggregated report ready to share with your design, engineering, and leadership teams via URL.

Use the insights chat to ask targeted questions: "Which design element received the most negative feedback?" or "What did power users say about the new navigation?"

How Many Redesign Interviews Do You Need?

Phase	Recommended Sample
Discovery	8–12 users covering your core use cases
Concept testing	8–10 per design concept
Launch validation	5–8 users across key segments

With Koji's asynchronous format, you can run all three phases in under two weeks — without scheduling a single call. Share the link, collect responses over 48 hours, and review the AI-generated report.

Common Redesign Research Mistakes

Mistake 1: Only testing with power users

Power users are your most flexible users — they will adapt to almost anything. Test with casual users, infrequent users, and users who have struggled with the current design.

Mistake 2: Showing final designs too early

High-fidelity mockups prime users to assume "this is done" and they soften their feedback. Use wireframes for concept testing — users will be more honest.

Mistake 3: Asking "Do you like the new design?"

Ask instead: "What questions does this design raise for you?" or "What would you need to figure out before you felt comfortable with this?"

Mistake 4: Skipping discovery

Without discovery research, you do not know which problems you are solving — which means you cannot evaluate whether your redesign actually solves them.

Mistake 5: Not including churned users

Churned users often left because the existing design frustrated them. Their feedback on what is broken is more valuable than almost any other segment.

Setting Up Redesign Research in Koji

Step 1: Create a discovery study with open-ended interview mode. Upload your product context document to give the AI interviewer background on your product.

Step 2: Use hybrid mode for concept testing — structured questions to benchmark design performance, open-ended questions to capture reactions and confusion.

Step 3: Target the right participants using CRM import. Filter by usage tier to separate power users from casual users.

Step 4: Share a personalized link with a message explaining this is part of your redesign research.

Step 5: Generate and share your report. Your design team, engineering lead, and stakeholders can access it directly via URL — no platform login required.

Product & Research

Revenue & Growth

Advisory & Services