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 Example Mapping |  Systems Thinking Current Reality Tree |  Agile Specification by Example |  Systems Thinking Causal Loop Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | 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 Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 30-60 min | 2-6 h | 60-90 min pro Feature | 1-3 h |
Participantsdifferent | 3-7 | 3-8 | 3-6 | 2-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Current Reality Tree, Core Problems, Intervention Ideas | Example Table, Acceptance Tests | Causal Loop Diagram, Feedback Notes, Leverage Points |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingRoot causeConstraintsCausality | AgileRequirementsExamplesBehavior-Driven Development | FeedbackSystems thinkingCausalityDynamics |