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 Acceptance Criteria Workshop |
|---|---|---|---|---|
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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 30-60 min | 60-120 min | 20-40 min pro Story |
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 | Acceptance Criteria, Story Update |
Tagsno overlap | Systems thinkingMappingBoundariesChange | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Theory of ConstraintsAssumptionsSystems thinking | AgileRequirementsRefinementBehavior-Driven Development |