validation-interview

Validation Interview

Overview

Validation interviews are not the same as discovery interviews. In discovery, you explore the problem. In validation, you present a proposed solution and gauge whether it works. This skill covers concept testing, prototype testing, and usability interview techniques.

When to Use

• You have a prototype or concept to test with real users
• You need to validate assumptions before committing to build
• You want to catch usability issues before shipping
• You're practicing continuous discovery — testing solutions as you design them
• Don't use for: early-stage discovery (use customer-interviews skill), quantitative validation (use A/B tests), or sales demos (different goal)

Instructions

1. Prepare the Interview

Define the goal: What specific assumptions are you testing?

Choose the method:

• Concept test: Show a description or mockup. Test desirability and comprehension.
• Prototype test: Let them use an interactive prototype. Test usability and flow.
• Wizard of Oz: Pretend the product works. Test the core value hypothesis.

Write the script:

• Opening: "I'm going to show you something we're thinking about building. I want your honest reaction — negative feedback is more valuable than positive."
• For each concept: "Here's the idea. What do you think this does?"
• For prototypes: "I'd like you to try completing [task]. Please think aloud as you go."
• Closing: "If this existed today, would you use it? Why or why not?"

2. Conduct the Interview

Do:

• Let users explore freely before explaining
• Ask "What would you expect to happen next?"
• Pay attention to body language and hesitation
• Encourage criticism: "What's wrong with this?"

Don't:

• Lead the user through the interface
• Explain what they missed (until after testing)
• Get defensive about your design
• Ask "Do you like it?" (production bias)
• Over-explain the concept (if it needs explanation, that's a finding)

3. Watch for Warning Signs