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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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 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 min Setup, dann laufend30-60 min45-90 min
Participantsdifferent
3-121-3 maintaining, briefing for everyone3-104-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsRAID Log, Status Report SourceEmotion Board, Themes, Action ItemsStarfish Board, Practice Changes, Experiments
Tagsno overlap
RetrospectiveImprovementTeamReflection
RiskTrackingStakeholdersGovernance
RetrospectiveTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods