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 |  Delivery RAID Log |  Architecture Risk Storming |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Halber Tag pro Domain Slice | 30 min Setup, dann laufend | 60-90 min | 60-120 min |
Participantsdifferent | 1-4 | 1-3 maintaining, briefing for everyone | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Knowledge graphValidationSemantic | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | ArchitectureCommunicationStakeholdersCanvas |