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 Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
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
Purposedifferent
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.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.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min45-90 min45-90 min45–75 min
Participantsdifferent
4-123-123-8Team members involved
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Starfish Board, Practice Changes, ExperimentsExpectation Map, Alignment Notes, AgreementsCATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RetrospectiveImprovementExperimentsTeam
AlignmentStakeholdersTeam
Systems thinkingFramingStakeholders
RetrospectiveLearningReflectionTeam
Add more methods