View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Property Graph Schema DesignRAID LogArchitecture Decision RecordArchitecture Communication Canvas
| Criterion | ![]() Knowledge Modeling Property Graph Schema Design | ![]() Delivery RAID Log | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. | 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. | 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. | 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 | 4-8 h initial, dann iterativ | 30 min Setup, dann laufend | 15-45 min | 60-120 min |
Participantsdifferent | 1-6 | 1-3 maintaining, briefing for everyone | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Knowledge graphModelingSemantic | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |



