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 |  Facilitation Stakeholder Salience Model |  Facilitation Consensus Workshop |  Domain Modeling EventStorming |
|---|---|---|---|---|
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. | 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. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-6 h | 60-90 min | 1-3 h | 2-8 h |
Participantsdifferent | 2-8 | 3-6 | 5-30 | 5-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Salience Diagram, Strategy per Class | Consensus Clusters, Theme Titles, Priority Areas | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | StakeholdersFacilitationAlignmentGovernance | FacilitationConsensusWorkshopAlignment | Domain-Driven DesignEventsDiscoveryWorkshop |