View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  Systems Thinking CATWOE Analysis |  Product Discovery Context Canvas |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 30-60 min | 45-90 min | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 3-8 | 3-10 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Context canvas, Open questions, Shared context notes | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingFramingStakeholders | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development |