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 a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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.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.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.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
HighLowLowLow
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews30-60 min15-45 min45-90 min
Participantsdifferent
5-123-121-34-12
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogStart Stop Continue Board, Improvement ActionsADR File, Decision Log, RationaleSailboat Board, Risks, Improvement Actions
Tagsno overlap
ExecutionCadenceLearningGovernance
RetrospectiveImprovementTeamReflection
ArchitectureRationaleDocumentationGovernance
RetrospectiveTeamImprovement
Add more methods