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 Polarity Mapping | ![]() Architecture Architecture Decision Record | ![]() Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30–45 min | 1-2 h | 15-45 min | 45-90 min |
Participantsdifferent | 1-10 | 3-12 | 1-3 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Polarity Map, Warning Signs, Balance Actions | ADR File, Decision Log, Rationale | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | FramingOpportunityIdeationQuestions | Systems thinkingTradeoffsLeadership | ArchitectureRationaleDocumentationGovernance | Systems thinkingFramingStakeholders |



