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 of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker
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 decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min60-90 min1-4 h45-90 min
Participantsdifferent
3-104-103-83-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsProblem Cluster, Prioritized Challenge, ExperimentProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanResponsibility Map, Role Agreements, Open Questions
Tagsno overlap
AutonomyRolesTeam
FacilitationDecisionProblem solvingWorkshop
Root causeProblem solvingQualityIncident
RolesResponsibilityTeamFacilitation
Add more methods