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 Specification by Example |  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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Medium | Medium |
Timedifferent | 45-90 min | 45-90 min | 60-90 min pro Feature | 60-120 min |
Participantsdifferent | 3-8 | 3-10 | 3-6 | 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 Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Systems thinkingFramingStakeholders | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas |