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 Architecture Decision Record | ![]() Operations Scatter Diagram | ![]() Delivery RAID Log |
|---|---|---|---|
Purposedifferent | 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 the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 30-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | 1-4 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Scatter Plot, Korrelationsnotiz, Hypothesenliste | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeQualityVisualization | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






