View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Team Design Team Cognitive Load Assessment | ![]() Systems Thinking Evaporating Cloud | ![]() Systems Thinking Leverage Points | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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 | High | Low |
Timedifferent | 60-90 min | 60-120 min | Half day | 45-90 min |
Participantsdifferent | 3-12 | 2-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Leverage Map, Action Strategy | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | TeamComplexityImprovementDiagnosis | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingChangeStrategy | ChangeDecisionStrategy |



