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 Three-Point Estimation.
Decision Making
Three-Point Estimation
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Purposedifferent
A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.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.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
10-30 min je Item1-3 hAs neededHalber Tag
Participantsdifferent
1-83-104-155-20
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Three-Point Estimate, Risk Range, Assumption NotesProcess Map, Handoff List, Improvement BacklogIncident Log, Action Tracker, Stakeholder UpdatesSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
EstimationUncertaintyForecasting
ProcessOperationsImprovement
IncidentOperationsReliability
ResilienceOperationsIncident
Add more methods