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 RecordFailure Mode and Effects AnalysisStandard Work AnalysisGemba Walk
| Criterion |  Architecture Architecture Decision Record |  Operations Failure Mode and Effects Analysis |  Operations Standard Work Analysis |  Operations Gemba Walk |
|---|---|---|---|---|
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 a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 15-45 min | 2-6 h | 1-3 h | 30-120 min |
Participantsdifferent | 1-3 | 3-10 | 2-6 | 2-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | Observation Notes, Improvement Ideas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause | LeanProcessQuality | LeanObservationProcessOperations |