Week 4 Day 7: Assignment: Identify One Thing You Do That Your Team Should Own

Look at your calendar and your task list from the past two weeks. Find one thing you did that is not actually a leadership function. Maybe you wrote a status report your tech lead should own. Maybe you ran a meeting that a senior developer could facilitate. Maybe you reviewed a document that did not need your eyes. Pick one thing. Just one. And give it away this week.

Here is how to hand it over without creating a mess. First, pick the right person -- someone who has the skill for this task or is ready to grow into it. Second, transfer context, not just the task. Do not say 'you run this meeting now.' Say 'here is why this meeting exists, here is what a good outcome looks like, here is what a bad one looks like, and here are the three people who care most about the output.' Third, set a check-in date -- not to take it back but to make sure the handoff landed. Say 'let us sync on this in two weeks so I can hear how it is going and help if anything is unclear.' Fourth, and this is the hard part: when they do it differently than you would have, let it go. If the outcome is acceptable, the method does not matter. Your way was not the only way. It was just the way you were used to. This assignment connects directly to Week 5, where we will go deeper into clearing the path versus carrying the load. Start with one thing. One.

Research on delegation effectiveness by Yukl and Fu (1999) identified that the two most common delegation failures are insufficient context transfer and premature reclamation. Leaders who delegate tasks without transferring the 'why' behind the task -- its purpose, its stakeholders, its success criteria -- set up the delegate for failure. And leaders who take tasks back at the first sign of imperfection teach the team that delegation is performative, not real. A study by Spreier, Fontaine, and Malloy published in Harvard Business Review found that leaders who scored high on 'socialized power motivation' (wanting to empower others) delegated more effectively than those with 'personalized power motivation' (wanting to maintain control), and their teams showed 15-20% higher performance over a 12-month period. The practical implication is that effective delegation is a skill that must be practiced deliberately. This assignment is intentionally small -- one task, one handoff -- because the habit of letting go starts with a single controlled experiment. If you can hand off one thing well this week, you can build on that pattern throughout the rest of this course.