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 a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
HighLowLow
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews20-60 min30-60 min
Participantsdifferent
5-1213-12
Formatdifferent
Workshop + asyncAsyncWorkshop
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogPlain-language Explanation, Knowledge Gaps, Study NotesStart Stop Continue Board, Improvement Actions
Tagsno overlap
ExecutionCadenceLearningGovernance
LearningKnowledgeUnderstanding
RetrospectiveImprovementTeamReflection
Add more methods

Often compared together

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

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective