methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session30-60 min per interview, plus 20 min synthesis per interviewWorkshop or asyncSolution Feedback

Session: Solution Interview

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 5-10 Interviews. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Solution Feedback. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Warm-up and problem recap

    5-10 min

    Introduction, purpose. Briefly return to the previously documented problem: "In our last conversation, you mentioned X". Get confirmation, keep context fresh. Hint: If the problem is not fresh in mind, reaction to solution becomes abstract. Problem reference is mandatory.

    FacilitatorSolution Feedback
  2. 2

    Phase 2: Show concept

    5-10 min

    Explain solution concept in max 3 min, with sketch or clickable prototype. Do not advertise benefits. "This is how we imagine it. What goes through your mind?" Hint: Pitch mode disrupts learning. If you explain for more than 5 min, you have already said too much and influenced reaction.

    FacilitatorObjection List
  3. 3

    Phase 3: Reaction and understanding

    10-15 min

    Collect first reaction. Understanding check: "Describe in your own words what this does." Document understanding gaps. Which value is perceived? Hint: If understanding is wrong, reaction is distorted. Secure understanding first, then ask deeper questions.

    FacilitatorValidation Notes
  4. 4

    Phase 4: Objections and willingness to pay

    10-15 min

    Actively ask for objections: "What would stop you from using this?" "What would need to be different?" Price or effort question: what would it be worth to you? Compare with current alternatives. Hint: A person who likes everything either has not thought seriously yet or wants to be polite. Objections are the more important signal.

    FacilitatorSolution Feedback
  5. 5

    Phase 5: Close and notes

    5-10 min

    Reflect back three most important objections and three strongest resonance points. Thank participant. Immediately complete notes, mark quotes, enter validation score in template. Hint: Validation score is not binary. A scale such as "credible interest, dependent on condition Y" is more informative than thumbs up or down.

    OwnerObjection List
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerSolution Feedback
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Solution Interview

Goal

Artifact: Solution Feedback

Working Question

Does the target person understand the solution, see its value for their concrete problem, and would they be willing to invest effort or money in it?

Context

Solution hypothesis as one sentence; target segment with concrete persona; problem evidence from previous interviews; price band or business-model assumptions; legal consent.

Setup

  • Format: Method session
  • Duration: 30-60 min per interview, plus 20 min synthesis per interview
  • Mode: Workshop or async
  • Participants: Interviewer with discovery practice (not sales); note-taker; recruiter; one designer or PM for synthesis.
  • Owner: Interviewer with discovery practice (not sales)
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Solution Feedback. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Solution concept as clickable prototype, mockup, sketch or description; interview guide with reaction questions and objection handling; recording tool; notes template with columns understanding, reaction, objection, willingness to pay.

Preparation

Recording with consent. Solution concept in maximum clarity but minimal polish (a sketch is enough). Guide: first reaction, then understanding check, then objections.

Agenda

  1. Phase 1: Warm-up and problem recap (5-10 min) Owner: Facilitator Action: Introduction, purpose. Briefly return to the previously documented problem: "In our last conversation, you mentioned X". Get confirmation, keep context fresh. Hint: If the problem is not fresh in mind, reaction to solution becomes abstract. Problem reference is mandatory. Output: Solution Feedback

  2. Phase 2: Show concept (5-10 min) Owner: Facilitator Action: Explain solution concept in max 3 min, with sketch or clickable prototype. Do not advertise benefits. "This is how we imagine it. What goes through your mind?" Hint: Pitch mode disrupts learning. If you explain for more than 5 min, you have already said too much and influenced reaction. Output: Objection List

  3. Phase 3: Reaction and understanding (10-15 min) Owner: Facilitator Action: Collect first reaction. Understanding check: "Describe in your own words what this does." Document understanding gaps. Which value is perceived? Hint: If understanding is wrong, reaction is distorted. Secure understanding first, then ask deeper questions. Output: Validation Notes

  4. Phase 4: Objections and willingness to pay (10-15 min) Owner: Facilitator Action: Actively ask for objections: "What would stop you from using this?" "What would need to be different?" Price or effort question: what would it be worth to you? Compare with current alternatives. Hint: A person who likes everything either has not thought seriously yet or wants to be polite. Objections are the more important signal. Output: Solution Feedback

  5. Phase 5: Close and notes (5-10 min) Owner: Owner Action: Reflect back three most important objections and three strongest resonance points. Thank participant. Immediately complete notes, mark quotes, enter validation score in template. Hint: Validation score is not binary. A scale such as "credible interest, dependent on condition Y" is more informative than thumbs up or down. Output: Objection List

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Solution Feedback

Closeout

  • Update result artifact: Solution Feedback
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Solution Feedback: Solution Interview

Working Question

Does the target person understand the solution, see its value for their concrete problem, and would they be willing to invest effort or money in it?

Context

Solution hypothesis as one sentence; target segment with concrete persona; problem evidence from previous interviews; price band or business-model assumptions; legal consent.

Participants

  • Owner: Interviewer with discovery practice (not sales)
  • Participants: Interviewer with discovery practice (not sales); note-taker; recruiter; one designer or PM for synthesis.

Input

Solution concept as clickable prototype, mockup, sketch or description; interview guide with reaction questions and objection handling; recording tool; notes template with columns understanding, reaction, objection, willingness to pay.

Template

Solution Interview Working Template

Goal

Tests reactions to a solution concept before it is fully built.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Solution Feedback:
  • Objection List:
  • Validation Notes:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Solution Feedback is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Solution Interview Working Template

View templateCompact working template for Solution Interview with context, input, output artifacts, and next step.
markdown

solution-interview-working-template.md

Compact working template for Solution Interview with context, input, output artifacts, and next step.

Solution Interview Working Template

Goal

Tests reactions to a solution concept before it is fully built.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Solution Feedback:
  • Objection List:
  • Validation Notes:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Solution Feedback.
  • One folder per concept version with date. Start new wave for larger concept updates; enable comparison of old and new wave.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet