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 Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Learning Review.
Operations
Learning Review
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
90-180 min30-90 min1-3 hAs needed
Participantsdifferent
4-123-123-104-15
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Planning Levels Map, Cadence Model, Planning Artifact InventoryPostmortem Doc, Action Items, TimelineLearning Review Notes, System Factors, Improvement ActionsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
CadenceGovernanceExecution
Site Reliability EngineeringIncidentLearningReliability
LearningRetrospectiveIncidentOperations
IncidentOperationsReliability
Add more methods