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 Power Interest Grid |  Engineering Goal Question Metric |  Facilitation Stakeholder 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. | When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 h | 30-60 min | 90-180 min | 60–90 min |
Participantsdifferent | 2-8 | 2-8 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Power Interest Grid, Strategy per Stakeholder | GQM Table, Metric Profiles | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | StakeholdersFacilitationAlignmentPlanning | MetricsMeasurementEngineeringAlignment | StakeholdersAlignmentFacilitationChange |