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 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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-2 h30-60 min20-40 min initial, dann laufend30 min Setup, dann laufend
Participantsdifferent
4-122-83-151-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Alignment Map, Open Issues, Decision QuestionsFishbone Diagram, Cause Categories, Investigation BacklogROAM Board, Owner ListRAID Log, Status Report Source
Tagsno overlap
AlignmentStakeholdersStrategyFacilitation
Root causeQualityOperations
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Add more methods