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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
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 a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
LowMediumLowLow
Timedifferent
20-40 min initial, dann laufend1-3 h30 min Setup, dann laufend20-45 min
Participantsdifferent
3-153-101-3 maintaining, briefing for everyone3-12
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListProcess Map, Handoff List, Improvement BacklogRAID Log, Status Report SourceLessons learned, Action items, Event summary
Tagsno overlap
RiskAgileTrackingAlignment
ProcessOperationsImprovement
RiskTrackingStakeholdersGovernance
LearningOperationsImprovement
Add more methods