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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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 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
20-40 min initial, dann laufend45-90 min30 min Setup, dann laufend1-2 h
Participantsdifferent
3-153-121-3 maintaining, briefing for everyone4-12
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
ROAM Board, Owner ListExpectation Map, Alignment Notes, AgreementsRAID Log, Status Report SourceAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RiskAgileTrackingAlignment
AlignmentStakeholdersTeam
RiskTrackingStakeholdersGovernance
AlignmentStakeholdersStrategyFacilitation
Add more methods