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 Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
LowLowLowHigh
Timedifferent
20-40 min initial, dann laufend30-60 min30 min Setup, dann laufend2-6 h
Participantsdifferent
3-151-61-3 maintaining, briefing for everyone3-10
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
ROAM Board, Owner ListPareto Chart, Top Causes, Focus ListRAID Log, Status Report SourceFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
RiskAgileTrackingAlignment
PrioritizationQualityFocusRoot cause
RiskTrackingStakeholdersGovernance
RiskQualityOperationsRoot cause
Add more methods