View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Domain Storytelling | ![]() Decision Making Force Field Analysis | ![]() Knowledge Modeling IBIS | ![]() Domain Modeling Context Map |
|---|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-2 h | 45-90 min | 1-3 h | 1-3 h |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Force Field Map, Change Levers, Risk Notes | Issue Map, Positions, Argument Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | ChangeDecisionStrategy | RationaleKnowledgeDecision | Domain-Driven DesignBoundariesStrategy |



