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 |  Operations Process Mapping |  Operations After-Action Review |  Operations Learning Review |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | 1-3 h | 20-45 min | 1-3 h |
Participantsdifferent | 2-8 | 3-10 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Process Map, Handoff List, Improvement Backlog | Lessons learned, Action items, Event summary | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ProcessOperationsImprovement | LearningOperationsImprovement | LearningRetrospectiveIncidentOperations |