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 Future Reality Tree | ![]() Agile Start Stop Continue | ![]() Agile Starfish Retrospective | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|---|
Purposedifferent | 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 2-4 h | 30-60 min | 45-90 min | 60-120 min |
Participantsdifferent | 3-8 | 3-12 | 4-12 | 2-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | Theory of ConstraintsSystems thinkingChange | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | Theory of ConstraintsAssumptionsSystems thinking |



