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 Runbook | ![]() Product Discovery Smoke Test |
|---|---|---|---|
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. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 20-60 min | 1-5 Tage |
Participantsdifferent | 1-3 | 1-4 | Nutzertraffic |
Formatsame | Async | Async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Runbook, Checklist, Escalation Path | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OperationsReliabilityDocumentation | ValidationExperimentsDemandGrowth |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






