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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.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.
Complexitysame
LowLowLow
Timedifferent
30-60 min45-90 min30 min Setup, dann laufend
Participantsdifferent
3-123-121-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshopAsync
Outputdifferent
Start Stop Continue Board, Improvement ActionsExpectation Map, Alignment Notes, AgreementsRAID Log, Status Report Source
Tagsno overlap
RetrospectiveImprovementTeamReflection
AlignmentStakeholdersTeam
RiskTrackingStakeholdersGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective