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 |  UX Design Design Studio |  Innovation Lotus Blossom |  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. | When several designs need to be quickly put in relation to each other, it makes ideas visible and comparable. It encourages early variants instead of long upfront debates. | 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. | 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 | Medium | Low | Low |
Timedifferent | 30-90 min | 1-3 h | 45-90 min | 30-60 min |
Participantsdifferent | 3-12 | 3-8 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Sketches, Concept Directions, Design Decisions | Lotus Diagram, Idea Themes, Shortlist | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | SketchingCollaborationIdeation | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationCreativityWorkshopDivergence |