methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Purposedifferent
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.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 read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
HighMediumLowLow
Timedifferent
Half day60-120 min45-90 min45–75 min
Participantsdifferent
3-122-84-12Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Leverage Map, Action StrategyConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsSailboat Board, Risks, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
Systems thinkingChangeStrategy
Theory of ConstraintsAssumptionsSystems thinking
RetrospectiveTeamImprovement
RetrospectiveLearningReflectionTeam
Add more methods