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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Fault Isolation.
Engineering
Fault Isolation
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.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.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30 min Setup, dann laufend30-180 min20-40 min initial, dann laufend1-2 h
Participantsdifferent
1-3 maintaining, briefing for everyone1-63-154-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceFault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaROAM Board, Owner ListAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RiskTrackingStakeholdersGovernance
TroubleshootingDiagnosisEngineering
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods