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 |  UX Research User Interviews |  Operations 5 Whys |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 30–60 min per interview | 15-30 min | 45-90 min |
Participantsdifferent | 1-3 | 1 participant per interview | 2-6 | 2-5 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Themes, Insight Summary | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QualitativeResearchCustomerDiscovery | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations |