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 |  Product Discovery Problem Interview |  Delivery RAID Log |  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. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 30-60 min je Interview | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 1-3 | 5-12 Interviews | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Problem Evidence, Risk Notes, Customer Segments | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | DiscoveryInterviewsValidation | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation |