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 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. | 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 |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 1-4 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
