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 |  Systems Thinking CATWOE Analysis |  Operations Root Cause Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 30–45 min | 45-90 min | 1-4 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-10 | 3-8 | 3-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | FramingOpportunityIdeationQuestions | Systems thinkingFramingStakeholders | Root causeProblem solvingQualityIncident | ArchitectureQualityRiskTradeoffsStakeholders |