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
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 Future Reality Tree.
Systems Thinking
Future Reality Tree
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.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
LowHighLowLow
Timedifferent
45–75 min2-4 h45-90 min30-60 min
Participantsdifferent
Team members involved3-83-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsFuture Reality Tree, Negative Branches, Assumption List, Improved InjectionsForce Field Map, Change Levers, Risk NotesEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveLearningReflectionTeam
Theory of ConstraintsSystems thinkingChange
ChangeDecisionStrategy
RetrospectiveTeamReflection
Add more methods