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 Design Charrette |  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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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 | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Halber Tag bis mehrere Tage | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 10-50 | 3-12 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationCreativityRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
