View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fishbone Diagram |  Delivery RAID Log |  Decision Making DACI |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | 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 | Low | Low | Low | High |
Timedifferent | 30-60 min | 30 min Setup, dann laufend | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 2-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | RAID Log, Status Report Source | DACI Matrix, Decision Owner, Decision Log | 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 | Root causeQualityOperations | RiskTrackingStakeholdersGovernance | DecisionRolesGovernanceAlignment | ArchitectureQualityRiskTradeoffsStakeholders |