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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Sailboat Retrospective
Agile
Sailboat 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 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
30-60 min45-90 min1-2 h45-90 min
Participantsdifferent
3-123-124-124-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsExpectation Map, Alignment Notes, AgreementsAlignment Map, Open Issues, Decision QuestionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
AlignmentStakeholdersTeam
AlignmentStakeholdersStrategyFacilitation
RetrospectiveTeamImprovement
Add more methods