Why Your Team Keeps Getting It Wrong (It's Not Them)

By Phillip Henslee  |  Agile Leadership Learning  |  Estimated read time: 6 minutes

▶  YOUTUBE VIDEO

Why Your Team Keeps Getting It Wrong (It's Not Them)

Prefer to watch? The full video version of this article is above. Or keep reading below — same idea, with two extra real-world examples that didn't fit in the 5-minute video.

You delegated something to one of your people last week.

You told them what you needed. They said "got it." You walked away thinking it was handled.

Friday rolls around. You see the work. It's not what you wanted. Not even close.

And the first thought in your head is: "What's wrong with this person?"

Nothing's wrong with that person. Something's wrong with how you delegated it.

Who this is for

I'm Phillip Henslee. I've spent 40 years leading people across six different industries — Navy, semiconductors, shipbuilding, federal services, retail, alternative fuels.

This blog is for the person who got promoted in the last 6 to 24 months and is figuring out — fast — that nobody trained you for this.

Today we're talking about the very first wall every new manager hits. And I'll show you exactly how to stop hitting it.

The Real Problem

Here's what most new managers don't realize:

When you delegate, you're not telling your team what you want. You're telling them what you're thinking.

And those are two very different things.

What you're thinking has 20 years of context behind it. The standards. The customer. The unwritten rules. The way it's "supposed" to look.

Your team doesn't have any of that. They have the words you said. That's it.

So when you say "put together a quick summary for the client meeting" — you're picturing the format you've used for ten years. They're picturing whatever a "quick summary" means in their head. Probably from the last manager they had, who wanted something completely different.

Your team can't read your mind. When you don't tell them what you actually want — they guess. And they guess wrong.

Why This Matters Right Now

This is the foundational skill. And it matters more right now than it ever has.

Half the companies in America have done force reductions in the last two years. Which means a lot of you reading this didn't just get promoted — you got promoted and inherited two other people's teams. You're managing more people than you signed up for, with less time, less training, and less support.

If you can't communicate what you need clearly — fast — your team is going to spin in circles. People will work hard on the wrong things. Deadlines will slip. Morale will drop. And the part nobody tells you: you will burn out twice as fast, because you'll spend your nights redoing work that should have been right the first time.

The data backs this up. Gallup reports that 65% of employees say they don't get enough clarity from their manager. Lack of role clarity is the number one driver of disengagement in the U.S. workforce.

Your people aren't disengaged because they're lazy. They're disengaged because nobody told them what good looks like.

The Fix: Four Things, Every Time

Here's how you fix it. Four things. Every time you delegate. Every time you set an expectation. Every time you start a piece of work with someone on your team.

Number one: tell them what "done" looks like.

Not what the work is. What it looks like when it's finished and right.

If it's a report — how long, what sections, who reads it. If it's a project — what the customer should be able to do at the end. If it's a fix — how you'll know the problem is gone.

Specific. Visual. So they can picture it before they start.

Number two: tell them when it's due, and tell them what "on time" means.

"End of the week" means five different things to five different people. Friday at 5? Thursday so you can review it? Wednesday so the customer gets it Friday?

Pick the actual day. Pick the actual hour. Say it out loud.

Number three: tell them what to do when they get stuck.

Because they will. And the worst thing a new employee can do is sit on a problem for three days because they didn't want to bother you.

Tell them: "If you hit a wall, come find me. Don't wait." Or: "If you're not sure about X, here's the call. If you're not sure about Y, ask me."

You're not micromanaging. You're removing the guesswork.

Number four: ask them what questions they have.

This sounds obvious. It's the step new managers skip the most.

You finish telling them what you need, what "done" looks like, when it's due, what to do when they're stuck — and then you walk away. Mission accomplished.

Don't walk away. Ask: "What questions do you have?" — not "any questions?", because that one gets a no every time. Ask it like you actually want them to find a hole in what you said.

Two things happen when you do this.

One — you catch the misunderstanding right now, in the next 60 seconds, instead of finding out about it Friday afternoon when the work comes back wrong. Cheapest fix you'll ever make.

Two — they start owning the work. The second somebody asks a question and you answer it, they're not executing your plan anymore. They have buy-in. They're executing our plan. That's a different employee on Friday than the one who just said "got it" and walked off.

A team that asks questions is a team that's thinking. A team that just nods is a team that's guessing.

What This Looks Like Done Right

Same delegation, done right, sounds like this:

"I need a one-page summary for the client meeting Thursday. Three sections: what we did last quarter, what's on track for next quarter, what we need from them. Get it to me Wednesday at noon so I have time to review it. If you're stuck on the 'need from them' section, come grab me — that's the part I want to talk through with you anyway. What questions do you have for me?"

Took me 30 seconds. Saved both of us four hours and a difficult Friday conversation.

That's it. That's the skill.

Three Real-World Examples

The principle is universal. The application looks different depending on what your team actually does. Here are three examples from three different kinds of work, so you can see what "clear expectations" sounds like in your world.

Example 1 — The technician on a manufacturing floor

Vague: "Hey, can you go check out line three? Something seems off."

Clear: "Line three's been throwing intermittent quality alarms since the shift change. I need you to run the standard troubleshooting checklist — Sections A through C — and document what you find. Get me a one-paragraph summary by end of shift. If you find anything outside the checklist or you're not sure, stop and call me. What questions do you have?"

Notice the difference. The vague version sends the technician hunting blind. The clear version tells them the symptom, the procedure, the deliverable, the deadline, the escalation rule, and asks for questions. The technician walks away knowing exactly what to do — and so do you.

Example 2 — The analyst preparing a client deck

Vague: "Pull together something for the Henderson meeting next week."

Clear: "I need a 10-slide deck for the Henderson meeting on Thursday at 2pm. Three sections: Q3 results, what we're recommending for Q4, and the budget impact. Stick with our standard template. Get me a draft by Tuesday end of day so I have time to review and we can iterate Wednesday morning. If you hit anything weird in the Q3 numbers, flag it to me right away — don't try to interpret it on your own. What questions do you have?"

Same principle. The clear version pictures the finished work before anyone starts. The analyst can begin immediately, knows where to flag for help, and you're not going to be surprised on Wednesday.

Example 3 — The new hire learning the ropes

Vague: "Just shadow Sarah today and let me know how it goes."

Clear: "I want you to shadow Sarah today on the customer onboarding calls. By the end of the day, I want you to be able to tell me three things: the basic flow of an onboarding call, the two or three places where customers usually get confused, and one question you still have. We'll grab 15 minutes at 4pm to debrief. If something happens during the calls you don't understand, write it down — we'll work through it together at 4. Make sense? What questions do you have?"

With the vague version, the new hire spends the day passively watching and has no idea what they were supposed to absorb. With the clear version, they know exactly what to look for, exactly what success means, and exactly what to do with confusion when it shows up.

The Real Takeaway

The four moves aren't a trick. They're not a hack. They're not something you do once when you read this blog and then forget.

They're a habit. The habit of slowing down for 30 extra seconds at the start of every delegation, every expectation, every assignment — and front-loading the clarity instead of paying for the confusion on the back end.

New managers who build this habit early become the kind of leaders their teams will follow for years. New managers who skip it spend their first two years putting out fires that didn't have to start.

Pick which one you want to be. Then start tomorrow.

Want to Go Deeper?

This is one of dozens of moments new managers hit in their first 90 days that nobody prepared them for. I built three resources for the supervisor who wants to figure this out faster than the long way:

•        The First 30 Days as a New Supervisor — a free field manual covering the five questions every newly promoted supervisor wrestle with.

•        The Leadership Library — 26 self-paced leadership courses, one year of access, yours to work through on your schedule.

•        The Manager to Leader Accelerator — a 4-week live cohort program with live coaching, a 1:1 closing call, and a personalized 90-day action plan you walk away with.

All three live at agileleadershiplearning.com.

About Phillip Henslee

Phillip Henslee is the founder of Agile Leadership Learning and a retired Navy Chief Petty Officer. He's spent 40 years leading people across six industries — Navy, semiconductors, shipbuilding, federal services, retail, and alternative fuels — and now teaches newly promoted supervisors and first-line managers what nobody taught him on his way up.

agileleadershiplearning.com