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
Paper illustration of shared options, independently placed voting dots, and a highlighted shortlist.
Facilitation
Dot Voting
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.When a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection.
Complexitydifferent
LowMediumLow
Timedifferent
30-90 min2-6 h5-15 min
Participantsdifferent
2-122-83-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Timeline, Milestones, Insight NotesEvent Model, UI Flow, Commands, Read ModelsRanked list, Consensus signal, Shortlist
Tagsno overlap
TimelineFacilitationSequence
EventsBlueprintDomain-Driven DesignBehavior
FacilitationVotingConsensusPrioritization
Add more methods

Often compared together

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

Independent contributions form an ordered group priority list.
Facilitation
Nominal Group Technique
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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