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 PDCA Cycle |  Delivery RAID Log |  Product Discovery Smoke Test |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | 1 h bis mehrere Wochen | 30 min Setup, dann laufend | 1-5 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-8 | 1-3 maintaining, briefing for everyone | Nutzertraffic | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | RAID Log, Status Report Source | Interest Metrics, Conversion Signal, Learning Note | 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 | Continuous improvementLeanExperiments | RiskTrackingStakeholdersGovernance | ValidationExperimentsDemandGrowth | ArchitectureQualityRiskTradeoffsStakeholders |