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 for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
MediumHighHigh
Timedifferent
2-6 h0.5-3 Tage1-4 h
Participantsdifferent
2-85-153-8
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRich Picture, Root Definitions, Conceptual Models, Change AgendaChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Soft systemsComplexitySensemakingSystems thinking
RiskDecisionSensemaking
Add more methods

Often compared together

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

Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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