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 |  Product Discovery Assumption Mapping |  Knowledge Modeling Shape-First Modeling |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 60-90 min | 45-60 min | Halber Tag pro Domain Slice | 45-90 min |
Participantsdifferent | 4-12 | 2-8 | 1-4 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption map, Test backlog, Risk ranking | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskArchitectureWorkshopValidation | AssumptionsRiskExperimentsValidation | Knowledge graphValidationSemantic | AssumptionsRiskDecisionDiscovery |