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 Specification by Example |  Systems Thinking Iceberg Model |  Agile Example Mapping |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-60 min | 30-60 min | 2-4 h |
Participantsdifferent | 3-6 | 2-10 | 3-7 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Example Map, Acceptance Criteria, Open Questions | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Systems thinkingRoot causePatterns | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causePatternsIncidentSystemic |