methodatlas
Session Builder

Plan my session

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

Method session30-90 minWorkshop or asyncStoryboard

Session: Storyboarding

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

  1. 1

    Phase 1: Invoke scenario and persona

    5-10 min

    Formulate scenario in one sentence ("Lisa, solo tax advisor, wants to submit VAT pre-return via app at quarter end"). Briefly recap persona profile. Hint: If scenario stays abstract ("user does task X"), storyboard becomes arbitrary. Concrete situation with time, place, trigger.

    FacilitatorStoryboard
  2. 2

    Phase 2: Identify key scenes

    10-15 min

    Which 6-10 key moments structure scenario? One frame placeholder per scene: trigger, context, action, reaction, transition. Fix order. Hint: Not every UI click is a frame. Frames are turning points or new contexts. 6-12 frames are enough for narrative arc.

    FacilitatorConcept Narrative
  3. 3

    Phase 3: Sketch frames

    20-40 min

    Per frame: persona in context (place, device, situation), action or reaction. Stick figures, simple shapes, speech bubbles. No finished UI, only visual sketch. Hint: Drawing UI detail slows down and loses narrative arc. Storyboard is story, not pixel design.

    FacilitatorTestable Assumptions
  4. 4

    Phase 4: Add annotations

    10-15 min

    Short text per frame: what happens, what persona thinks/feels. Name assumptions explicitly ("Assumption: Lisa has internet under quarter-end stress"). Transitions between frames as small arrows with trigger. Hint: Assumption list becomes the most important follow-up artifact. Per frame at least one verified assumption or clearly marked to validate.

    FacilitatorStoryboard
  5. 5

    Phase 5: Flow check and iteration

    10-15 min

    Have someone read storyboard as whole. Does flow stall? Are frames missing? Are transitions plausible? If gaps: add or merge two frames. Hint: An outsider unfamiliar with storyboard should understand story. If much explanation is needed, storyboard is not self-explanatory.

    OwnerConcept Narrative
  6. 6

    Publish artifact

    10 min

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

    OwnerStoryboard
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Storyboarding

Goal

Artifact: Storyboard

Working Question

How does the persona experience the scenario frame by frame, and which assumptions about context, behavior and expectations become visible?

Context

Scenario description; persona profile; existing wireframes or prototypes (if available); identified testable assumptions; purpose (concept pitch, user-test preparation, service design).

Setup

  • Format: Method session
  • Duration: 30-90 min
  • Mode: Workshop or async
  • Participants: One storyteller who provides scenario (often product or service designer); 1-7 sketchers (all skill levels); one note-taker for assumptions per frame.
  • Owner: One storyteller who provides scenario (often product or service designer)
  • 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 Storyboard. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Storyboard template with 6-12 frames (A4 or digital); markers, pens, stickies for annotations; for digital setup tool such as Miro, FigJam, Sketchbook or PowerPoint with frame layout.

Preparation

Template with 8-12 fields. Persona card at top, scenario sentence below. Agree pen convention (stick figures for actors, speech bubbles for dialog, arrows for movement). Sketches, no finished designs.

Agenda

  1. Phase 1: Invoke scenario and persona (5-10 min) Owner: Facilitator Action: Formulate scenario in one sentence ("Lisa, solo tax advisor, wants to submit VAT pre-return via app at quarter end"). Briefly recap persona profile. Hint: If scenario stays abstract ("user does task X"), storyboard becomes arbitrary. Concrete situation with time, place, trigger. Output: Storyboard

  2. Phase 2: Identify key scenes (10-15 min) Owner: Facilitator Action: Which 6-10 key moments structure scenario? One frame placeholder per scene: trigger, context, action, reaction, transition. Fix order. Hint: Not every UI click is a frame. Frames are turning points or new contexts. 6-12 frames are enough for narrative arc. Output: Concept Narrative

  3. Phase 3: Sketch frames (20-40 min) Owner: Facilitator Action: Per frame: persona in context (place, device, situation), action or reaction. Stick figures, simple shapes, speech bubbles. No finished UI, only visual sketch. Hint: Drawing UI detail slows down and loses narrative arc. Storyboard is story, not pixel design. Output: Testable Assumptions

  4. Phase 4: Add annotations (10-15 min) Owner: Facilitator Action: Short text per frame: what happens, what persona thinks/feels. Name assumptions explicitly ("Assumption: Lisa has internet under quarter-end stress"). Transitions between frames as small arrows with trigger. Hint: Assumption list becomes the most important follow-up artifact. Per frame at least one verified assumption or clearly marked to validate. Output: Storyboard

  5. Phase 5: Flow check and iteration (10-15 min) Owner: Owner Action: Have someone read storyboard as whole. Does flow stall? Are frames missing? Are transitions plausible? If gaps: add or merge two frames. Hint: An outsider unfamiliar with storyboard should understand story. If much explanation is needed, storyboard is not self-explanatory. Output: Concept Narrative

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

Closeout

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

Storyboard: Storyboarding

Working Question

How does the persona experience the scenario frame by frame, and which assumptions about context, behavior and expectations become visible?

Context

Scenario description; persona profile; existing wireframes or prototypes (if available); identified testable assumptions; purpose (concept pitch, user-test preparation, service design).

Participants

  • Owner: One storyteller who provides scenario (often product or service designer)
  • Participants: One storyteller who provides scenario (often product or service designer); 1-7 sketchers (all skill levels); one note-taker for assumptions per frame.

Input

Storyboard template with 6-12 frames (A4 or digital); markers, pens, stickies for annotations; for digital setup tool such as Miro, FigJam, Sketchbook or PowerPoint with frame layout.

Template

Workshop Agenda

Goal: ... Participants: ... Duration: ...

TimeMethodPurposeOutput
00:00Check-inSet focusShared start
00:10How Might WeIdeation questionsHMW list
00:35BrainwritingGenerate ideasIdea pool
01:10Dot VotingPrepare selectionPrioritized ideas
01:30StoryboardingMake the concept tangibleStoryboard

Close-out

Decision, owner, next test.

Completion Check

  • Storyboard 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

Workshop Agenda

View templateCompact agenda template for method sequences with timebox, purpose, and output.
agenda

workshop-agenda-markdown.md

Compact agenda template for method sequences with timebox, purpose, and output.

Workshop Agenda

Goal: ... Participants: ... Duration: ...

TimeMethodPurposeOutput
00:00Check-inSet focusShared start
00:10How Might WeIdeation questionsHMW list
00:35BrainwritingGenerate ideasIdea pool
01:10Dot VotingPrepare selectionPrioritized ideas
01:30StoryboardingMake the concept tangibleStoryboard

Close-out

Decision, owner, next test.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Storyboard.
  • One storyboard file per concept with date and scenario title. On iterations after user test or stakeholder feedback, create new version and keep old as reference. Track assumption validation status across versions.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet