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
A paper-based illustration representing OKRs with its core stages and visible working result.
Product Strategy
OKRs
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper objective sheet with five SMART fields, baseline, target, owner, deadline and a complete result statement.
Product Strategy
SMART Goals
Purposedifferent
When strategic direction needs to become measurable, it connects ambition with checkable results. It makes goals connectable to focus and review.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.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.When goals are formulated too generally, it brings measurability, direction, and timing into shape. It prevents intentions from staying without clear verification.
Complexitydifferent
MediumHighHighLow
Timedifferent
1-2 h SetupPreparation, scenario analysis, and findings review; effort depends on scopeSeveral meetings plus preparation and analysis; total effort depends on scope15-30 min
Participantsdifferent
2-20Architecture experts and stakeholders for scenarios and weightingEvaluation team, architects, and relevant stakeholders1-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
OKR set, Measurement plan, Review cadenceDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsSMART Goal, Measurement Note, Deadline
Tagsno overlap
GoalsAlignmentOutcomesMeasurement
ArchitectureChangeAnalysisComparisonQuality
ArchitectureQualityRiskTradeoffsStakeholders
GoalsPlanningMeasurementAlignment
Add more methods