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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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.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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
HighLowLowHigh
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews15-45 min15-30 min1-6 Wochen
Participantsdifferent
5-121-32-64-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogADR File, Decision Log, RationaleRoot cause notes, Countermeasures8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
ExecutionCadenceLearningGovernance
ArchitectureRationaleDocumentationGovernance
Root causeIncidentLeanProblem solving
QualityProblem solvingRoot cause
Add more methods