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 Standard Work Analysis |  Product Strategy ICE Scoring |  Product Strategy RICE Scoring |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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 | Medium | High |
Timedifferent | 1-3 h | 30-60 min | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-6 | 2-8 | 2-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | ICE Table, Top Idea List | RICE Scores, Ranked List, Assumption 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 | LeanProcessQuality | PrioritizationScoringGrowthDecision | PrioritizationScoringRoadmapTradeoffs | ArchitectureQualityRiskTradeoffsStakeholders |