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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration of Shape Up with its method-specific working model.
Delivery
Shape Up
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts.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
MediumMediumLow
Timedifferent
30-240 min6 Wochen Cycle + 2 Wochen Cool-Down10-20 min daily
Participantsdifferent
1-62-4 pro Pitch1
Formatdifferent
Workshop + asyncWorkshop + asyncAsync
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryPitches, Bet-table decisions, Hill charts, Cooldown outcomesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
PlanningDeliveryAutonomy
PlanningTime managementProductivityOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Paper illustration for Communication Plan
Delivery
Communication Plan
Paper illustration for Fault Isolation.
Engineering
Fault Isolation
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done