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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Learning Review.
Operations
Learning Review
Purposedifferent
During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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'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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
MediumHighLowMedium
Timedifferent
As neededInitial 3-6 h, then monthly or quarterly reviews30-60 min1-3 h
Participantsdifferent
4-155-123-103-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesExecution Loop, Review Cadence, Strategic Learning LogEmotion Board, Themes, Action ItemsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
IncidentOperationsReliability
ExecutionCadenceLearningGovernance
RetrospectiveTeamReflection
LearningRetrospectiveIncidentOperations
Add more methods