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
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowLowLowMedium
Timedifferent
30 min Setup, dann laufend20-40 min initial, dann laufend1-5 Tage45-60 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-15Nutzertraffic2-8
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceROAM Board, Owner ListInterest Metrics, Conversion Signal, Learning NoteAssumption map, Test backlog, Risk ranking
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
ValidationExperimentsDemandGrowth
AssumptionsRiskExperimentsValidation
Add more methods