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 Responsibility Poker.
Facilitation
Responsibility Poker
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 OODA Loop.
Decision Making
OODA Loop
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences.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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min45–75 min15-60 min je Zyklus45-90 min
Participantsdifferent
3-10Team members involved1-83-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Responsibility Map, Role Agreements, Open Questions4Ls Board, Learning Themes, Improvement ActionsSituation Assessment, Decision Loop, Action UpdatesForce Field Map, Change Levers, Risk Notes
Tagsno overlap
RolesResponsibilityTeamFacilitation
RetrospectiveLearningReflectionTeam
DecisionChangeLearningStrategy
ChangeDecisionStrategy
Add more methods