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 |  Facilitation Lean Coffee |  Operations Root Cause Tree Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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 group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 30-90 min | 1-3 h | 15-30 min |
Participantsdifferent | 3-10 | 3-20 | 2-8 | 2-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Prioritized Topics, Discussion Notes, Action Items | Cause Tree, Evidence Notes, Countermeasures | Root cause notes, Countermeasures |
Tagsno overlap | AutonomyRolesTeam | FacilitationAutonomyDialogue | Root causeTreeIncidentQuality | Root causeIncidentLeanProblem solving |