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 | ![]() Architecture Software Architecture Canvas | ![]() Systems Thinking Rich Picture |
|---|---|---|---|
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. | 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. | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 45-90 min | 1-2 h | 30-90 min |
Participantsdifferent | 3-8 | 3-10 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Architecture Canvas, Goals, Constraints, Quality Attributes | Rich Picture, Problem Framing Notes |
Tagsno overlap | Systems thinkingFramingStakeholders | CanvasArchitectureAlignmentWorkshop | Systems thinkingSoft systemsFramingVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






