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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Communication Plan
Delivery
Communication Plan
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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 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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.
Complexitydifferent
LowLowHighLow
Timedifferent
20–45 min30 min Setup, dann laufend1-4 Wochen45-90 min
Participantsdifferent
Small cross-functional group1-3 maintaining, briefing for everyone1-62-6
Formatdifferent
WorkshopAsyncAsyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logRAID Log, Status Report SourceExperiment results, Decision log, Learning summaryCommunication Plan, Channel Matrix, Message Cadence
Tagsno overlap
RiskDecisionFailurePlanning
RiskTrackingStakeholdersGovernance
ExperimentsGrowthAnalyticsValidation
CommunicationStakeholdersDeliveryPlanning
Add more methods