This edition looks at the line between helping and taking over, three places the problem might live, and what to ask when someone hands the work back to you.
You're sitting at your kitchen table at 8:40 on a Thursday night. A report is due to your director in the morning, and one of your team members turned it in to you that afternoon. The problem is that it doesn't sound like you. You wouldn't build the document this way. It's not going to work in the actual room. You wouldn't present the data like this; it's not how your boss likes to see things, and it's way too long for the time you've been given. So you start rewriting.
Two hours later, it's perfect. It's also completely different. You'll have to talk to your team about it after the presentation tomorrow because there's no time now. The presentation will go as planned in the morning, but your team member will have wasted all of their time putting it together; they won't have grown at all from this, and you'll now have to find time on your calendar later to give a feedback session.
What the promotion actually rewarded
You are dependable, know the work, and deliver. Those are real strengths, and they're part of the reason you now have a team of your own. But your success no longer depends only on your own output. What other people produce is now what you produce, and that is a different kind of accountability. A leader is failing if their team is not succeeding.
In the scenario above, rewriting the report might have been the only answer, but developing your team is always your job. It is more time-consuming, takes more energy, and cannot be done in one night.
Am I helping or am I taking over?
The line is easy to cross without noticing. It tends to show up in a few ways. You step in because it's faster than explaining. Sometimes your experience shows you things and you just want to help. Sometimes you find you have grabbed a task back because someone approached it differently than you would have. I've had people start walking into my office saying "I'm stuck" instead of "here's what I tried." And then I've found myself in threads and meetings that I didn't need to be in.
When I as the leader didn't handle the problem correctly, the team ends up learning that the work isn't really theirs. It's always ultimately mine. All they have to do is bring it to me.
What's underneath it all
Before deciding the issue is the employee, it helps to look at what you can actually observe and then work through three places the problem might live.
People. Sometimes there is a real gap in skill or confidence. Ask whether the skill is missing or whether it has never been given room to come to life. An employee whose work gets completely rewritten every time learns to stop investing in themselves.
Communication. Was the assignment defined well enough for your team to succeed at it, or just to complete it? Does your team know the purpose of this assignment, or have they been given the authority to create something new? What specifics have they been given that help them understand what a win looks like?
Systems. Where, when, and how do you as the leader see the work before it's finished? As much as my teams hated this, we were always done well before the deadline, because you have to factor in the chaos you know is coming. Also, have you clearly defined what goes into the assignment before it even begins? Where is your team to go for information or support when they are stuck?
What the leader can do instead
When your team starts coming to hand the work back, try these instead:
- What have you tried, and where are you stuck?
- Based on what your goals are, what do you think should happen here?
- How can I help you get to where you need to get to next in this project?
Take the time you need to help them work through the problem. Make the connection. Provide the access. Give them the report. Forward the email. Make the call.
Then be honest about what you can do to help them. What is your responsibility as a manager in this project, and what is their responsibility as a team member? Some decisions need your authority, and others you've simply gotten used to doing. Make those decisions and be clear with your team.
When you are handing something off, say it plainly. "I've been handling the weekly report. I'd like you to own it. Here's what the director looks for, here's when I'd like to see a draft, we can discuss it in our next weekly meeting, and here's what's yours to decide without checking with me."
Checkpoints are key to staying informed on progress, making yourself available to your team, and catching quick coaching opportunities along the way. None of this requires you to take the work back. Lastly, change what you measure. Ask yourself, if I took a week off, what would stall? That tells you more about your effectiveness than your own task list does.
The Leadership Check
Two moves this week
- Choose one of your recurring responsibilities that you should not be doing and write what you think is in the way: a capability gap, an expectation you never defined, or a missing process.
- Give yourself a date to have the conversation. This includes fixing whatever is blocking it.
The first time you do this, it will not go smoothly. Nothing ever does. Your team is used to handing this type of work off to you and you not pushing back. But this is different. They might not see it that way now, but this is development. The growing pains your team will experience up front will be real, but they are worth it when you think about how efficient you and your team can be once everyone is doing their own work.
Between the Work and the People is published by Next to Nunn. Browse every past edition, or visit the Between the Work and the People page.
