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 Starbursting | ![]() Innovation Design Charrette |
|---|---|---|---|
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 ideas, open questions, and testable next steps in concrete terms. It opens the thinking space, collects ideas, and leads to testable options. The result is captured as a star-shaped question map, question list, and assumption list. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | Halber Tag bis mehrere Tage |
Participantsdifferent | 3-20 Reviewer | 3-10 | 10-50 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Star-Shaped Question Map, Question List, Assumption List | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationWorkshopDiscovery | BrainstormingWorkshopCollaborationIdeation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






