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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Purposedifferent
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.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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.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
LowMediumHighMedium
Timedifferent
20-40 min initial, dann laufend1-3 h2-4 h1-3 h
Participantsdifferent
3-153-123-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
ROAM Board, Owner ListKnowledge Map, Critical Knowledge Areas, Transfer PlanFuture Reality Tree, Negative Branches, Assumption List, Improved InjectionsSystem Map, Dependencies, Leverage Points
Tagsno overlap
RiskAgileTrackingAlignment
KnowledgeMappingRisk
Theory of ConstraintsSystems thinkingChange
Systems thinkingMappingBoundariesChange
Add more methods