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 | ![]() Agile Three Amigos | ![]() Product Discovery Context Canvas |
|---|---|---|---|---|
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 45-90 min | 15-30 min | 45-90 min |
Participantsdifferent | 3-7 | 3-8 | 3 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Clarified Story, Test Examples, Open Questions | Context canvas, Open questions, Shared context notes |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingFramingStakeholders | CollaborationBehavior-Driven DevelopmentQualityRefinement | ContextFramingRequirementsCanvas |



