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 for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
MediumMediumHighLow
Timedifferent
2-8 h60-120 min1-5 Tage45-90 min
Participantsdifferent
5-122-84-122-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsLogic Model, Change Objectives, Intervention Components, Evaluation PlanAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
Theory of ConstraintsAssumptionsSystems thinking
ChangeSystems thinkingCapability
AssumptionsRiskDecisionDiscovery
Add more methods