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 Systems Mapping |  Agile Example Mapping |  Systems Thinking Evaporating Cloud |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 30-60 min | 60-120 min | 60-90 min pro Feature |
Participantsdifferent | 3-12 | 3-7 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | System Map, Dependencies, Leverage Points | Example Map, Acceptance Criteria, Open Questions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Example Table, Acceptance Tests |
Tagsno overlap | Systems thinkingMappingBoundariesChange | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Theory of ConstraintsAssumptionsSystems thinking | AgileRequirementsExamplesBehavior-Driven Development |