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 for Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
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 Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitysame
LowLowLowLow
Timedifferent
20-45 min45-90 min45–75 min45-90 min
Participantsdifferent
1-84-12Team members involved4-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesStarfish Board, Practice Changes, Experiments4Ls Board, Learning Themes, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tags1 shared
ResponsibilityLeadershipTeam
RetrospectiveImprovementExperimentsTeam
RetrospectiveLearningReflectionTeam
RetrospectiveTeamImprovement
Add more methods