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 | ![]() Facilitation Stakeholder Mapping | ![]() Facilitation Storytelling | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | When an insight needs to have an effect, storytelling translates dry facts into a comprehensible development. It combines context, tension, and consequence into a form that people remember and pass on more easily. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-2 h | 60–90 min | 45-120 min | 60-90 min |
Participantsdifferent | 2-8 | 2-8 | 1-6 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Stakeholder Map, Engagement Plan, Risk Notes | Narrative Outline, Key Message, Story Arc | Salience Diagram, Strategy per Class |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | StakeholdersAlignmentFacilitationChange | CommunicationNarrativeStakeholdersFacilitation | StakeholdersFacilitationAlignmentGovernance |



