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 ATAM (Architecture Tradeoff Analysis Method) |  Innovation Reverse Brainstorming |
|---|---|---|---|
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. | 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. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Low | High | Low |
Timedifferent | 30–45 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 1-10 | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureQualityRiskTradeoffsStakeholders | BrainstormingIdeationCreativityRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
