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 Leverage Points | ![]() Systems Thinking Evaporating Cloud | ![]() Agile Sailboat Retrospective | ![]() Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Half day | 60-120 min | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | 2-8 | 4-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Leverage Map, Action Strategy | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | Systems thinkingChangeStrategy | Theory of ConstraintsAssumptionsSystems thinking | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam |



