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 Responsibility Poker.
Facilitation
Responsibility Poker
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
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.When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences.With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.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.
Complexitysame
LowLowLowLow
Timedifferent
45–75 min45-90 min45-90 min30-60 min
Participantsdifferent
Team members involved3-102-83-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsResponsibility Map, Role Agreements, Open QuestionsRACI Matrix, Responsibility Map, Decision NotesEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
RolesResponsibilityTeamFacilitation
RolesResponsibilityGovernanceOperations
RetrospectiveTeamReflection
Add more methods