methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-6 h60-90 min1-3 h1-2 h
Participantsdifferent
2-84-102-84-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsProblem Cluster, Prioritized Challenge, ExperimentContext Map, Integration Patterns, Boundary NotesAlignment Map, Open Issues, Decision Questions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
FacilitationDecisionProblem solvingWorkshop
Domain-Driven DesignBoundariesStrategy
AlignmentStakeholdersStrategyFacilitation
Add more methods