Read a sample: 1. From Doing the Work to Leading It
You know how to get the work done. That may be one reason you were asked to lead the team.
Perhaps you are the person colleagues turn to when a customer issue becomes complicated, a deadline starts to slip, or a process stops working. You know where to find the information, whom to ask, and which details are likely to cause trouble. When something needs attention, you step in.
Those skills still matter. But now they serve a different purpose.
As an individual contributor, you could often make a visible difference by completing an assignment yourself. As a manager, your contribution increasingly depends on whether other people understand the work, have room to do it, and can get support when they need it. You are still responsible for results, but you cannot create every result with your own hands.
That change can feel less like a promotion than a loss of familiar ground. The tasks that once made you useful are still there. People may still ask you to handle them. You may be faster than someone who is learning. Meanwhile, the work of leading—clarifying a priority, asking a question, or preparing for a difficult conversation—can feel less concrete than finishing a task.
Yet those conversations are part of the work. They help the team make progress without waiting for you to solve every problem.
This chapter will help you notice where your role has changed, identify habits that may be limiting your team, and decide which responsibilities you should own, share, or stop doing.
Imagine that Maya has been promoted to lead a small customer support team. Before the promotion, she was known for resolving difficult cases. She could read a long customer history, spot the underlying issue, and write a clear response.
During her first few weeks as team lead, Maya keeps doing what made her successful. Whenever a case looks complicated, she takes it. When a colleague drafts a response, she rewrites it before it goes out. She checks the shared inbox frequently and answers questions as soon as they appear.
At first, this seems helpful. Customers receive thoughtful responses, and the team knows Maya is available. But soon several patterns emerge. Colleagues wait for her approval on decisions they used to make themselves. She has little time to explain changes in priorities. A recurring issue continues because she has been too busy resolving individual cases to look at the process behind them.
Maya is working hard. The problem is not her commitment. It is that her old way of contributing is crowding out her new one.
A shift in approach might begin with a conversation:
> “I’ve noticed I’ve been taking over the more complicated cases. I want to make sure you have the chance to handle them, with support when you need it. Let’s look at what decisions you can make independently and where it would be useful to check in with me.”
Maya does not have to disappear from the work. She may still handle a sensitive case, cover an absence, or bring her expertise to a difficult decision. The difference is that she makes those choices deliberately rather than treating every difficult task as hers by default.
Leading means looking beyond the immediate assignment. You pay attention to whether the team has the information, authority, skills, and coordination it needs to do the work well. Sometimes your best contribution will be an answer. Sometimes it will be a question, a decision, a conversation with another department, or the choice to let someone else proceed.
New managers sometimes hear “delegate” and conclude that their job is to hand work over and stay out of the way. Others hear “accountable” and conclude that they must inspect every detail. Neither extreme gives the team much room to succeed.
You can remain accountable for a result while another person owns the assignment. Your responsibility is to make the outcome clear, establish appropriate boundaries, provide access to support, and follow up in a way that fits the work. The person doing the assignment is responsible for carrying it forward, raising concerns, and making decisions within the authority you have agreed on.
Consider the difference between these two statements:
> “Put together the report. I’ll take it from there.”
> “Please prepare the report for Friday’s planning meeting. It needs to show the current workload, the main risks, and any decisions the group needs to make. You can choose the format. Let’s review an outline together before you finish it.”
The second statement does not eliminate every question, but it gives the employee a result to work toward and identifies a useful point for support. It also makes clear that the manager has not simply abandoned responsibility.
The right level of involvement depends on the assignment and the person. A familiar task with limited consequences may need a brief check-in. An unfamiliar or sensitive task may call for closer coordination. Ask what the work requires rather than applying the same level of oversight to everything.
There will also be responsibilities you cannot hand off entirely. Depending on your organization and role, these may include decisions about priorities, communicating expectations, addressing performance concerns, or representing the team to your manager. You can invite input and share parts of the work, but you should understand which decisions remain yours and which require someone else’s approval.
If you are unsure about your…