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
Rich Picture workspace showing the question, observations, and next decision.
Systems Thinking
Rich Picture
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h30-90 min30 min Setup, dann laufend20-40 min initial, dann laufend
Participantsdifferent
3-122-101-3 maintaining, briefing for everyone3-15
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRich Picture, Problem Framing NotesRAID Log, Status Report SourceROAM Board, Owner List
Tagsno overlap
KnowledgeMappingRisk
Systems thinkingSoft systemsFramingVisualization
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
Add more methods