View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Problem Interview |  Delivery RAID Log |  Architecture Risk Storming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 30-60 min je Interview | 30 min Setup, dann laufend | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 5-12 Interviews | 1-3 maintaining, briefing for everyone | 4-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | RAID Log, Status Report Source | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | DiscoveryInterviewsValidation | RiskTrackingStakeholdersGovernance | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskTradeoffsStakeholders |