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 asyncProblem Evidence

Session: Problem 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-12 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 Problem Evidence. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Warm-up and context

    5-10 min

    Introduce yourself, state the purpose of the conversation in one sentence ("We are exploring how people like you handle X, without selling anything"). Start recording, GDPR notice. Hint: If the person asks about the solution, defer briefly ("I am happy to tell you, but first I would like to understand how it works today").

    FacilitatorProblem Evidence
  2. 2

    Phase 2: Concrete situation

    10-15 min

    Ask about the last concrete situation in which the topic was relevant. "Tell me step by step how that happened." Take notes with timestamps. Hint: Past situation beats hypothetical answer. "What did you do then?" is gold; "What would you do?" is wishful thinking.

    FacilitatorRisk Notes
  3. 3

    Phase 3: Pain and frequency

    10-15 min

    Probe deeper: how often does this happen? What did it cost (time, money, mood)? How important compared to other topics? Use "Tell me more about that" as standard follow-up. Hint: Concrete numbers (hours, euros, frequency per week) provide robust evidence. Without numbers, it remains impression.

    FacilitatorCustomer Segments
  4. 4

    Phase 4: Workarounds and alternatives

    5-10 min

    What does the person do today to address the problem? Which tools, tricks, colleagues, workarounds? How satisfied are they with that? Hint: Existing workarounds show real investment level. Someone with a workaround takes the problem seriously; someone who does nothing either does not have it or has resigned.

    FacilitatorProblem Evidence
  5. 5

    Phase 5: Close and notes

    5-10 min

    Reflect back the three most important takeaways and check them. Thank them. Immediately complete notes, mark three quotes with timestamp, enter problem-hypothesis evidence into template. Hint: Complete notes within 30 min. Otherwise detail memory frays and the interview loses half its value.

    OwnerRisk Notes
  6. 6

    Publish artifact

    10 min

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

    OwnerProblem Evidence
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Problem Interview

Goal

Artifact: Problem Evidence

Working Question

Is the assumed problem real, frequent and painful enough for the target person to justify solution investment?

Context

Problem hypothesis as one sentence; target segment with concrete persona; exclusion criteria; incentive; 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; note-taker or transcription tool; recruiter; synthesis team of two to four people after interviews.
  • Owner: Interviewer with discovery practice
  • 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 Problem Evidence. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Interview guide with 5-7 open questions around the problem hypothesis; recording tool with consent; notes template with columns situation, frequency, pain, workaround; recruiting plan.

Preparation

Record with consent. Keep guide open, no closed questions. Copy notes template. Write down pre-assumptions before the conversation so they can be challenged.

Agenda

  1. Phase 1: Warm-up and context (5-10 min) Owner: Facilitator Action: Introduce yourself, state the purpose of the conversation in one sentence ("We are exploring how people like you handle X, without selling anything"). Start recording, GDPR notice. Hint: If the person asks about the solution, defer briefly ("I am happy to tell you, but first I would like to understand how it works today"). Output: Problem Evidence

  2. Phase 2: Concrete situation (10-15 min) Owner: Facilitator Action: Ask about the last concrete situation in which the topic was relevant. "Tell me step by step how that happened." Take notes with timestamps. Hint: Past situation beats hypothetical answer. "What did you do then?" is gold; "What would you do?" is wishful thinking. Output: Risk Notes

  3. Phase 3: Pain and frequency (10-15 min) Owner: Facilitator Action: Probe deeper: how often does this happen? What did it cost (time, money, mood)? How important compared to other topics? Use "Tell me more about that" as standard follow-up. Hint: Concrete numbers (hours, euros, frequency per week) provide robust evidence. Without numbers, it remains impression. Output: Customer Segments

  4. Phase 4: Workarounds and alternatives (5-10 min) Owner: Facilitator Action: What does the person do today to address the problem? Which tools, tricks, colleagues, workarounds? How satisfied are they with that? Hint: Existing workarounds show real investment level. Someone with a workaround takes the problem seriously; someone who does nothing either does not have it or has resigned. Output: Problem Evidence

  5. Phase 5: Close and notes (5-10 min) Owner: Owner Action: Reflect back the three most important takeaways and check them. Thank them. Immediately complete notes, mark three quotes with timestamp, enter problem-hypothesis evidence into template. Hint: Complete notes within 30 min. Otherwise detail memory frays and the interview loses half its value. Output: Risk Notes

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

Closeout

  • Update result artifact: Problem Evidence
  • 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

Problem Evidence: Problem Interview

Working Question

Is the assumed problem real, frequent and painful enough for the target person to justify solution investment?

Context

Problem hypothesis as one sentence; target segment with concrete persona; exclusion criteria; incentive; legal consent.

Participants

  • Owner: Interviewer with discovery practice
  • Participants: Interviewer with discovery practice; note-taker or transcription tool; recruiter; synthesis team of two to four people after interviews.

Input

Interview guide with 5-7 open questions around the problem hypothesis; recording tool with consent; notes template with columns situation, frequency, pain, workaround; recruiting plan.

Template

Problem Interview Working Template

Goal

Validates whether a suspected problem is real, important, and frequent enough.

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

  • Problem Evidence:
  • Risk Notes:
  • Customer Segments:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Problem Evidence 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

Problem Interview Working Template

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

problem-interview-working-template.md

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

Problem Interview Working Template

Goal

Validates whether a suspected problem is real, important, and frequent enough.

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

  • Problem Evidence:
  • Risk Notes:
  • Customer Segments:

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 Problem Evidence.
  • Dedicated folder per discovery wave with date and hypothesis. Synthesis document as living document. Track status per hypothesis (confirmed, refuted, modified).
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet