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
How Might We
Innovation
How Might We
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
Purposedifferent
With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction.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.
Complexitysame
LowLowLow
Timedifferent
30–45 min45-90 min45–75 min
Participantsdifferent
1-103-10Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
HMW Questions, Challenge Framing, Idea PromptsDelegation Board, Decision Boundaries, Role Agreements4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
FramingOpportunityIdeationQuestions
AutonomyRolesTeam
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 for Learning Review.
Operations
Learning Review
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker