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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.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
MediumMediumLowMedium
Timedifferent
1-2 h1-3 h20-40 min initial, dann laufend1-3 h
Participantsdifferent
3-123-123-153-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsKnowledge Map, Critical Knowledge Areas, Transfer PlanROAM Board, Owner ListSystem Map, Dependencies, Leverage Points
Tagsno overlap
Systems thinkingTradeoffsLeadership
KnowledgeMappingRisk
RiskAgileTrackingAlignment
Systems thinkingMappingBoundariesChange
Add more methods