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 an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
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.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2-8 h1-3 h20-35 min30-60 min
Participantsdifferent
5-122-81-51-5
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsIssue Map, Positions, Argument NotesTest Card with a pre-set thresholdCompleted Experiment Canvas, Success Metric
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
RationaleKnowledgeDecision
ExperimentsValidationDiscoveryHypothesis
ExperimentsValidationDiscoveryHypothesis
Add more methods