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 of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for ALPEN Method
Operations
ALPEN Method
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Purposedifferent
Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.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
LowMediumLowMedium
Timedifferent
45-90 minAs needed10-20 min daily30-90 min
Participantsdifferent
2-84-1513-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanIncident Log, Action Tracker, Stakeholder UpdatesDaily Plan, Time Estimates, Review NotesPostmortem Doc, Action Items, Timeline
Tagsno overlap
AssumptionsRiskDecisionDiscovery
IncidentOperationsReliability
PlanningTime managementProductivityOperations
Site Reliability EngineeringIncidentLearningReliability
Add more methods