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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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 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
Purposedifferent
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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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.
Complexitydifferent
LowLowHighLow
Timedifferent
15-45 min45–75 minInitial 3-6 h, then monthly or quarterly reviews30-60 min
Participantsdifferent
1-3Team members involved5-123-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
ADR File, Decision Log, Rationale4Ls Board, Learning Themes, Improvement ActionsExecution Loop, Review Cadence, Strategic Learning LogEmotion Board, Themes, Action Items
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RetrospectiveLearningReflectionTeam
ExecutionCadenceLearningGovernance
RetrospectiveTeamReflection
Add more methods