View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Soft Systems MethodologyLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)Cynefin Workshop
| Criterion |  Systems Thinking Soft Systems Methodology |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Cynefin Workshop |
|---|---|---|---|---|
Purposedifferent | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | 0.5-3 Tage | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope | 60-180 min |
Participantsdifferent | 5-15 | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting | 4-20 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | 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 | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | Soft systemsComplexitySensemakingSystems thinking | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality | ComplexitySensemakingDecision |