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 Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for RAPID
Decision Making
RAPID
Purposedifferent
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.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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.
Complexitydifferent
HighHighMedium
Timedifferent
Initial 3-6 h, then monthly or quarterly reviewsSeveral meetings plus preparation and analysis; total effort depends on scope45-90 min
Participantsdifferent
5-12Evaluation team, architects, and relevant stakeholders3-12
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
ExecutionCadenceLearningGovernance
ArchitectureQualityRiskTradeoffsStakeholders
DecisionRolesGovernance
Add more methods

Often compared together

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

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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments