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 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
Paper illustration for DACI
Decision Making
DACI
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 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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min20-40 min initial, dann laufend30 min Setup, dann laufend30-60 min
Participantsdifferent
3-123-151-3 maintaining, briefing for everyone2-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Expectation Map, Alignment Notes, AgreementsROAM Board, Owner ListRAID Log, Status Report SourceDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
AlignmentStakeholdersTeam
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
DecisionRolesGovernanceAlignment
Add more methods