View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Knowledge Modeling Shape-First Modeling |  Product Discovery Assumption Mapping |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | Halber Tag pro Domain Slice | 45-60 min | 1-2 Wochen pro Iteration |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | 2-8 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Assumption map, Test backlog, Risk ranking | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Knowledge graphValidationSemantic | AssumptionsRiskExperimentsValidation | ExperimentsValidationDiscoveryAssumptions |