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 Delegation Poker.
Facilitation
Delegation 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 Knowledge Mapping.
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
LowLowMedium
Timedifferent
45-90 min45–75 min1-3 h
Participantsdifferent
3-10Team members involved3-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role Agreements4Ls Board, Learning Themes, Improvement ActionsKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
AutonomyRolesTeam
RetrospectiveLearningReflectionTeam
KnowledgeMappingRisk
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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 Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration for Feynman Technique.
Knowledge Modeling
Feynman Technique