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 Brainstorming |  Architecture Risk Storming |  Innovation Reverse 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. | 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. | 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. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 60-90 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 4-12 | 4-12 | 3-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Idea pool, Theme clusters, Shortlist | Annotated Diagram, Prioritized Risk List, Action Backlog | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationCreativityWorkshopDivergence | RiskArchitectureWorkshopValidation | BrainstormingIdeationCreativityRisk |