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 Accountability Ladder
Operations
Accountability Ladder
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Expectation Mapping.
Facilitation
Expectation 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.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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 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.
Complexitysame
LowLowLowLow
Timedifferent
20-40 min initial, dann laufend20-45 min30 min Setup, dann laufend45-90 min
Participantsdifferent
3-151-81-3 maintaining, briefing for everyone3-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
ROAM Board, Owner ListOwnership Reflection, Action Commitment, Coaching NotesRAID Log, Status Report SourceExpectation Map, Alignment Notes, Agreements
Tagsno overlap
RiskAgileTrackingAlignment
ResponsibilityLeadershipTeam
RiskTrackingStakeholdersGovernance
AlignmentStakeholdersTeam
Add more methods