View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Knowledge Modeling Shape-First Modeling |  Product Discovery Hypothesis Prioritization Canvas |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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 many hypotheses compete for attention, it brings order to their learning sequence and importance. It separates problem, assumption, solution, and evidence. The result is captured as a prioritization canvas and a hypothesis backlog. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 60-90 min | Halber Tag pro Domain Slice | 60-90 min | 1-5 Tage |
Participantsdifferent | 4-12 | 1-4 | 3-8 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Prioritization Canvas, Hypothesis Backlog | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | RiskArchitectureWorkshopValidation | Knowledge graphValidationSemantic | ExperimentsPrioritizationDiscoveryHypothesis | ValidationExperimentsDemandDiscovery |