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 |  Operations Process Mapping |  Operations PDCA Cycle |  Agile Starfish 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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 h | 1 h bis mehrere Wochen | 45-90 min |
Participantsdifferent | 3-10 | 3-10 | 1-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Process Map, Handoff List, Improvement Backlog | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | AutonomyRolesTeam | ProcessOperationsImprovement | Continuous improvementLeanExperiments | RetrospectiveImprovementExperimentsTeam |