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 Rolestorming |  Innovation Lotus Blossom |
|---|---|---|---|
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. | When a search for ideas stalls, switching roles helps people step outside their own perspective and activate new logics of action. The method reduces habit because contributions arise from a different stance. This brings unfamiliar, often fitting solution approaches into play. | 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 | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 45-90 min |
Participantsdifferent | 3-20 Reviewer | 3-12 | 3-10 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Rollenkarten, Ideenpool pro Rolle, Konsolidierte Shortlist | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationCreativity | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
