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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Kaizen Event.
Operations
Kaizen Event
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
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 a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
45-90 min1-3 h0.5-5 Tage1 h bis mehrere Wochen
Participantsdifferent
3-103-104-101-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsProcess Map, Handoff List, Improvement BacklogKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdatePDCA Log, Experiment Plan, Learning Outcome, Standard Change
Tagsno overlap
AutonomyRolesTeam
ProcessOperationsImprovement
LeanContinuous improvementOperations
Continuous improvementLeanExperiments
Add more methods