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) |  Systems Thinking Polarity Mapping |
|---|---|---|---|
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. | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 30–45 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
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 | Polarity Map, Warning Signs, Balance Actions |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureQualityRiskTradeoffsStakeholders | Systems thinkingTradeoffsLeadership |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
