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 Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
20–45 min90-180 min45-90 min30 min Setup, dann laufend
Participantsdifferent
Small cross-functional group4-123-121-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshopWorkshopAsync
Outputdifferent
Risk list, Mitigation plan, Assumption logDecision Rights Matrix, AgreementExpectation Map, Alignment Notes, AgreementsRAID Log, Status Report Source
Tagsno overlap
RiskDecisionFailurePlanning
DecisionGovernanceAlignmentResponsibility
AlignmentStakeholdersTeam
RiskTrackingStakeholdersGovernance
Add more methods