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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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
LowLowLowMedium
Timedifferent
30 min Setup, dann laufend20-40 min initial, dann laufend15-45 min1-2 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-151-34-12
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop
Outputdifferent
RAID Log, Status Report SourceROAM Board, Owner ListADR File, Decision Log, RationaleAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
ArchitectureRationaleDocumentationGovernance
AlignmentStakeholdersStrategyFacilitation
Add more methods