View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Visual Management |  Operations Kepner-Tregoe |  Architecture Architecture Decision Record |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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 a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | Ongoing | 2-8 h | 15-45 min | 15-30 min |
Participantsdifferent | 1-20 | 2-8 | 1-3 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Visual Board, Status Indicators, Exception Cues | Problem Analysis, Decision Analysis, Risk Plan | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures |
Tagsno overlap | SignalsOperationsVisual management | Problem solvingRoot causeDecisionOperations | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving |