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 | ![]() Innovation Reverse Brainstorming | ![]() Architecture Risk Storming |
|---|---|---|---|
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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitysame | Low | Low | Low |
Timedifferent | 15-45 min | 30-60 min | 60-90 min |
Participantsdifferent | 1-3 | 3-12 | 4-12 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Reverse Ideas, Risk Themes, Solution Ideas | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | BrainstormingIdeationCreativityRisk | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






