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 Blameless Postmortem |  Business Strategy Blue Ocean Strategy Canvas |  DevOps Incident Timeline Analysis |
|---|---|---|---|---|
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. | 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. | The Blue Ocean Strategy Canvas shows how an offering is positioned relative to the market. Differentiation thereby becomes tangible in value factors instead of merely being claimed. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Halbtags-Workshop, dann iterativ | 30-90 min | 2-4 h | 60-180 min |
Participantsdifferent | 3-12 | 3-12 | 3-10 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Horizon map, Portfolio view, Initiatives per horizon, Resource plan | Postmortem Doc, Action Items, Timeline | Strategy Canvas, Value Curve, ERRC Actions | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions |
Tagsno overlap | StrategyInnovationPortfolioForesight | Site Reliability EngineeringIncidentLearningReliability | StrategyPositioningInnovationValue | IncidentTimelineSite Reliability Engineering |