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 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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowLowHighMedium
Timedifferent
30 min Setup, dann laufend20-40 min initial, dann laufend1-4 Wochen45-60 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-151-62-8
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceROAM Board, Owner ListExperiment results, Decision log, Learning summaryAssumption map, Test backlog, Risk ranking
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
ExperimentsGrowthAnalyticsValidation
AssumptionsRiskExperimentsValidation
Add more methods