View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation How Might We |  Architecture Architecture Decision Record |  Operations 5 Whys |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction. | 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. | 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 | 30–45 min | 15-45 min | 15-30 min | 45-90 min |
Participantsdifferent | 1-10 | 1-3 | 2-6 | 2-5 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations |