View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Domain Modeling Context Map | ![]() Systems Thinking Iceberg Model | ![]() Systems Thinking Wardley Mapping |
|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. | Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 30-60 min | 1-3 h |
Participantsdifferent | 2-8 | 2-10 | 2-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Wardley Map, Strategic Options, Evolution Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Systems thinkingRoot causePatterns | StrategySystems thinkingDynamics |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






