View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:EventStormingArchitecture Decision RecordProblem Framing WorkshopStakeholder Salience Model
| Criterion |  Domain Modeling EventStorming |  Architecture Architecture Decision Record |  Facilitation Problem Framing Workshop |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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 | Medium | Low | Low | Medium |
Timedifferent | 2-8 h | 15-45 min | 60-120 min | 60-90 min |
Participantsdifferent | 5-12 | 1-3 | 4-10 | 3-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | ADR File, Decision Log, Rationale | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureRationaleDocumentationGovernance | FacilitationAlignmentDiscovery | StakeholdersFacilitationAlignmentGovernance |