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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Bucket System.
Agile
Bucket System
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Purposedifferent
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.When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.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.When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h30-90 min45-90 min30-90 min
Participantssame
3-123-123-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
System Map, Dependencies, Leverage PointsBucketed Backlog, Relative Estimates, Split CandidatesForce Field Map, Change Levers, Risk NotesAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
Systems thinkingMappingBoundariesChange
EstimationBacklogRelative sizing
ChangeDecisionStrategy
EstimationBacklogRelative sizing
Add more methods