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 Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Purposedifferent
When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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-2 h30 min Setup, dann laufend30-60 min20-40 min initial, dann laufend
Participantsdifferent
4-121-3 maintaining, briefing for everyone2-83-15
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Alignment Map, Open Issues, Decision QuestionsRAID Log, Status Report SourceFishbone Diagram, Cause Categories, Investigation BacklogROAM Board, Owner List
Tagsno overlap
AlignmentStakeholdersStrategyFacilitation
RiskTrackingStakeholdersGovernance
Root causeQualityOperations
RiskAgileTrackingAlignment
Add more methods