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 Learning Review.
Operations
Learning Review
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.
Complexitydifferent
MediumMediumLow
Timedifferent
60-120 min1-3 h30-60 min
Participantssame
3-103-103-10
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Futures Wheel, Consequence Chains, Strategic SignalsLearning Review Notes, System Factors, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
ForesightSystems thinkingSignals
LearningRetrospectiveIncidentOperations
RetrospectiveTeamReflection
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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem