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 Solo Brainstorming |  Architecture arc42 |  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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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-60 min | 1-2 Tage | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 1 | 1-4 | 4-12 |
Formatdifferent | Async | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Personal Idea List, Sketches or Mind Map, Pre-Read for Group Session | Architecture Document, Context View, Runtime View, Deployment View | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationAsync | ArchitectureDocumentationCommunication | BrainstormingIdeationCreativityWorkshopDivergence |