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 Risk Storming |  Innovation Rapid Ideation |  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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | When a decision needs to be prepared quickly, the method generates many solution-close variants in a short time. It deliberately relies on pace to undercut self-censorship and perfectionism. This quickly produces a usable field for prioritization and further work. | 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 | 60-90 min | 5-20 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 4-12 | 1-20 | 4-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Annotated Diagram, Prioritized Risk List, Action Backlog | Ideenpool, Roh-Shortlist, Cluster | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskArchitectureWorkshopValidation | BrainstormingIdeationDivergenceSpeed | BrainstormingIdeationCreativityWorkshopDivergence |