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 Request for Comments |  Innovation Brainstorming |  Decision Making RAPID |  Innovation Design Charrette |
|---|---|---|---|---|
Purposedifferent | 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. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 45-90 min | Halber Tag bis mehrere Tage |
Participantsdifferent | 3-20 Reviewer | 4-12 | 3-12 | 10-50 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Idea pool, Theme clusters, Shortlist | RAPID Role Map, Recommendation, Decision Log | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationCreativityWorkshopDivergence | DecisionRolesGovernance | BrainstormingWorkshopCollaborationIdeation |