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 Evaporating Cloud |  Agile Start Stop Continue |  Systems Thinking Future Reality Tree |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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 | Medium | Low | High | Low |
Timedifferent | 60-120 min | 30-60 min | 2-4 h | 45-90 min |
Participantsdifferent | 2-8 | 3-12 | 3-8 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Start Stop Continue Board, Improvement Actions | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | RetrospectiveImprovementTeamReflection | Theory of ConstraintsSystems thinkingChange | RetrospectiveImprovementExperimentsTeam |