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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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 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.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 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
LowMediumLowLow
Timedifferent
45-90 min1-2 h20-40 min initial, dann laufend30 min Setup, dann laufend
Participantsdifferent
3-124-123-151-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Expectation Map, Alignment Notes, AgreementsAlignment Map, Open Issues, Decision QuestionsROAM Board, Owner ListRAID Log, Status Report Source
Tagsno overlap
AlignmentStakeholdersTeam
AlignmentStakeholdersStrategyFacilitation
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Add more methods