View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Blameless Postmortem |  Innovation SCAMPER |  Operations Family Tree Analysis |
|---|---|---|---|
Purposedifferent | 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. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-90 min | 30-60 min | 2-4 h |
Participantsdifferent | 3-12 | 2-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | SCAMPER Idea List, Concept Shortlist, Variation Notes | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | BrainstormingIdeationCreativityReframingInnovation | Root causePatternsIncidentSystemic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
