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 Game Day |  Architecture Risk Storming |  Innovation Starbursting |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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. | 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. | 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 | High | Low | Low | Low |
Timedifferent | Halber Tag | 60-90 min | 30-60 min | 45-90 min |
Participantsdifferent | 5-20 | 4-12 | 3-10 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Annotated Diagram, Prioritized Risk List, Action Backlog | Star-Shaped Question Map, Question List, Assumption List | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ResilienceOperationsIncident | RiskArchitectureWorkshopValidation | BrainstormingIdeationWorkshopDiscovery | BrainstormingIdeationCreativityDivergenceWorkshop |