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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for ALPEN Method
Operations
ALPEN Method
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.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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
MediumLowLowLow
Timedifferent
45-90 min15-45 min30-60 min10-20 min daily
Participantsdifferent
3-81-32-81
Formatdifferent
WorkshopAsyncWorkshopAsync
Outputdifferent
Impact Map, Outcome Hypotheses, Delivery OptionsADR File, Decision Log, RationaleFishbone Diagram, Cause Categories, Investigation BacklogDaily Plan, Time Estimates, Review Notes
Tagsno overlap
OutcomesStrategyBehaviorPlanning
ArchitectureRationaleDocumentationGovernance
Root causeQualityOperations
PlanningTime managementProductivityOperations
Add more methods