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 |  Product Strategy ICE Scoring |  Product Discovery Assumption Mapping |  Growth A/B Testing |
|---|---|---|---|---|
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 ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 30-60 min | 45-60 min | 1-4 Wochen |
Participantsdifferent | 2-8 | 2-8 | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | ICE Table, Top Idea List | Assumption map, Test backlog, Risk ranking | Experiment results, Decision log, Learning summary |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | PrioritizationScoringGrowthDecision | AssumptionsRiskExperimentsValidation | ExperimentsGrowthAnalyticsValidation |