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 TRIZ |  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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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 | High | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Contradiction Statement, Inventive Principles, Solution Concepts | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | InnovationProblem solvingContradictionsCreativity | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
