View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Shape-First Modeling |  Architecture Architecture Decision Record |  Product Discovery Assumption Mapping |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | Halber Tag pro Domain Slice | 15-45 min | 45-60 min | 60-90 min |
Participantsdifferent | 1-4 | 1-3 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | Knowledge graphValidationSemantic | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation | RiskArchitectureWorkshopValidation |