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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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.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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
HighLowMediumMedium
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews15-30 min90-180 min1-4 h
Participantsdifferent
5-122-64-123-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogRoot cause notes, CountermeasuresDecision Rights Matrix, AgreementProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ExecutionCadenceLearningGovernance
Root causeIncidentLeanProblem solving
DecisionGovernanceAlignmentResponsibility
Root causeProblem solvingQualityIncident
Add more methods