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 Rich Picture |  Agile Example Mapping |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-90 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-6 | 2-10 | 3-7 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Rich Picture, Problem Framing Notes | Example Map, Acceptance Criteria, Open Questions | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Systems thinkingSoft systemsFramingVisualization | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingFramingStakeholders |