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 Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
Paper illustration of Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes.
Complexitydifferent
HighMediumMedium
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews2-4 h90-180 min
Participantsdifferent
5-122-64-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogFamily Tree Diagram, Pattern Notes, Systemic MeasuresPlanning Levels Map, Cadence Model, Planning Artifact Inventory
Tagsno overlap
ExecutionCadenceLearningGovernance
Root causePatternsIncidentSystemic
CadenceGovernanceExecution
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem