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 Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
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 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.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.
Complexitysame
LowLowLowLow
Timedifferent
30-60 min30-60 min45-90 min45-90 min
Participantsdifferent
3-123-103-124-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action ItemsExpectation Map, Alignment Notes, AgreementsStarfish Board, Practice Changes, Experiments
Tags1 shared
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
AlignmentStakeholdersTeam
RetrospectiveImprovementExperimentsTeam
Add more methods