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 of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.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.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.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.
Complexitydifferent
HighLowHighLow
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope30 min Setup, dann laufend
Participantsdifferent
5-122-8Evaluation team, architects, and relevant stakeholders1-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogAssumption List, Critical Assumptions, Learning PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRAID Log, Status Report Source
Tagsno overlap
ExecutionCadenceLearningGovernance
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskTradeoffsStakeholders
RiskTrackingStakeholdersGovernance
Add more methods