How to Build Team Capability Through Delegation
Use delegation to grow your people and the team's depth, so the work you hand off leaves the team more capable than it found it. Choose assignments for what they teach, set each stretch up to succeed, debrief the lesson, and close the skills only one person holds.
Developing
Start here. Build the foundation.- 1
When you decide who gets a piece of work, choose partly for the skill it will build, so some assignments push a person just past what they can already do in a capability the team will need more of. Write down what it is meant to develop; if you cannot name the growth edge, you are using existing skill, not building new capability.
- 2
When you give someone work beyond their current range, pair it with support proportional to the stretch: context and a light early check-in for a small step, a named person to consult and a mid-point review for a bigger one, and your time plus a lower-stakes first cut the first time they own anything like it. Make the stretch survivable, not absent.
Proficient
Build consistency and rhythm.- 3
When a delegated piece lands, spend twenty minutes on what worked, what the person would do differently, and what they now know, and write the takeaway in their development notes. This makes the next assignment start higher; skip it and the same person relearns the same lesson.
- 4
When you notice you are keeping high-value work because you do it well, hand some of it to a developing person and accept that the first few passes will be less polished. Pay that dip deliberately on work where a rough first version is survivable, not on your highest-stakes piece, so the team stops depending on you alone.
Mastered
Operate at the highest level.- 5
On a regular rhythm, keep a current map of people against the capabilities the team relies on and mark every skill only one person holds, then aim the next relevant assignment at closing one. A team where several people can do each critical thing absorbs a departure or a surge; a team where one person can is a set of bottlenecks waiting to be found.
Common Pitfalls
Avoid the common failure modes.- Giving stretch work with no support. A stretch without a safety net is a setup to fail, and a failed stretch teaches the person they cannot do it, so match support to the size of the stretch.
- Keeping the work you do best. The work you do well and enjoy is what quietly keeps the team dependent on you, so hand some of it over on work where a rough first version is survivable.
- Skipping the debrief. Work that finishes without a debrief teaches only whoever was paying attention, so spend twenty minutes locking in the lesson and record it.