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 for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
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.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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.
Complexitydifferent
LowMediumLow
Timedifferent
45-90 min1-3 h30-60 min
Participantsdifferent
3-122-83-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsCause Tree, Evidence Notes, CountermeasuresStart Stop Continue Board, Improvement Actions
Tagsno overlap
AlignmentStakeholdersTeam
Root causeTreeIncidentQuality
RetrospectiveImprovementTeamReflection
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 Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective