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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.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.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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
1-2 h45-90 min2-6 h1-3 h
Participantssame
2-82-82-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeAssumption List, Critical Assumptions, Learning PlanEvent Model, UI Flow, Commands, Read ModelsIssue Map, Positions, Argument Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
AssumptionsRiskDecisionDiscovery
EventsBlueprintDomain-Driven DesignBehavior
RationaleKnowledgeDecision
Add more methods