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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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 Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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 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 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
30 min Setup, dann laufend30-60 min30-60 min45-90 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-123-104-12
Formatdifferent
AsyncWorkshopWorkshopWorkshop
Outputdifferent
RAID Log, Status Report SourceStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action ItemsSailboat Board, Risks, Improvement Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
RetrospectiveTeamImprovement
Add more methods