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 Systems Mapping | ![]() Systems Thinking Evaporating Cloud | ![]() Growth Funnel Analysis | ![]() Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 60-120 min | 1-3 h | 1-4 Wochen |
Participantsdifferent | 3-12 | 2-8 | 1-5 | 1-6 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | System Map, Dependencies, Leverage Points | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Funnel report, Drop-off analysis, Optimization hypotheses | Experiment results, Decision log, Learning summary |
Tagsno overlap | Systems thinkingMappingBoundariesChange | Theory of ConstraintsAssumptionsSystems thinking | AnalyticsConversionGrowth | ExperimentsGrowthAnalyticsValidation |



