View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Crazy 8s | ![]() Architecture Request for Comments | ![]() Innovation Reverse Brainstorming |
|---|---|---|---|
Purposedifferent | 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. | 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 persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 8-15 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min |
Participantsdifferent | 1-10 | 3-20 Reviewer | 3-12 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Sketch Set, Idea Shortlist, Direction Options | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | BrainstormingSketchingSpeedDivergenceDesign sprint | ArchitectureDecisionAsyncGovernance | BrainstormingIdeationCreativityRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






