Match the task to the person

Delegate based on the fit between the task’s demands and the person’s skill, growth needs, and capacity.

Why it works

A delegated task is simultaneously work that must get done and a development opportunity. Matching it to someone whose skills fit (or slightly stretch) protects quality, while a deliberate stretch toward their growth edge builds capability and signals trust. Good matching also distributes load according to real capacity, not just whoever says yes.

How to do it

1. List the task’s actual demands (skills, judgment, time) before picking a person.
2. Choose someone for whom it’s a manageable stretch, not a guaranteed easy win or a setup to fail.
3. Factor in their current load and their development goals, not just availability.

Evidence

Matching challenge to skill is central to flow research and to job-design findings that tasks with the right stretch and meaning drive motivation; transactive-memory research shows teams perform better when work routes to the right expertise. A controlled study found that groups trained together outperformed individually-trained members because a shared transactive memory let work route to whoever knew it best. (observational)

The supporting research is on motivation and team memory generally; "delegation matching" as such is a practitioner application of it.

Sources

• Csikszentmihalyi, flow (challenge–skill balance); Hackman & Oldham (1976), job characteristics model
• Hackman, J. R., & Oldham, G. R. (1976). Motivation through the design of work: Test of a theory. Organizational Behavior and Human Performance, 16(2), 250–279.
• Fong, C. J., Zaleski, D. J., & Leach, J. K. (2015). The challenge–skill balance and antecedents of flow: A meta-analytic investigation. The Journal of Positive Psychology, 10(5), 425–446.
• Liang, D. W., Moreland, R., & Argote, L. (1995). Group versus individual training and group performance: The mediating role of transactive memory. Personality and Social Psychology Bulletin, 21(4), 384–393.

Common mistake

Delegating only the boring, low-growth tasks while hoarding the interesting ones — people read it correctly as offloading, not developing.