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 for Feynman Technique.
Knowledge Modeling
Feynman Technique
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier 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.The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
HighLowMedium
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews20-60 min2-4 h
Participantsdifferent
5-1212-6
Formatdifferent
Workshop + asyncAsyncWorkshop + async
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogPlain-language Explanation, Knowledge Gaps, Study NotesBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
ExecutionCadenceLearningGovernance
LearningKnowledgeUnderstanding
Root causeSafetyIncident
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 Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem