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
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Purposedifferent
ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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.
Complexitydifferent
HighMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope2-4 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-12
Formatdifferent
Workshop + asyncWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
OrganizationStrategyAlignmentChange
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Stakeholder Mapping
Facilitation
Stakeholder Mapping