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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min20-40 min initial, dann laufend45-90 min30 min Setup, dann laufend
Participantsdifferent
3-123-152-81-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Expectation Map, Alignment Notes, AgreementsROAM Board, Owner ListAssumption List, Critical Assumptions, Learning PlanRAID Log, Status Report Source
Tagsno overlap
AlignmentStakeholdersTeam
RiskAgileTrackingAlignment
AssumptionsRiskDecisionDiscovery
RiskTrackingStakeholdersGovernance
Add more methods