View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Engineering Kanban |  Facilitation Consensus Workshop |  Facilitation Decision Jam |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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 decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | Ongoing | 1-3 h | 60-90 min |
Participantsdifferent | 2-8 | 2-12 | 5-30 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Kanban board, WIP policies, Flow metrics | Consensus Clusters, Theme Titles, Priority Areas | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | FlowVisual managementDelivery | FacilitationConsensusWorkshopAlignment | FacilitationDecisionProblem solvingWorkshop |