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
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 for RAPID
Decision Making
RAPID
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
Purposedifferent
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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
45–75 min45-90 min15-45 min30-60 min
Participantsdifferent
Team members involved3-121-33-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, RationaleEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
RetrospectiveTeamReflection
Add more methods