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 Scrum | ![]() Systems Thinking System Archetypes | ![]() Systems Thinking Iceberg Model |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | System Archetypes make recurring dynamics such as Fixes that Fail or Limits to Growth recognizable. It draws relationships, patterns, and feedback loops. The result is captured as an archetype assignment and lever list. | 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. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 90-180 min | 30-60 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-10 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Archetype Mapping, Lever List | Iceberg Worksheet, Pattern Notes, Intervention Ideas |
Tagsno overlap | AgileIterationCadence | Systems thinkingPatternsDiagnosisDynamics | Systems thinkingRoot causePatterns |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






