You're Doing Your Team's Work. Here's How to Stop.

Prefer to listen?

This article is also Episode 03 of The Morning Drive — operator-to-operator, ten minutes from the field.

You're doing your team's job. Why are you doing your team's job?

You did not plan it this way. You hired people. You trained them. You handed things off. And somehow the work keeps landing back on your desk. You stay late. You catch what they miss. You tell yourself it's faster to just do it.

So you do it. Again.

If that's you, this one's for you.

What most bosses think the problem is

Most bosses in this spot reach for the same explanation. They think it's a delegation problem. "I'm bad at letting go." Or they think it's a people problem. "My team won't pull their weight." Or they think it's a willpower problem. "I just need to stop being a control freak."

I get it. I've been there. But every one of those explanations sends you to the wrong fix.

If it's a delegation problem, you read another delegation book. If it's a people problem, you start managing out your team. If it's a willpower problem, you white-knuckle it and let things slide that should not slide.

None of that works. Because none of that is what's actually happening.

Let me tell you about a team I took over

Years back I took over a retail operation. Team of more than sixty people. The turnover was running two hundred percent a year. Most folks there just needed a job to get by. A lot of them told me straight up they didn't come there to work hard.

Forty-five days in, I was doing what every manager does when they take over an underperforming team. I was everywhere. I caught every miss. I covered every gap. I worked twice the hours of anyone on that floor. And I called it being "accountable."

I was proud of it. I thought carrying the load was the job.

About ten months later it hit me. I wasn't holding anybody accountable. I was just absorbing the work. The team wasn't failing to do their jobs. The jobs had never actually become theirs. I'd assumed the handoff. I'd never installed it.

Nobody on that floor had ever clearly agreed to own anything. So when it didn't get done, there was nothing to point to. No owner. No promise. No line. Just me, picking it up. Every time.

Here's what's really going on

The work keeps coming back because ownership was never fully transferred.

A nod is not a handoff. "Sounds good" is not a commitment. Telling someone what to do is not the same as them agreeing to own it.

When you hand work to someone and they don't own it, only one person is left holding it. You.

So stop calling it a delegation problem. It's a transfer problem.

Stop trying to let go harder. Start installing the handoff.

Stop absorbing the work and calling it accountability. Start getting a real yes before you walk away.

Why this matters more than you think

Here's what it's costing you. Not just the hours. The hours are bad enough.

It's costing you the thing you actually wanted when you took the job. You wanted to lead. You wanted to build something that runs when you're not standing on top of it. Instead you're the bottleneck. You can't take a day off. You can't take a vacation. You go home tired and you come back to the same pile.

And here's the part that stings. The longer you carry it, the more your team learns that you'll carry it. You've trained them to hand it back. Not because they're lazy. Because you taught them the work returns to you if they wait long enough.

Here's the good news. That's fixable. Permanently.

It's a method problem, not a people problem

Your team isn't broken. The way the work gets handed off is broken.

There's a real reason your people don't follow through, and it's almost never the reason you think. Sometimes they don't know what good looks like. Sometimes they can't actually do the thing yet. And sometimes, like the team I took over, they never really agreed to own it in the first place.

Three different breakdowns. Three different fixes. And if you misread which one you're dealing with, you fix the wrong problem and the work comes right back.

That's one of three things every boss has to get right before any of this works. Doing your team's job is just the most exhausting symptom of getting one of them wrong.

So what do you do Monday?

One move. Just one.

Pick the next thing you're about to take off someone's plate and put on yours. Before you do it, stop and ask them four questions. Who owns this? What does done look like? When is it due? And what's the first step you'll take?

Then wait for a real answer. Not a nod. A yes, in their words.

If you can't get that yes, you just found your problem. And it was never that you're bad at delegating.

You're doing your team's job because the work was never truly handed off. Get the yes first, and you stop being the place the work comes home to.

If you want help figuring out where this is breaking in your operation, there's a free three-minute diagnostic at https://www.kwanhoward.com/accountability-diagnostic. It tells you whether your follow-through problem is Awareness, Ability, or Agreement, so you know which fix to reach for.

Reference Framework: Awareness, Ability, Agreement

Before you treat a missed commitment as an accountability issue, diagnose the breakdown. Most follow-through failures are one of three things:

• Awareness — The person understands what good looks like. They can name the standard, not just nod at it.

• Ability — The person can actually execute, with the skill, time, tools, authority, and support they have.

• Agreement — The person clearly committed to the owner, the outcome, the deadline, and the first step. In their own words.

Work from the bottom up. Whichever rung breaks first is the one to fix. Skipping rungs makes the problem worse.

Use this before treating a missed commitment as an accountability problem. Accountability only works after Awareness, Ability, and Agreement are in place.

Awareness, Ability, Agreement is the diagnostic at the center of the book Say It Once by Kwan Howard.

A note on the data behind this

I asked twenty-nine managers to describe their follow-through problem in their own words. Not one of them used the word "accountability." They said they were buried. They said they were doing everyone's work. They said their team wouldn't pull their weight. They felt the problem clearly. They just never named it the way the textbooks do.

Almost half of them described the exact pattern in this article. Doing work that was supposed to be someone else's.

That's not a delegation problem. That's a transfer problem. And it's the single most common one I see.