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 | ![]() Architecture Architecture Decision Record | ![]() Innovation Solo Brainstorming | ![]() Innovation Brainstorming |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 15-60 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 1-3 | 1 | 4-12 |
Formatdifferent | Async | Async | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Personal Idea List, Sketches or Mind Map, Pre-Read for Group Session | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | BrainstormingIdeationAsync | BrainstormingIdeationCreativityWorkshopDivergence |



