methodatlas
Session Builder

Plan my session

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

Method session2-8 hWorkshopEvent Timeline

Session: EventStorming

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

  1. 1

    Phase 1: Chaotic Storming

    30-60 min

    All participants write Domain Events (orange, past tense) in parallel and place them roughly in chronological order on the wall. No sorting, no discussion. Hint: Expect 80-300 events. If only 30 events are present after 20 min, domain knowledge is missing or the question is too narrow. No one corrects things in this phase.

    FacilitatorEvent Timeline
  2. 2

    Phase 2: Timeline Enforcement

    30-45 min

    Order events chronologically, consolidate duplicates, mark gaps. Highlight pivotal events (turning points), for example by moving them upward. Hint: Disagreement about order is useful, not a disruption. If the group cannot agree, place both variants and mark them as a Hot Spot.

    FacilitatorUbiquitous Language
  3. 3

    Phase 3: Commands, Actors, Policies

    45-90 min

    Place the triggering command (blue) and Actor (yellow) in front of each event. Mark automatic follow-up reactions as Policies (purple). Add Read Models (green) where decisions need data. Hint: If no command fits in front of an event, it is either an external trigger (system, time) or a gap. Make both explicit.

    FacilitatorBoundaries
  4. 4

    Phase 4: Hot Spots and Boundaries

    30-45 min

    Use pink for each point of friction, risk, uncertainty, or conflict. Then draw boundaries (dashed lines) for bounded contexts or organizational boundaries. Hint: Hot Spots are the most valuable output, not a lack. If none appear, the facilitator should explicitly ask for workarounds, escalations, and exceptions.

    FacilitatorOpen Questions
  5. 5

    Phase 5: Follow-ups and Outputs

    20-30 min

    Photograph the wall at each phase. Name one owner and next action per Hot Spot. Derive glossary terms from events and include them in the Ubiquitous Language. Hint: Without named follow-ups, energy dissipates. At least three Hot Spots need owner and date before the workshop ends.

    OwnerEvent Timeline
  6. 6

    Publish artifact

    10 min

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

    OwnerEvent Timeline
Usable artifact

Session Brief

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

session-brief.md

Session Brief: EventStorming

Goal

Artifact: Event Timeline

Working Question

Which business events, triggers, and boundaries shape the flow, and where do friction, risk, or learning needs arise?

Context

Clearly bounded business flow (e.g. "from order entry to fulfillment"); glossary of known domain terms; existing process documentation as backup, not as template.

Setup

  • Format: Method session
  • Duration: 2-8 h
  • Mode: Workshop
  • Participants: A facilitator with EventStorming experience; three to six domain experts from business; two to four engineers or architects; one scribe for hot spots and open questions.
  • Owner: A facilitator with EventStorming experience
  • 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 Event Timeline. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Large wall or digital board with at least 8 m of horizontal space; orange sticky notes (Events), blue (Commands), yellow (Actors), pink (Hot Spots), purple (Policies), green (Read Models); markers; camera for snapshots; parking-lot area.

Preparation

Mark wall with timeline (left start, right end). Make the color legend visible. State the rule: Events are in past tense and business-relevant. Phones away, no laptops except for the scribe.

Agenda

  1. Phase 1: Chaotic Storming (30-60 min) Owner: Facilitator Action: All participants write Domain Events (orange, past tense) in parallel and place them roughly in chronological order on the wall. No sorting, no discussion. Hint: Expect 80-300 events. If only 30 events are present after 20 min, domain knowledge is missing or the question is too narrow. No one corrects things in this phase. Output: Event Timeline

  2. Phase 2: Timeline Enforcement (30-45 min) Owner: Facilitator Action: Order events chronologically, consolidate duplicates, mark gaps. Highlight pivotal events (turning points), for example by moving them upward. Hint: Disagreement about order is useful, not a disruption. If the group cannot agree, place both variants and mark them as a Hot Spot. Output: Ubiquitous Language

  3. Phase 3: Commands, Actors, Policies (45-90 min) Owner: Facilitator Action: Place the triggering command (blue) and Actor (yellow) in front of each event. Mark automatic follow-up reactions as Policies (purple). Add Read Models (green) where decisions need data. Hint: If no command fits in front of an event, it is either an external trigger (system, time) or a gap. Make both explicit. Output: Boundaries

  4. Phase 4: Hot Spots and Boundaries (30-45 min) Owner: Facilitator Action: Use pink for each point of friction, risk, uncertainty, or conflict. Then draw boundaries (dashed lines) for bounded contexts or organizational boundaries. Hint: Hot Spots are the most valuable output, not a lack. If none appear, the facilitator should explicitly ask for workarounds, escalations, and exceptions. Output: Open Questions

  5. Phase 5: Follow-ups and Outputs (20-30 min) Owner: Owner Action: Photograph the wall at each phase. Name one owner and next action per Hot Spot. Derive glossary terms from events and include them in the Ubiquitous Language. Hint: Without named follow-ups, energy dissipates. At least three Hot Spots need owner and date before the workshop ends. Output: Event Timeline

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

Closeout

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

Event Timeline: EventStorming

Working Question

Which business events, triggers, and boundaries shape the flow, and where do friction, risk, or learning needs arise?

Context

Clearly bounded business flow (e.g. "from order entry to fulfillment"); glossary of known domain terms; existing process documentation as backup, not as template.

Participants

  • Owner: A facilitator with EventStorming experience
  • Participants: A facilitator with EventStorming experience; three to six domain experts from business; two to four engineers or architects; one scribe for hot spots and open questions.

Input

Large wall or digital board with at least 8 m of horizontal space; orange sticky notes (Events), blue (Commands), yellow (Actors), pink (Hot Spots), purple (Policies), green (Read Models); markers; camera for snapshots; parking-lot area.

Template

Event Storming Working Template

Goal

Rapid, visual domain exploration through Business Events, Commands, Policies, and Actors on a timeline.

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

  • Event timeline:
  • Ubiquitous language:
  • Boundaries:
  • Open questions:

Assumptions and open questions

  • ...

Decision / next step

Owner, date, and success signal.

Completion Check

  • Event Timeline 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

Event Storming Working Template

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

event-storming-working-template.md

Compact working template for Event Storming with context, input, output artifacts, and next step.

Event Storming Working Template

Goal

Rapid, visual domain exploration through Business Events, Commands, Policies, and Actors on a timeline.

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

  • Event timeline:
  • Ubiquitous language:
  • Boundaries:
  • Open questions:

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 Event Timeline.
  • One folder per workshop with date, participant list, and phase snapshots. For follow-up workshops, do not overwrite but create a new version and document the delta.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet