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
Paper timeline with three dates, parallel lanes for work, signals and decisions, and labeled links.
Facilitation
Timeline
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Purposedifferent
When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time.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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.
Complexitydifferent
LowMediumMedium
Timedifferent
30-90 min2-6 h30-90 min
Participantsdifferent
2-122-81-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Timeline, Milestones, Insight NotesEvent Model, UI Flow, Commands, Read ModelsDecision Tree, Option Map, Assumption List
Tagsno overlap
TimelineFacilitationSequence
EventsBlueprintDomain-Driven DesignBehavior
DecisionTreeOptions
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper matrix with six colored hat cards for information, feeling, value, caution, ideas and process control.
Facilitation
Six Thinking Hats
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming