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 |  Decision Making Force Field Analysis |  Product Discovery MVP Test Matrix |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | When several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 45-90 min | 45-75 min | 30-60 min |
Participantsdifferent | 2-8 | 3-12 | 2-8 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes | Test Matrix, Test Plan | Completed Experiment Canvas, Success Metric |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy | ExperimentsValidationDiscoveryOptions | ExperimentsValidationDiscoveryHypothesis |