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 Event Modeling |  Business Strategy GAP Analysis |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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 | Medium | Medium | Low |
Timedifferent | 2-6 h | 1-3 h | 60–90 min |
Participantssame | 2-8 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Gap Matrix, Action Plan, Risk Notes | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | StrategyAnalysisPlanning | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
