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 of Working Backwards with its method-specific working model.
Product Discovery
Working Backwards
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Purposedifferent
When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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 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.
Complexitydifferent
MediumHighLowLow
Timedifferent
4-8 h, mehrere Iterationen2-6 h30 min Setup, dann laufend20-40 min initial, dann laufend
Participantsdifferent
2-63-81-3 maintaining, briefing for everyone3-15
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Future Press Release, FAQ, Vision StatementFault Tree, Critical Paths, Cause Hypotheses, Control ActionsRAID Log, Status Report SourceROAM Board, Owner List
Tagsno overlap
VisionNarrativeAlignment
RiskRoot causeSafety
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
Add more methods