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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.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.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
MediumMediumHighLow
Timedifferent
30-60 min1-3 hHalf day45-90 min
Participantsdifferent
2-63-123-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleSystem Map, Dependencies, Leverage PointsLeverage Map, Action StrategyForce Field Map, Change Levers, Risk Notes
Tagsno overlap
BacklogIterationDelivery
Systems thinkingMappingBoundariesChange
Systems thinkingChangeStrategy
ChangeDecisionStrategy
Add more methods