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
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
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
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.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.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
LowMediumLow
Timedifferent
45-90 min1-3 h45–75 min
Participantsdifferent
3-103-12Team members involved
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsKnowledge Map, Critical Knowledge Areas, Transfer Plan4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
AutonomyRolesTeam
KnowledgeMappingRisk
RetrospectiveLearningReflectionTeam
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