What does it mean that the delegation decision framework?

Use clear criteria to decide what to delegate, what to automate, and what to keep.

Example: You are a product manager who writes weekly stakeholder updates, reviews pull requests, designs sprint roadmaps, and mentors two junior team members. Every Friday afternoon you feel crushed under accumulated tasks, unable to prioritize. One week you apply a delegation decision framework: you score each task on irreversibility, identity-centrality, and cognitive load. Stakeholder updates — low irreversibility, low identity-centrality, moderate cognitive load — get delegated to your project coordinator with a template. Pull request reviews — moderate irreversibility, moderate identity-centrality, high cognitive load — get split: you review architecture decisions, a senior engineer reviews implementation details. Sprint roadmaps — high irreversibility, high identity-centrality, high cognitive load — stay with you. Mentoring — low irreversibility, high identity-centrality, moderate cognitive load — stays with you but shifts from ad hoc to structured weekly sessions. Within a month you reclaim eight hours per week without losing quality on what matters. The framework did not tell you to do less. It told you to do less of the wrong things.

Try this: List every recurring task you performed this week. For each task, score three dimensions on a 1-5 scale: (1) Irreversibility — how costly is it to fix a poor outcome? (2) Identity-centrality — does this task define who you are or develop a skill only you should develop? (3) Cognitive uniqueness — does this task require judgment, context, or creativity that only you possess? Multiply the three scores to get a Delegation Resistance Score (DRS) ranging from 1 to 125. Tasks scoring below 30 are strong delegation candidates. Tasks scoring 30-60 are candidates for partial delegation or automation. Tasks scoring above 60 should stay with you. Identify your three lowest-scoring tasks and draft a delegation plan for each: who or what system receives it, what specification they need, and what verification you will use.