View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Story Points | ![]() Systems Thinking Evaporating Cloud | ![]() Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 60-120 min | 45-90 min |
Participantsdifferent | 3-9 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | EstimationAgileMeasurement | Theory of ConstraintsAssumptionsSystems thinking | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






