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 Specification by Example |  Systems Thinking CATWOE Analysis |  Product Discovery Context Canvas |  Systems Thinking Rich Picture |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 45-90 min | 45-90 min | 30-90 min |
Participantsdifferent | 3-6 | 3-8 | 3-10 | 2-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Context canvas, Open questions, Shared context notes | Rich Picture, Problem Framing Notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Systems thinkingFramingStakeholders | ContextFramingRequirementsCanvas | Systems thinkingSoft systemsFramingVisualization |