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 for Mad Sad Glad
Agile
Mad Sad Glad
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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.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.When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.
Complexitydifferent
LowHighLowLow
Timedifferent
30-60 minInitial 3-6 h, then monthly or quarterly reviews30-60 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
3-105-123-12Scrum Team
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Emotion Board, Themes, Action ItemsExecution Loop, Review Cadence, Strategic Learning LogStart Stop Continue Board, Improvement ActionsImprovement actions, Team agreements
Tagsno overlap
RetrospectiveTeamReflection
ExecutionCadenceLearningGovernance
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementLearning
Add more methods