View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Delegation Poker |  Decision Making OODA Loop |  Domain Modeling Context Map |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 15-60 min je Zyklus | 1-3 h | 45–75 min |
Participantsdifferent | 3-10 | 1-8 | 2-8 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Situation Assessment, Decision Loop, Action Updates | Context Map, Integration Patterns, Boundary Notes | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | AutonomyRolesTeam | DecisionChangeLearningStrategy | Domain-Driven DesignBoundariesStrategy | RetrospectiveLearningReflectionTeam |