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 Futures Wheel with its method-specific working model.
Systems Thinking
Futures Wheel
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event.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 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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.
Complexitydifferent
MediumLowLowLow
Timedifferent
60-120 min45-90 min30-60 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
3-104-123-10Scrum Team
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Futures Wheel, Consequence Chains, Strategic SignalsStarfish Board, Practice Changes, ExperimentsEmotion Board, Themes, Action ItemsImprovement actions, Team agreements
Tagsno overlap
ForesightSystems thinkingSignals
RetrospectiveImprovementExperimentsTeam
RetrospectiveTeamReflection
RetrospectiveImprovementLearning
Add more methods