Your Time Problem Is a Delegation Problem
The average manager now carries 51% more responsibilities than they can effectively manage, according to a Gartner survey of more than 6,000 managers and employees. Microsoft’s 2025 Work Trend Index found the typical worker is interrupted every two minutes, roughly 275 times a day. Gallup’s latest State of the Global Workplace report shows manager engagement falling to 22%, the steepest drop of any group it tracks.
I hear the human version of those numbers every week from the leaders I work with, especially the ones sandwiched between the top and the bottom of their organizations. More demands, fewer resources, a calendar that belongs to everyone else. The sentence is always the same: I don’t have time.
For years at McKinsey, I prided myself on being the person people could turn to when something needed fixing. I enjoyed solving difficult problems and being someone others could rely on. But over time, I realized that constantly stepping in to solve problems was preventing me from focusing on the bigger things that only I could do.
Caroline Webb, a former McKinsey Partner and one of the world’s leading voices on applying behavioral science to work. She has written the playbook I wish I had back then “Leadership Intelligence”. The book tackles 21 of the toughest challenges leaders face when managing people, offering practical guidance for each.”
The real reason you have no time
Time is finite. Caroline’s starting point sounds obvious, yet most of us lead as if one more thing could always be shoehorned into the day. The loudest requests win our attention, and we end up, in her words, “fitting your time around other people’s priorities and not your own.”
No one’s going to manage your time for you, no one’s going to send you less stuff”
she told me. The only lever a leader has is intention: deciding, deliberately, where a tiny amount of conscious attention gets to play.
Caroline’s framework for that decision runs in three steps, and the order matters.
First, name your positive yes: the work you are uniquely placed to do as a leader. Usually, that means setting strategic direction, addressing complex people issues, and helping your team perform at its best.
Second, let go and grow: if someone else can do the work, give them the opportunity to step up and take it on.”
Third, say a clear, positive no to what does not belong on your plate at all.
It starts with the yes because the yes tells you what the other two are for. Once you know what you are protecting, the no stops feeling arbitrary and the letting go stops feeling like a loss.
Start with what only you can do
Here is the trap. The work you are best at is usually the work that made your name. It feels habitual, it makes you feel productive the moment you pick it up, and somebody thanks you every time you finish it. As you rise, that same work is often the first thing you should stop doing.
Lindsay, one of the role models in Caroline’s book, was the safe pair of hands in a large multinational: liked by everyone, extremely capable. She wanted to help and people wanted her help. That is exactly why she was stuck in the day-to-day details, until her CEO made it clear that the strategic issues needed her and the daily fixing did not.
The hard part is rarely the work that only you can do; that list is obvious. The hard part is the work you can do better than the people around you, because you keep going back to it. You can do it better, after all.
Caroline’s answer is disarmingly simple.
You might be the team’s fastest typist. Does that mean you should do everybody’s typing?”
Every hour of typing is an hour not spent on the strategy, the culture or the deep people issue that nobody else is going to tackle.
So the question she asks leaders is sharper than “what can other people do?” If you only hand over what someone already does as well as you, you will never hand over anything.
Skip that question and the cost compounds. Your people never get the reps, so they never develop. You plateau, because nobody promotes a leader whose team cannot do what the leader does. In the meantime, you are carrying your leadership work and a good share of your team’s work, which is exhausting.
There is grief in letting go, and it helps to admit it. An executive told Caroline he felt “almost jealous” handing over a task he was known for, even though he knew it was the only way to do justice to the annual planning round. That honesty is the beginning of an identity shift. Your role becomes less about being great at a task and more about building people who will, in time, be as good as you.
Start small. Choose one piece of work to delegate to a team member and treat it as an experiment. Show them how you would approach it, agree on how they’ll keep you updated, and then give them the space to take ownership.”
How to say no without damaging the relationship
Letting go only creates space if you can protect it. The moment you clear something off your plate, something else arrives to fill the gap, and most of us let it, because we believe a no will cost us the relationship.
Caroline’s claim is the opposite. “There is a way of saying no that helps the relationship rather than harms it.” Her version builds on William Ury’s positive no and runs in four steps.
Start with warmth: this sounds like a great project, thank you for thinking of me. Then state your positive yes: here is what I am fully committed to right now. Then the no that follows from it: because of that, I am having to say no to things I would otherwise love to do. Close with warmth and a real alternative, never a vague “come back in three months.”
The counterintuitive move is leading with the yes. It reminds you, and the other person, what you are protecting. People are usually “thrilled that you’re making a choice rather than letting them dangle,” as Caroline puts it, and the relationship ends up stronger, not weaker.
I think of it as simple math.
If I spread myself across 10 things, I’m making one inch of progress on all 10, which I’m gonna long term end up disappointing people.”
Making meaningful progress on three priorities is better than making little progress on ten.
How to delegate without micromanaging
Delegation fails at two extremes. You hand something over and step away completely, or you hand it over and never take your hands off it.
The second failure does more than annoy people. Autonomy feeds the brain’s reward system, the engine of motivation, which is why self-determination theory treats it as a basic psychological need. Take autonomy away and motivation drops. Performance follows. Gallup found the same thing at company level. In a study of Inc. 500 CEOs, the leaders who were good at delegating grew their companies much faster over three years than the leaders who kept hold of the work, and brought in 33% more revenue.
Caroline’s middle path is what she calls fixed-flex:
Decide what you are fixed on, which is usually three things: what the finished work needs to contain, how good it needs to be, and when it is due. Then let people know what you are flexible on: the format, the person’s approach. Most of us only cover the first part, but letting people know where you are flexible gives them real ownership of the work at hand.
Then talk through the things that seem obvious to you but may not be obvious to the person you’re delegating to. Do you want a rough first draft or a finished document? A one-page summary or a full report? A realistic timeframe, and when should you check in along the way? Five minutes on these questions up front saves a week of rework later.
Delegating when your team uses AI
Most of your team now uses AI, so it is tempting to assume a task that used to take a week now takes an afternoon. It does not. AI speeds up the middle of the work, it does not speed up the two parts that matter most: thinking clearly about the problem before you start, and checking the answer when it comes back.
A 25-year-old with a prompt and a 20-year veteran reviewing the result need very different amounts of time, because judgment comes from experience. If you push people to move faster than that, you get work that looks finished and is wrong.
The research says the same. In 2025, Microsoft Research and Carnegie Mellon surveyed 319 knowledge workers. The more people trusted the AI, the less they thought for themselves. The more they trusted their own expertise, the more they thought. So when you delegate, say how you want AI used. First, do your own thinking before you open the tool. Then use AI for three things: to find the holes in your work (“Don’t tell me what’s good about this. Tell me where the holes are.”), to practice a hard conversation, or to add one more option to your list. Used that way, as Caroline puts it, AI “amplifies their intelligence rather than atrophies it.”
How to coach employees instead of fixing for them
Most leaders say they want to develop their people. Yet when a team member comes to us with a problem, our first instinct is often to jump in with the answer.
The research on this is uncomfortable. For a Harvard Business Review study, Julia and Trenton Milner asked managers to coach a colleague. Most of them simply gave advice, then rated themselves as good coaches. The authors called it micromanaging-as-coaching. After 15 hours of training, expert ratings of their coaching rose by about 40%. Coaching is a skill. Giving advice is often our default when we haven’t developed it.
Caroline’s image for this is the gym.
We don’t build capability and strength by watching a trainer lift weights. We have to do it ourselves.”
Your people get stronger by thinking through the problem, not by listening to you think it through for them.
So pause before you solve, and let Caroline’s GUIDE model shape the conversation:
G is for Goal. Ask what they are really trying to solve. A “supplier problem” might be a quality issue, a contract issue or an operations issue, and naming it is half the work.
U is for Understand. Ask what they already know. Sometimes they are off track and you find out early. Sometimes they know things you do not.
I is for Ideas. Ask what they have tried and what options they see, before you add your own. You can still add yours. Theirs come first.
D is for Deepen. Test the thinking with one hard question: what would you have to believe for this to work? What if the opposite were true?
E is for Enable. Agree on the next step, when it happens, and what they will do if something goes wrong.
What makes it stick is intention. Solving a problem feels good, so in the rush between meetings, development loses by default. Before each one-on-one I now set a single intention: “My job in this meeting is development. It’s not solving the problem.” Replace one instruction with one question, then stop talking.
Then build growth into the work itself. Give people stretch projects that lead somewhere, not office housework. Hand over front-of-room moments you would normally keep. Bring someone into a high-stakes meeting they would not normally attend, and debrief it properly afterward. The daily practice of letting people do the lifting is what compounds.
Winning back your time, one practice at a time
Coaching someone through a task the first time can take three times longer than doing it yourself. That feels like a bad trade until you remember it pays back the fourth, fifth and twentieth time, and that it builds a person along the way.
You do not need to change everything at once. Pick one of these:
- Write down your positive yes, and take two minutes each morning to recommit to it.
- Choose one task you are holding onto and ask the kicker question: what could someone else do, even if not as well as me?
- Say one positive no, with your yes first.
- Before your next handover, name what is fixed, name what is flexible, and have the what-when-how conversation.
- In your next one-on-one, ask “tell me how you’re thinking about this” before you offer anything.
Winning back your time isn’t about working harder or becoming more efficient at doing everything yourself. It’s about making deliberate choices about what only you can do, trusting others with more responsibility, and investing in their development.
The next time you catch yourself thinking, ‘It’s faster if I just do it myself,’ ask yourself a different question:
‘Am I solving today’s problem or building a team that can solve tomorrow’s?’
For a deeper dive into these practices, listen to my conversation with Caroline Webb on The Flourishing Edge.
Learn more about Caroline Webb on LinkedIn.
Listen to the podcast with Ashish and Caroline Webb. above, You can also listen on Apple Podcasts.
Access and subscribe to all of the episodes of the Flourishing Edge Podcast here.
Make Flourishing Your Competitive Edge.
