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 | ![]() Systems Thinking Rich Picture |
|---|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 30-60 min | 30-90 min |
Participantsdifferent | 3-8 | 3-10 | 3-7 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Context canvas, Open questions, Shared context notes | Example Map, Acceptance Criteria, Open Questions | Rich Picture, Problem Framing Notes |
Tagsno overlap | Systems thinkingFramingStakeholders | ContextFramingRequirementsCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingSoft systemsFramingVisualization |



