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
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 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.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
LowLowMediumLow
Timedifferent
15-45 min30-60 min1-3 h30-60 min
Participantsdifferent
1-33-103-103-12
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
ADR File, Decision Log, RationaleEmotion Board, Themes, Action ItemsLearning Review Notes, System Factors, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RetrospectiveTeamReflection
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementTeamReflection
Add more methods