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 Architecture Decision Record |  Architecture Request for Comments |  Innovation Brainstorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 45-90 min |
Participantsdifferent | 1-3 | 3-20 Reviewer | 4-12 | 3-10 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Idea pool, Theme clusters, Shortlist | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityDivergenceWorkshop |