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 ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |  Innovation Lotus Blossom |
|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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 | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min | 45-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 4-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Annotated Diagram, Prioritized Risk List, Action Backlog | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
