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 of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
HighHighMediumMedium
Timedifferent
Initial 3-6 h, then monthly or quarterly reviewsSeveral meetings plus preparation and analysis; total effort depends on scope1-3 Wochen vom Draft bis zur Entscheidung60-120 min
Participantsdifferent
5-12Evaluation team, architects, and relevant stakeholders3-20 Reviewer2-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + 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 investigationsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ExecutionCadenceLearningGovernance
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDecisionAsyncGovernance
ArchitectureCommunicationStakeholdersCanvas
Add more methods