methodatlas
Session Builder

Plan my session

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

Method session90-180 min per inquiry plus 60 min follow-upWorkshop or asyncField Notes

Session: Contextual Inquiry

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 4-12 Beobachtungen. 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 Field Notes. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    0-10 min

    10 min

    Introduction on the workstation: introductions, consent confirmation, explanation of the Master-Apprentice model. Briefly brief the task the person is anyway completing today. Hint: If the person prepared a special task for the study, the method is contaminated. Repeat the instruction: normal work in normal sequence.

    FacilitatorField Notes
  2. 2

    10-90 min

    80 min

    Observe and ask clarifying questions: participant works, researcher observes, asks questions in the flow ("What are you doing now?", "Why this way?"). Document artifacts, screens, and workarounds. Hint: If the researcher speaks more than the participant, the balance is off. Rule of thumb: 20% researcher, 80% participant. Hold silence and let the participant continue explaining.

    FacilitatorWorkflow Insights
  3. 3

    90-110 min

    20 min

    Review with the participant: walk through observed steps together, validate interpretations, and clarify open questions. The participant confirms or corrects what the researcher understood. Hint: Skipping this phase moves interpretation to a later solo effort. Recapping with the participant saves hours during synthesis and avoids misinterpretation.

    FacilitatorPain Points
  4. 4

    110-120 min

    10 min

    Close: thank the participant, define next step (feedback loop), and provide contact details for follow-up questions. Stop the recording and say goodbye. Hint: Do not evaluate in front of the participant. Impressions are not yet synthesized; premature conclusions can frustrate or upset them.

    FacilitatorField Notes
  5. 5

    120-180 min

    60 min

    Immediately after the session, do structured follow-up: complete field notes, skim the recording, form initial theme clusters, sort photos, and note open questions for the next inquiry. Hint: If synthesis takes place later than 24 hours, impressions blur. Invest at least 30 minutes the same day; do full synthesis within 48 hours.

    OwnerWorkflow Insights
  6. 6

    Publish artifact

    10 min

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

    OwnerField Notes
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Contextual Inquiry

Goal

Artifact: Field Notes

Working Question

How does the participant carry out their work in the real context, which workarounds, artifacts, and implicit assumptions shape the process, and which of these observations are design-relevant?

Context

Written consent; explanation of the Master-Apprentice model (user is the master, researcher is the apprentice); briefing on time window, duration, and recording; expectation that normal work should continue with no demonstration.

Setup

  • Format: Method session
  • Duration: 90-180 min per inquiry plus 60 min follow-up
  • Mode: Workshop or async
  • Participants: One primary researcher (lead interviewer and observer); optional note-taking partner; the user performing work in their real context; and one organization representative for safety-critical devices or rooms if required.
  • Owner: One primary researcher (lead interviewer and observer)
  • 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 Field Notes. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Notebook or tablet with an observation template; recorder (audio or video) with consent; camera for artifact photos; travel setup for on-site visits (power, business cards); structured field notes template.

Preparation

Meet at the participant's actual workplace, not in a meeting room. Researcher sits beside or slightly behind the person, not opposite. Place recording device visibly. Start with a 5-minute setup: explain the model, confirm consent, and clarify when interruptions are acceptable.

Agenda

  1. 0-10 min (10 min) Owner: Facilitator Action: Introduction on the workstation: introductions, consent confirmation, explanation of the Master-Apprentice model. Briefly brief the task the person is anyway completing today. Hint: If the person prepared a special task for the study, the method is contaminated. Repeat the instruction: normal work in normal sequence. Output: Field Notes

  2. 10-90 min (80 min) Owner: Facilitator Action: Observe and ask clarifying questions: participant works, researcher observes, asks questions in the flow ("What are you doing now?", "Why this way?"). Document artifacts, screens, and workarounds. Hint: If the researcher speaks more than the participant, the balance is off. Rule of thumb: 20% researcher, 80% participant. Hold silence and let the participant continue explaining. Output: Workflow Insights

  3. 90-110 min (20 min) Owner: Facilitator Action: Review with the participant: walk through observed steps together, validate interpretations, and clarify open questions. The participant confirms or corrects what the researcher understood. Hint: Skipping this phase moves interpretation to a later solo effort. Recapping with the participant saves hours during synthesis and avoids misinterpretation. Output: Pain Points

  4. 110-120 min (10 min) Owner: Facilitator Action: Close: thank the participant, define next step (feedback loop), and provide contact details for follow-up questions. Stop the recording and say goodbye. Hint: Do not evaluate in front of the participant. Impressions are not yet synthesized; premature conclusions can frustrate or upset them. Output: Field Notes

  5. 120-180 min (60 min) Owner: Owner Action: Immediately after the session, do structured follow-up: complete field notes, skim the recording, form initial theme clusters, sort photos, and note open questions for the next inquiry. Hint: If synthesis takes place later than 24 hours, impressions blur. Invest at least 30 minutes the same day; do full synthesis within 48 hours. Output: Workflow Insights

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

Closeout

  • Update result artifact: Field Notes
  • 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

Field Notes: Contextual Inquiry

Working Question

How does the participant carry out their work in the real context, which workarounds, artifacts, and implicit assumptions shape the process, and which of these observations are design-relevant?

Context

Written consent; explanation of the Master-Apprentice model (user is the master, researcher is the apprentice); briefing on time window, duration, and recording; expectation that normal work should continue with no demonstration.

Participants

  • Owner: One primary researcher (lead interviewer and observer)
  • Participants: One primary researcher (lead interviewer and observer); optional note-taking partner; the user performing work in their real context; and one organization representative for safety-critical devices or rooms if required.

Input

Notebook or tablet with an observation template; recorder (audio or video) with consent; camera for artifact photos; travel setup for on-site visits (power, business cards); structured field notes template.

Template

Contextual Inquiry Working Template

Goal

Observes and interviews users while they are doing real work in their actual context of use.

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

  • Field Notes:
  • Workflow Insights:
  • Pain Points:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Field Notes 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

Contextual Inquiry Working Template

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

contextual-inquiry-working-template.md

Compact working template for Contextual Inquiry with context, input, output artifacts, and next step.

Contextual Inquiry Working Template

Goal

Observes and interviews users while they are doing real work in their actual context of use.

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

  • Field Notes:
  • Workflow Insights:
  • Pain Points:

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 Field Notes.
  • One file per inquiry with date, role, and pseudonym in the header. Pseudonymize personally identifiable data. Keep aggregated synthesis linked to individual inquiries to preserve traceability.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet