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 a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
MediumLowLowMedium
Timedifferent
45-90 min30 min Setup, dann laufend15-45 min1-2 h
Participantsdifferent
3-81-3 maintaining, briefing for everyone1-34-12
Formatdifferent
WorkshopAsyncAsyncWorkshop
Outputdifferent
Impact Map, Outcome Hypotheses, Delivery OptionsRAID Log, Status Report SourceADR File, Decision Log, RationaleAlignment Map, Open Issues, Decision Questions
Tagsno overlap
OutcomesStrategyBehaviorPlanning
RiskTrackingStakeholdersGovernance
ArchitectureRationaleDocumentationGovernance
AlignmentStakeholdersStrategyFacilitation
Add more methods