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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge 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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
20-40 min initial, dann laufend30 min Setup, dann laufend1-2 h1-3 h
Participantsdifferent
3-151-3 maintaining, briefing for everyone1-83-12
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
ROAM Board, Owner ListRAID Log, Status Report SourceConcept Map, Relationship Labels, Knowledge GapsKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
KnowledgeConceptsMappingSensemaking
KnowledgeMappingRisk
Add more methods