View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Assumption Mapping |  Knowledge Modeling Shape-First Modeling |  Architecture Risk Storming |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | Medium | Low | High |
Timedifferent | 45-60 min | Halber Tag pro Domain Slice | 60-90 min | 1-4 Wochen |
Participantsdifferent | 2-8 | 1-4 | 4-12 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Assumption map, Test backlog, Risk ranking | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Annotated Diagram, Prioritized Risk List, Action Backlog | Experiment results, Decision log, Learning summary |
Tags1 shared | AssumptionsRiskExperimentsValidation | Knowledge graphValidationSemantic | RiskArchitectureWorkshopValidation | ExperimentsGrowthAnalyticsValidation |