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 |  Product Discovery Context Canvas |  Agile Example Mapping |  Architecture Architecture Communication 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. | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 45-90 min | 45-90 min | 30-60 min | 60-120 min |
Participantsdifferent | 3-8 | 3-10 | 3-7 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Context canvas, Open questions, Shared context notes | Example Map, Acceptance Criteria, Open Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Systems thinkingFramingStakeholders | ContextFramingRequirementsCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureCommunicationStakeholdersCanvas |