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 Design Charrette |  Innovation Solo Brainstorming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | For an individual thinking problem with no counterpart immediately available, the method creates a protected space for one's own approaches. It prevents outside opinions from narrowing thinking too early. This lets ideas mature before they go into a group format. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Halber Tag bis mehrere Tage | 15-60 min | 15-45 min |
Participantsdifferent | 3-20 Reviewer | 10-50 | 1 | 1-3 |
Formatdifferent | Async | Workshop | Async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Personal Idea List, Sketches or Mind Map, Pre-Read for Group Session | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationAsync | ArchitectureRationaleDocumentationGovernance |