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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
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.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 many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
30-90 minAs needed1-2 h Setup, laufend30-90 min
Participantsdifferent
2-84-1513-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Constraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesIncident Log, Action Tracker, Stakeholder UpdatesAction Lists, Project List, Review RoutinePostmortem Doc, Action Items, Timeline
Tagsno overlap
ConstraintsDecisionPlanningOptions
IncidentOperationsReliability
ProductivityPlanningTasksExecution
Site Reliability EngineeringIncidentLearningReliability
Add more methods