methodatlas
Session Builder

Plan my session

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

Method session1-2 h per session, plus 4-8 h preparation and synthesisWorkshop or asyncUsability Issues

Session: Usability Testing

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-8. 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 Usability Issues. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Briefing and warm-up

    5-10 min

    Welcome participant, explain purpose ("We are testing the product, not you"). Introduce think-aloud method, confirm consent. Demographic warm-up questions. Hint: Putting testers under pressure distorts results. Explicitly say "There is no wrong here". If tester goes silent, gently remind think-aloud.

    FacilitatorUsability Issues
  2. 2

    Phase 2: Run tasks

    30-45 min

    Read tasks in order. Testers work independently, moderator observes silently. If stuck, ask carefully ("What are you thinking right now?"). Do not help, do not suggest solution path. Hint: If tester is stuck after 5 min and success criterion is not reached, stop task. That is a data point, not a failure.

    FacilitatorSeverity List
  3. 3

    Phase 3: Post-task questions

    5-10 min

    After each task: difficulty rating (1-7), short "What was frustrating?" and "What was helpful?". At end, SEQ or UMUX-Lite questionnaire. Hint: Quantitative mini-scale plus qualitative rationale. Only quantitative is thin, only qualitative hard to compare.

    FacilitatorRecommendations
  4. 4

    Phase 4: Debrief per session

    10 min after each session

    Moderator and observers note top-3 problems each. Assign severity. Secure and store recording. Hint: Debrief immediately after session. Otherwise sessions blur in memory and detail is lost.

    FacilitatorUsability Issues
  5. 5

    Phase 5: Synthesis and ranking

    3-6 h after all sessions

    Aggregate all problems, consolidate duplicates. Per problem: frequency (how many testers affected) and severity. Sort top problems by frequency x severity. Derive recommendations. Hint: Frequency alone misleads. Show-stopper in 1/5 matters more than cosmetic note in 5/5. Take severity seriously.

    OwnerSeverity List
  6. 6

    Publish artifact

    10 min

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

    OwnerUsability Issues
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Usability Testing

Goal

Artifact: Usability Issues

Working Question

Can typical users complete the central tasks successfully, efficiently, and satisfactorily, and where do they fail on what?

Context

Tasks in order with wording; success criteria per task; known hypotheses (what we expect to fail); participant demographics; test environment with data setup.

Setup

  • Format: Method session
  • Duration: 1-2 h per session, plus 4-8 h preparation and synthesis
  • Mode: Workshop or async
  • Participants: One moderator for sessions; one to three silent observers from the team for notes; optional note-taker for synthesis; recruiter for 5-8 participants from target group.
  • Owner: One moderator for sessions
  • 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 Usability Issues. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Testable artifact (prototype, staging, live); task script with exact wording; recording tool (Lookback, Maze, Zoom with screen share); observation template (task, observed behavior, problems, severity 1-4); participant incentive.

Preparation

Plan 5-8 sessions of 45-60 min each (Nielsen threshold: 5 testers uncover about 85% of usability problems). Pilot with 1 person, then main runs. Silent observers in room or remote, moderator leads alone. Define severity scale (1=show-stopper, 4=cosmetic).

Agenda

  1. Phase 1: Briefing and warm-up (5-10 min) Owner: Facilitator Action: Welcome participant, explain purpose ("We are testing the product, not you"). Introduce think-aloud method, confirm consent. Demographic warm-up questions. Hint: Putting testers under pressure distorts results. Explicitly say "There is no wrong here". If tester goes silent, gently remind think-aloud. Output: Usability Issues

  2. Phase 2: Run tasks (30-45 min) Owner: Facilitator Action: Read tasks in order. Testers work independently, moderator observes silently. If stuck, ask carefully ("What are you thinking right now?"). Do not help, do not suggest solution path. Hint: If tester is stuck after 5 min and success criterion is not reached, stop task. That is a data point, not a failure. Output: Severity List

  3. Phase 3: Post-task questions (5-10 min) Owner: Facilitator Action: After each task: difficulty rating (1-7), short "What was frustrating?" and "What was helpful?". At end, SEQ or UMUX-Lite questionnaire. Hint: Quantitative mini-scale plus qualitative rationale. Only quantitative is thin, only qualitative hard to compare. Output: Recommendations

  4. Phase 4: Debrief per session (10 min after each session) Owner: Facilitator Action: Moderator and observers note top-3 problems each. Assign severity. Secure and store recording. Hint: Debrief immediately after session. Otherwise sessions blur in memory and detail is lost. Output: Usability Issues

  5. Phase 5: Synthesis and ranking (3-6 h after all sessions) Owner: Owner Action: Aggregate all problems, consolidate duplicates. Per problem: frequency (how many testers affected) and severity. Sort top problems by frequency x severity. Derive recommendations. Hint: Frequency alone misleads. Show-stopper in 1/5 matters more than cosmetic note in 5/5. Take severity seriously. Output: Severity 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: Usability Issues

Closeout

  • Update result artifact: Usability Issues
  • 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

Usability Issues: Usability Testing

Working Question

Can typical users complete the central tasks successfully, efficiently, and satisfactorily, and where do they fail on what?

Context

Tasks in order with wording; success criteria per task; known hypotheses (what we expect to fail); participant demographics; test environment with data setup.

Participants

  • Owner: One moderator for sessions
  • Participants: One moderator for sessions; one to three silent observers from the team for notes; optional note-taker for synthesis; recruiter for 5-8 participants from target group.

Input

Testable artifact (prototype, staging, live); task script with exact wording; recording tool (Lookback, Maze, Zoom with screen share); observation template (task, observed behavior, problems, severity 1-4); participant incentive.

Template

Usability Testing Working Template

Goal

Observes people using a design to uncover usability problems.

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

  • Usability Issues:
  • Severity List:
  • Recommendations:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Usability Issues 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

Usability Testing Working Template

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

usability-testing-working-template.md

Compact working template for Usability Testing with context, input, output artifacts, and next step.

Usability Testing Working Template

Goal

Observes people using a design to uncover usability problems.

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

  • Usability Issues:
  • Severity List:
  • Recommendations:

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 Usability Issues.
  • Own reports per test round with date and artifact version. Retests after fixes with explicit "tested against version Y on ..." status. Visualize trajectory of the most important problems across test rounds.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet