View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Design Charrette | ![]() DevOps Blameless Postmortem | ![]() Operations Learning Review | ![]() Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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 | Medium | Medium | Low |
Timedifferent | Halber Tag bis mehrere Tage | 30-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 10-50 | 3-12 | 3-10 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Postmortem Doc, Action Items, Timeline | Learning Review Notes, System Factors, Improvement Actions | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | BrainstormingWorkshopCollaborationIdeation | Site Reliability EngineeringIncidentLearningReliability | LearningRetrospectiveIncidentOperations | BrainstormingIdeationCreativityDivergenceWorkshop |



