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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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 early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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
LowLowMediumLow
Timedifferent
30-90 min20–45 minAs needed10-20 min daily
Participantsdifferent
2-8Small cross-functional group4-151
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Constraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesRisk list, Mitigation plan, Assumption logIncident Log, Action Tracker, Stakeholder UpdatesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
ConstraintsDecisionPlanningOptions
RiskDecisionFailurePlanning
IncidentOperationsReliability
PlanningTime managementProductivityOperations
Add more methods