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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.
Complexitydifferent
LowHighLowHigh
Timedifferent
15-45 minInitial 3-6 h, then monthly or quarterly reviews30 min Setup, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-35-121-3 maintaining, briefing for everyoneEvaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleExecution Loop, Review Cadence, Strategic Learning LogRAID Log, Status Report SourcePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ExecutionCadenceLearningGovernance
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods