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 Morphological Analysis |  Architecture Architecture Decision Record |  Innovation SCAMPER |
|---|---|---|---|---|
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 a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 15-45 min | 30-60 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | 1-3 | 2-10 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Morphological Box, Concept Combinations, Idea Shortlist | ADR File, Decision Log, Rationale | SCAMPER Idea List, Concept Shortlist, Variation Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | IdeationInnovationCreativity | ArchitectureRationaleDocumentationGovernance | BrainstormingIdeationCreativityReframingInnovation |