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 RecordARID (Active Reviews for Intermediate Designs)RunbookIncident Command
| Criterion |  Architecture Architecture Decision Record |  Architecture ARID (Active Reviews for Intermediate Designs) |  Operations Runbook |  DevOps Incident Command |
|---|---|---|---|---|
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. | 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. | 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. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 2–4 h review as a planning range; preparation and evaluation additional | 20-60 min | As needed |
Participantsdifferent | 1-3 | Designers, developers as users, and facilitation | 1-4 | 4-15 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Runbook, Checklist, Escalation Path | Incident Log, Action Tracker, Stakeholder Updates |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureEngineeringFeedbackValidationTasks | OperationsReliabilityDocumentation | IncidentOperationsReliability |