View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking CATWOE Analysis |  Innovation How Might We |  Architecture Software Architecture Canvas |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 45-90 min | 30–45 min | 1-2 h | 1-2 h |
Participantsdifferent | 3-8 | 1-10 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | HMW Questions, Challenge Framing, Idea Prompts | Architecture Canvas, Goals, Constraints, Quality Attributes | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | Systems thinkingFramingStakeholders | FramingOpportunityIdeationQuestions | CanvasArchitectureAlignmentWorkshop | AlignmentArchitectureCanvas |