View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy GAP Analysis |  Operations Gemba Walk |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 1-3 h | 30-120 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-8 | 2-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | Observation Notes, Improvement Ideas | 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 |
Tagsno overlap | StrategyAnalysisPlanning | LeanObservationProcessOperations | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
