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 Constraint Analysis.
Decision Making
Constraint Analysis
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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.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
LowHighMediumLow
Timedifferent
30-90 minHalber TagAs needed10-20 min daily
Participantsdifferent
2-85-204-151
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Constraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesSimulation Notes, Gaps List, Updated RunbooksIncident Log, Action Tracker, Stakeholder UpdatesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ConstraintsDecisionPlanningOptions
ResilienceOperationsIncident
IncidentOperationsReliability
PlanningTime managementProductivityOperations
Add more methods