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 for Constraint Analysis.
Decision Making
Constraint Analysis
Paper illustration for Learning Review.
Operations
Learning Review
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.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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
MediumLowMediumLow
Timedifferent
As needed30-90 min1-3 h10-20 min daily
Participantsdifferent
4-152-83-101
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesLearning Review Notes, System Factors, Improvement ActionsDaily Plan, Time Estimates, Review Notes
Tagsno overlap
IncidentOperationsReliability
ConstraintsDecisionPlanningOptions
LearningRetrospectiveIncidentOperations
PlanningTime managementProductivityOperations
Add more methods