View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordRunbookSmoke TestARID (Active Reviews for Intermediate Designs)
| Criterion |  Architecture Architecture Decision Record |  Operations Runbook |  Product Discovery Smoke Test |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 20-60 min | 1-5 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-3 | 1-4 | Nutzertraffic | Designers, developers as users, and facilitation |
Formatdifferent | Async | Async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path | Interest Metrics, Conversion Signal, Learning Note | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation | ValidationExperimentsDemandGrowth | ArchitectureEngineeringFeedbackValidationTasks |