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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.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.
Complexitydifferent
MediumLowHighMedium
Timedifferent
1-3 h20-40 min initial, dann laufendHalf day1-3 h
Participantsdifferent
3-123-153-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanROAM Board, Owner ListLeverage Map, Action StrategySystem Map, Dependencies, Leverage Points
Tagsno overlap
KnowledgeMappingRisk
RiskAgileTrackingAlignment
Systems thinkingChangeStrategy
Systems thinkingMappingBoundariesChange
Add more methods