View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile ROAM Board |  Domain Modeling EventStorming |  Facilitation Consensus Workshop |  Facilitation Problem Framing Workshop |
|---|---|---|---|---|
Purposedifferent | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-40 min initial, dann laufend | 2-8 h | 1-3 h | 60-120 min |
Participantsdifferent | 3-15 | 5-12 | 5-30 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | ROAM Board, Owner List | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Consensus Clusters, Theme Titles, Priority Areas | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | RiskAgileTrackingAlignment | Domain-Driven DesignEventsDiscoveryWorkshop | FacilitationConsensusWorkshopAlignment | FacilitationAlignmentDiscovery |