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 Incident Command |  Innovation Starbursting |  DevOps Blameless Postmortem |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | As needed | 30-60 min | 30-90 min | 45-90 min |
Participantsdifferent | 4-15 | 3-10 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Incident Log, Action Tracker, Stakeholder Updates | Star-Shaped Question Map, Question List, Assumption List | Postmortem Doc, Action Items, Timeline | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | IncidentOperationsReliability | BrainstormingIdeationWorkshopDiscovery | Site Reliability EngineeringIncidentLearningReliability | BrainstormingIdeationCreativityDivergenceWorkshop |