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 | ![]() Delivery RAID Log | ![]() Knowledge Modeling Knowledge Mapping |
|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 1-2 h | 30 min Setup, dann laufend | 1-3 h |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | RAID Log, Status Report Source | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | RiskTrackingStakeholdersGovernance | KnowledgeMappingRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






