View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Three Horizons |  DevOps Incident Command |  Operations Learning Review |  DevOps Blameless Postmortem |
|---|---|---|---|---|
Purposedifferent | Three Horizons helps clarify strategic options across different timeframes. It compares strengths, risks, market logic, and investment choices, and captures the result as a horizon map, portfolio view, and initiatives per horizon. | 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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Halbtags-Workshop, dann iterativ | As needed | 1-3 h | 30-90 min |
Participantsdifferent | 3-12 | 4-15 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Horizon map, Portfolio view, Initiatives per horizon, Resource plan | Incident Log, Action Tracker, Stakeholder Updates | Learning Review Notes, System Factors, Improvement Actions | Postmortem Doc, Action Items, Timeline |
Tagsno overlap | StrategyInnovationPortfolioForesight | IncidentOperationsReliability | LearningRetrospectiveIncidentOperations | Site Reliability EngineeringIncidentLearningReliability |