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 Example Mapping |  Agile Specification by Example |
|---|---|---|---|---|
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 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 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 | Medium | Low | Medium |
Timedifferent | 60-120 min | 1-3 h | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 3-10 | 2-8 | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Futures Wheel, Consequence Chains, Strategic Signals | Causal Loop Diagram, Feedback Notes, Leverage Points | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | ForesightSystems thinkingSignals | FeedbackSystems thinkingCausalityDynamics | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |