View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Business Strategy GAP Analysis |  Product Strategy OKRs |
|---|---|---|---|
Purposedifferent | 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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | When strategic direction needs to become measurable, it connects ambition with checkable results. It makes goals connectable to focus and review. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h | 1-2 h Setup |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 2-20 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | 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 | Gap Matrix, Action Plan, Risk Notes | OKR set, Measurement plan, Review cadence |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | StrategyAnalysisPlanning | GoalsAlignmentOutcomesMeasurement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
