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 a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of Team Cognitive Load Assessment with its method-specific working model.
Team Design
Team Cognitive Load Assessment
Purposedifferent
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.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 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.When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list.
Complexitydifferent
LowLowLowMedium
Timedifferent
30-60 min45-90 min45-90 min60-90 min
Participantsdifferent
3-124-124-123-12
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Start Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, ExperimentsSailboat Board, Risks, Improvement ActionsCognitive Load Profile, Action List
Tags2 shared
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
RetrospectiveTeamImprovement
TeamComplexityImprovementDiagnosis
Add more methods