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 IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
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.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 h1-3 h20–45 min1-3 h
Participantsdifferent
2-82-8Small cross-functional group3-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeIssue Map, Positions, Argument NotesRisk list, Mitigation plan, Assumption logFailure Scenarios, Risk Notes, Control Gaps, Test and Response Actions
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
RationaleKnowledgeDecision
RiskDecisionFailurePlanning
FailureResilienceRisk
Add more methods