View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingStakeholder MappingSAAM (Software Architecture Analysis Method)
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Stakeholder Mapping |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | 30-240 min | 60–90 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-6 | 2-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Stakeholder Map, Engagement Plan, Risk Notes | 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 | TroubleshootingProblem solvingDiagnosis | StakeholdersAlignmentFacilitationChange | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
