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 Iceberg Model | ![]() Systems Thinking Causal Loop Diagram | ![]() Agile Specification by Example |
|---|---|---|---|---|
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. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 30-60 min | 30-60 min | 1-3 h | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 2-10 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Causal Loop Diagram, Feedback Notes, Leverage Points | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingRoot causePatterns | FeedbackSystems thinkingCausalityDynamics | AgileRequirementsExamplesBehavior-Driven Development |



