View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Software Architecture Canvas |  Systems Thinking Rich Picture |  Architecture Architecture Communication Canvas |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Medium |
Timedifferent | 1-2 h | 30-90 min | 60-120 min | 45-90 min |
Participantsdifferent | 3-10 | 2-10 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | Rich Picture, Problem Framing Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | Systems thinkingSoft systemsFramingVisualization | ArchitectureCommunicationStakeholdersCanvas | Systems thinkingFramingStakeholders |