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 | ![]() Agile 4Ls Retrospective | ![]() Knowledge Modeling Knowledge Mapping |
|---|---|---|---|
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. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | 45–75 min | 1-3 h |
Participantsdifferent | 3-10 | Team members involved | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | 4Ls Board, Learning Themes, Improvement Actions | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | AutonomyRolesTeam | RetrospectiveLearningReflectionTeam | KnowledgeMappingRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






