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 Starbursting |  Innovation Reverse Brainstorming |  Innovation Brainstorming |
|---|---|---|---|---|
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. | Helps clarify ideas, open questions, and testable next steps in concrete terms. It opens the thinking space, collects ideas, and leads to testable options. The result is captured as a star-shaped question map, question list, and assumption list. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-90 min | 30-60 min | 30-60 min | 30-60 min |
Participantsdifferent | 3-12 | 3-10 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Star-Shaped Question Map, Question List, Assumption List | Reverse Ideas, Risk Themes, Solution Ideas | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | BrainstormingIdeationWorkshopDiscovery | BrainstormingIdeationCreativityRisk | BrainstormingIdeationCreativityWorkshopDivergence |