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 |  Product Discovery Assumption Mapping |  Architecture Views and Beyond |  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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 45-60 min | 1-3 Tage | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | 2-8 | 1-4 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking | Architecture Views, Cross-view Notes, Rationale | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation | DocumentationStakeholdersArchitecture | RiskTrackingStakeholdersGovernance |