View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  DevOps Blameless Postmortem |  Innovation Design Charrette |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | 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. | 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 | Low | Medium | Medium | Low |
Timedifferent | 60-90 min | 30-90 min | Halber Tag bis mehrere Tage | 45-90 min |
Participantsdifferent | 4-12 | 3-12 | 10-50 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Postmortem Doc, Action Items, Timeline | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | RiskArchitectureWorkshopValidation | Site Reliability EngineeringIncidentLearningReliability | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationCreativityDivergenceWorkshop |