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 Contradiction Analysis |
|---|---|---|---|
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 system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 60-120 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Contradiction Statement, Inventive Principles, Solution Concepts | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | InnovationProblem solvingContradictionsCreativity | ContradictionsInnovationProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
