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) |  UX Design Design Studio |  Innovation Starbursting |  Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 h | 30-60 min | 60-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-8 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Sketches, Concept Directions, Design Decisions | Star-Shaped Question Map, Question List, Assumption List | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | SketchingCollaborationIdeation | BrainstormingIdeationWorkshopDiscovery | RiskArchitectureWorkshopValidation |