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 for NoEstimates.
Agile
NoEstimates
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Purposedifferent
When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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.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.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
laufend1-3 h45-90 minHalf day
Participantsdifferent
2-123-123-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesSystem Map, Dependencies, Leverage PointsForce Field Map, Change Levers, Risk NotesLeverage Map, Action Strategy
Tagsno overlap
EstimationForecastingFlow
Systems thinkingMappingBoundariesChange
ChangeDecisionStrategy
Systems thinkingChangeStrategy
Add more methods