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.

Selected:ROAM BoardRAID LogAssumption MappingA/B Testing
Criterion
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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.
Complexitydifferent
LowLowMediumHigh
Timedifferent
20-40 min initial, dann laufend30 min Setup, dann laufend45-60 min1-4 Wochen
Participantsdifferent
3-151-3 maintaining, briefing for everyone2-81-6
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
ROAM Board, Owner ListRAID Log, Status Report SourceAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods