methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.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
MediumLowMediumHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional45-90 min2-4 hPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people3-123-12Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
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 checksForce Field Map, Change Levers, Risk Notes7S Assessment, Alignment Gaps, Change ActionsDomain 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
ArchitectureQualityRiskAssessmentLean
ChangeDecisionStrategy
OrganizationStrategyAlignmentChange
ArchitectureChangeAnalysisComparisonQuality
Add more methods