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 |  Delivery RAID Log |  Innovation Brainstorming |  Innovation Reverse Brainstorming |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 30 min Setup, dann laufend | 30-60 min | 30-60 min |
Participantsdifferent | 1-3 | 1-3 maintaining, briefing for everyone | 4-12 | 3-12 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Idea pool, Theme clusters, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityRisk |