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
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
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent
MediumLow
Timedifferent
2-8 h45-90 min
Participantsdifferent
5-123-12
Formatsame
WorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsForce Field Map, Change Levers, Risk Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ChangeDecisionStrategy
Add more methods

Often compared together

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

Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam