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 Futures Wheel |  Systems Thinking Causal Loop Diagram |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-120 min | 1-3 h | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 3-10 | 2-8 | 3-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Futures Wheel, Consequence Chains, Strategic Signals | Causal Loop Diagram, Feedback Notes, Leverage Points | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ForesightSystems thinkingSignals | FeedbackSystems thinkingCausalityDynamics | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |