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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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
As needed45-90 min30-90 min10-20 min daily
Participantsdifferent
4-152-82-81
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesAssumption List, Critical Assumptions, Learning PlanConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
IncidentOperationsReliability
AssumptionsRiskDecisionDiscovery
ConstraintsDecisionPlanningOptions
PlanningTime managementProductivityOperations
Add more methods