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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.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.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.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.
Complexitydifferent
LowHighLowLow
Timedifferent
OngoingHalber Tag20–45 min30-90 min
Participantsdifferent
1-205-20Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Visual Board, Status Indicators, Exception CuesSimulation Notes, Gaps List, Updated RunbooksRisk list, Mitigation plan, Assumption logConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
SignalsOperationsVisual management
ResilienceOperationsIncident
RiskDecisionFailurePlanning
ConstraintsDecisionPlanningOptions
Add more methods