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 Soft Systems Methodology | ![]() Agile Example Mapping | ![]() Product Discovery Context Canvas | ![]() Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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. | 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 | High | Low | Low | Medium |
Timedifferent | 0.5-3 Tage | 30-60 min | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 5-15 | 3-7 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Example Map, Acceptance Criteria, Open Questions | Context canvas, Open questions, Shared context notes | Example Table, Acceptance Tests |
Tagsno overlap | Soft systemsComplexitySensemakingSystems thinking | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development |



