methodatlas
Method guideProduct Discovery

Solution Interview

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time30-60 min je Interview
Participants5-10 Interviews
FormatWorkshop + async
MaturityEstablished
Plan
01

Prerequisite

What needs to be finished first

Complete firstProblem evidence

Understand the relevant problem and existing alternatives.

Otherwise an appealing demo is evaluated without a need.
Complete firstTestable representation

Prepare a consistent short representation and neutral tasks.

Inconsistent sales pitches make responses incomparable.
02

Preparation

What needs to be ready before start

Materials

Concept, neutral tasks, observation sheet.

People / roles

Target participant, neutral moderator, note-taker.

Pre-read

Prepare an evidenced problem and a concrete concept that can be presented neutrally.

Time needed

30–45 minutes conversation plus 15 minutes synthesis.

Setup

Fix concept version and tasks in advance; discuss the problem incident first, then show the same representation. Record observation separately from interpretation.

03

Core question

The one question this method answers

Does the person understand the approach, and what evidenced progress could it enable in their actual context?

04

Flow

Phases with goal, actions, output and pitfall

A Solution Interview uses a concrete concept to investigate whether people understand its value and how it fits their evidenced problem and current behaviour. Approval alone does not establish demand.

Solution Interview· worksheet

Fictional example

A Solution Interview uses a concrete concept to investigate whether people understand its value and how it fits their evidenced problem and current behaviour. Approval alone does not establish demand.

Problem and current alternative

Which real case provides the comparison baseline?

Fictional: P04 missed a last-minute room change and currently uses email. Only after this account does the team show a clickable change alert.

Concept and understanding

Which version was shown and how? What was understood or done unaided?

Version 2 shows room, start time and acknowledgement. P04 locates the room but interprets acknowledgement as a binding course commitment. Moderator help is logged separately.

Fit and objections

Which concrete improvement, prerequisite and switching barrier was identified?

Objection: push notifications are silenced during travel. Value therefore depends on timing and an acceptable alternative. Another app alone does not resolve the case.

Follow-up signal and decision

Distinguish statement, observed action, fulfilled commitment and remaining uncertainty.

P04 voluntarily books an available trial session. This is an appointment, not a purchase. The team simplifies the label and tests timely notice during the pilot.

All example details are fictional and illustrate the application.

Ash Maurya: Running Lean im Gespräch

  1. 1

    Baseline

    Baseline

    Goal

    Problem anchor

    Inputs for this step

    • Existing problem evidence

    Actions

    • Briefly reconstruct the last problem incident and current alternative.
    • Show the concept only afterwards so it does not shape recall.

    Output

    Problem anchor

    Was the baseline recorded before the demo?

    Quality check

    Was the baseline recorded before the demo?

    Pitfall

    The demonstration presumes the supposed problem. Ask about the actual incident first.

    Timing: 5–10 minutes

  2. 2

    Understanding

    Understanding

    Goal

    Understanding findings

    Inputs for this step

    • Concept and task

    Actions

    • Show the concept briefly and consistently; ask the person to explain value and flow in their own words.
    • Wait for reactions rather than defending benefits; use neutral tasks for interaction.

    Output

    Understanding findings

    What does the person understand without extra help?

    Quality check

    What does the person understand without extra help?

    Pitfall

    The moderator immediately explains away every confusion. Record confusion and required help as findings.

    Timing: 10 minutes

  3. 3

    Fit

    Fit review

    Goal

    Fit and objections

    Inputs for this step

    • Problem anchor and concept findings

    Actions

    • Compare the approach with the actual incident and existing alternative.
    • Explore prerequisites, disadvantages, switching effort and purchase decisions; price reactions remain statements until a real offer is tested.

    Output

    Fit and objections

    Are benefits and barriers tied to a case?

    Quality check

    Are benefits and barriers tied to a case?

    Pitfall

    A requested feature is immediately promised. Understand the reason behind the request and record it openly.

    Timing: 10–15 minutes

  4. 4

    Follow-up

    Follow-up

    Goal

    Test decision

    Inputs for this step

    • Findings and real follow-up option

    Actions

    • Distinguish statements, observed actions and actual commitments.
    • Offer a voluntary next step that is genuinely available; verify completion later and record the learning decision.

    Output

    Test decision

    Is commitment separate from fulfilment?

    Quality check

    Is commitment separate from fulfilment?

    Pitfall

    Pilot interest is counted as a purchase. Label the signal accurately and plan the next behavioural evidence.

    Timing: 10–15 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Solution InterviewShow a solution concept or prototype to test understanding, objections, willingness to use, and next validation steps
Solution InterviewThe visual shows a solution concept, interview reactions, understanding, objections, signals, validation notes, and the next test.Validate a solution idea before it is fully builtThe conversation separates understanding, objections, and real usage or buying signals.do not sellobserve reactionderive riskSolution conceptprototype, pitch, or mockupInterviewshow, observe, askUnderstandingis the value clear?Objectionsrisks, doubtsSignaltime, money, usageValidation Notesseparate value, usability, andriskNext testfake door, usability, or MVP
Form

Concept findings on understanding, fit, objections and verifiable follow-up.

Versioning / ownership

Record date and scope; retain the previous version and reason when changing it.

Tool alternatives
  • Paper concept
  • Clickable prototype
  • Observation sheet with version

solution-interview-working-template.md

Prepare an evidenced problem and a concrete concept that can be presented neutrally.

Solution Interview: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete cycle Time: 30–45 minutes conversation plus 15 minutes synthesis.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Concept, neutral tasks, observation sheet.
  • Roles: Target participant, neutral moderator, note-taker.
  • Advance information: Prepare an evidenced problem and a concrete concept that can be presented neutrally.
  • Overall time needed: 30–45 minutes conversation plus 15 minutes synthesis.
  • Setup: Fix concept version and tasks in advance; discuss the problem incident first, then show the same representation. Record observation separately from interpretation.

Prepare for the work steps

Baseline: Baseline

  • Existing problem evidence

Understanding: Understanding

  • Concept and task

Fit: Fit review

  • Problem anchor and concept findings

Follow-up: Follow-up

  • Findings and real follow-up option

Solution Interview· worksheet

Problem and current alternative

Which real case provides the comparison baseline?

...

Concept and understanding

Which version was shown and how? What was understood or done unaided?

...

Fit and objections

Which concrete improvement, prerequisite and switching barrier was identified?

...

Follow-up signal and decision

Distinguish statement, observed action, fulfilled commitment and remaining uncertainty.

...

Answer the prompts with your own information. Explicitly mark unknowns and assumptions.

Ash Maurya: Running Lean im Gespräch

Baseline: Baseline

Expected artifact: Problem anchor

Was the baseline recorded before the demo?

Entry:

...

  • Was the baseline recorded before the demo?

Understanding: Understanding

Expected artifact: Understanding findings

What does the person understand without extra help?

Entry:

...

  • What does the person understand without extra help?

Fit: Fit review

Expected artifact: Fit and objections

Are benefits and barriers tied to a case?

Entry:

...

  • Are benefits and barriers tied to a case?

Follow-up: Follow-up

Expected artifact: Test decision

Is commitment separate from fulfilment?

Entry:

...

  • Is commitment separate from fulfilment?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/solution-interview/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

solution-interview-beispiel.md

Concrete filled scenario, fictional example

Fictional example

Problem and current alternative: Fictional: P04 missed a last-minute room change and currently uses email. Only after this account does the team show a clickable change alert.

Concept and understanding: Version 2 shows room, start time and acknowledgement. P04 locates the room but interprets acknowledgement as a binding course commitment. Moderator help is logged separately.

Fit and objections: Objection: push notifications are silenced during travel. Value therefore depends on timing and an acceptable alternative. Another app alone does not resolve the case.

Follow-up signal and decision: P04 voluntarily books an available trial session. This is an appointment, not a purchase. The team simplifies the label and tests timely notice during the pilot.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. BaselineThe demonstration presumes the supposed problem.View in phase
  2. UnderstandingThe moderator immediately explains away every confusion.View in phase
  3. Fit reviewA requested feature is immediately promised.View in phase
  4. Follow-upPilot interest is counted as a purchase.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

If praise replaces behaviour, examine a concrete barrier and agree an honest next test.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.