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 for RAPID
Decision Making
RAPID
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 of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
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.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitydifferent
MediumHighHighMedium
Timedifferent
45-90 minInitial 3-6 h, then monthly or quarterly reviewsSeveral meetings plus preparation and analysis; total effort depends on scope1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
3-125-12Evaluation team, architects, and relevant stakeholders3-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
RAPID Role Map, Recommendation, Decision LogExecution 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 investigationsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
DecisionRolesGovernance
ExecutionCadenceLearningGovernance
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDecisionAsyncGovernance
Add more methods