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 Strategy ICE Scoring |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Kepner-Tregoe |  Operations Change Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitydifferent | Low | High | High | Medium |
Timedifferent | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope | 2-8 h | 45-120 min |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ICE Table, Top Idea List | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Problem Analysis, Decision Analysis, Risk Plan | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | PrioritizationScoringGrowthDecision | ArchitectureChangeAnalysisComparisonQuality | Problem solvingRoot causeDecisionOperations | ChangeRoot causeTroubleshootingComparison |