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 of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Purposedifferent
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.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
LowHighLow
Timedifferent
45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope45-90 min
Participantsdifferent
3-12Evaluation team, architects, and relevant stakeholders2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
ChangeDecisionStrategy
ArchitectureQualityRiskTradeoffsStakeholders
AssumptionsRiskDecisionDiscovery
Add more methods

Often compared together

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

Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)