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 Lotus Blossom | ![]() Innovation Crazy 8s |
|---|---|---|---|
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 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. | With only a few minutes available and a still-fuzzy solution search, the method forces a wide range of variants. It produces fast sketches before the first idea can settle in, making different directions directly comparable and open to further development. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 8-15 min |
Participantsdifferent | 3-20 Reviewer | 3-10 | 1-10 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Lotus Diagram, Idea Themes, Shortlist | Sketch Set, Idea Shortlist, Direction Options |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingSketchingSpeedDivergenceDesign sprint |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






