View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Design Design Studio | ![]() Decision Making RAPID | ![]() Architecture Request for Comments | ![]() Innovation Design Charrette |
|---|---|---|---|---|
Purposedifferent | 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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | Halber Tag bis mehrere Tage |
Participantsdifferent | 3-8 | 3-12 | 3-20 Reviewer | 10-50 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Sketches, Concept Directions, Design Decisions | RAPID Role Map, Recommendation, Decision Log | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | SketchingCollaborationIdeation | DecisionRolesGovernance | ArchitectureDecisionAsyncGovernance | BrainstormingWorkshopCollaborationIdeation |



