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 |  Agile Specification by Example |  Facilitation Power Interest Grid |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 60-90 min pro Feature | 30-60 min | 1-2 h |
Participantsdifferent | 2-8 | 3-6 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Example Table, Acceptance Tests | Power Interest Grid, Strategy per Stakeholder | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AgileRequirementsExamplesBehavior-Driven Development | StakeholdersFacilitationAlignmentPlanning | AlignmentStakeholdersStrategyFacilitation |