Why You Keep Chasing Your Team for Follow-Through (And How to Stop)

A version of this conversation also lives on The Morning Drive podcast. Audio version embedded below.

Prefer to listen?

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

The question we're answering today

Why are you chasing your team every week to do things they should already be doing — and what does it actually take to stop?

That's the question I get more than any other when I'm in stores. So let's work it.

Why most managers get this wrong

Most managers, when they're stuck in this — and I've been there, I ran stores for a long time — go to the same place. They look at the team and ask "what's wrong with these people?"

That's the wrong question. That's the question that keeps you stuck.

Here's what's actually happening. When you're chasing your team every week, every problem on the floor looks the same to you. Somebody didn't do something they should've done. Your default move is more pressure. You go talk to them. You raise your voice a little. You write it up. You terminate if you have to.

And it works sometimes. Mostly it doesn't.

And here's the part nobody tells you — when the pressure stops working, you don't conclude that the pressure is wrong. You conclude the person is wrong. You start thinking "this team can't be developed. I just need different people." And you start looking for the next hire instead of fixing what's actually broken.

That's the trap. Every gap gets the same intervention. Every failure gets blamed on people. And the harder you work, the more it confirms the story that you're the only one in the building who cares.

I'll tell you what's actually happening. You're trying to enforce a standard your team doesn't fully understand, can't reliably execute, or never agreed to in the first place. And until you know which one of those three is the actual problem — you're guessing.

And guessing in this job feels like working hard. It's not. It's running on a treadmill.

A DM who was stuck in this for years

Let me show you what this looks like in real life.

I worked with a DM a while back — call him Tom. Top performer. Smart guy. Years in the role. He came to me running. Pulling teeth for follow-through from his GMs every week. Showing up at stores Monday morning saying the same things he said last Monday. Going home tired. Coming back Tuesday and doing it again.

When we started talking, the first thing he wanted me to tell him was how to get his GMs to listen. That was the wrong question too. We didn't talk about his GMs for the first hour. We talked about him. About what he was actually walking into every Monday. About what he was assuming when he walked in. About what he was leaving the store with — which most weeks was nothing in writing, no agreed-upon behavior change, no way to verify anything by Wednesday.

He wasn't a bad DM. He was a great DM running on the system he'd been taught. The system he'd been taught was the problem.

And here's what mattered. He didn't get unstuck by working harder. He got unstuck by realizing the layer he was missing wasn't underneath his GMs. It was inside his own week.

The three-question diagnostic

So here's the move. This is the answer to the question we opened with.

Next time you're about to have the same conversation with the same person for the second or third time — stop before you walk in. Ask yourself three questions in order.

Question one — Awareness

Does this person actually know — specifically, in behavior terms, not in theme terms — what I'm asking them to do?

Not "be more accountable." Not "step up." A specific behavior. A specific timing. A specific way of doing it.

If all they have is a general expectation, the problem isn't them. The problem is Awareness. They can't comply with something they don't have a clear picture of.

Question two — Ability

If they do know it — can they actually do it?

Do they have the skill? Do they have the system? Did anyone ever show them what good looks like, or did they get told the standard and then left to figure it out on their own?

If they can't do it — that's Ability. And here's the part most operators miss: pressure doesn't fix Ability. Coaching does. Putting pressure on a skill gap doesn't close the gap. It just terminates the attempt.

Question three — Agreement

If they know it and they can do it — did they ever explicitly agree to own it?

Not a nod. Not an "okay." A real yes they said with their mouth.

If they didn't agree to it — that's Agreement. And that's the conversation you actually need to have.

Awareness. Ability. Agreement. AAA.

Three rungs.

Most managers spend their whole career swinging at Agreement when the actual gap is one of the other two. I see this in stores every week. Operator's frustrated. Going in hot. Reading the team as not committed. And the team's actually just trying to do something they were never properly shown how to do. Wrong fight. Wrong layer. Same result every week.

This three-question check is the diagnostic instrument underneath everything I work on. Walk those three questions before your next correction conversation. Ninety percent of the time, the problem isn't where you think it is.

Why this matters

Most managers, when I walk them through this for the first time, want to argue with it. They want to say "no, my team just doesn't care."

Could be. But before you make that call — you've got to rule out Awareness and Ability first. Otherwise you're telling yourself a story about your team that might not be true. And acting on a story that isn't true wastes your time, costs you good people, and keeps you running on the same treadmill for another year.

The way out of chasing isn't more pressure. It's recognition. Recognizing that you've been treating every problem the same when the problems are not the same. Recognizing that the move that worked when you were a shift leader is now what's keeping you stuck as a GM or a DM. Recognizing that your team is responding rationally to the conditions you set — and the conditions, not the team, are usually what need to change first.

That recognition is what flips the whole picture. Once you see it, you can't unsee it. And the work after recognition is faster, lighter, and more honest than the work before it.

Back to the question

So back to where we started.

Why are you chasing your team every single week — and what does it actually take to stop?

You're chasing them because you've been treating every gap the same and the gap is rarely where you think it is.

What it takes to stop is the three-question check. Awareness. Ability. Agreement. Walk those before your next correction conversation. Ninety percent of the time, the answer reframes the whole situation.

If you want to find out where your operation is actually breaking down across all three — there's a free diagnostic on my site. Takes three minutes. No purchase. No pitch. Just an honest read on which condition is your bottleneck right now.

If something in this article landed — share it with one operator you work with. Not because I'm asking. Because if you're carrying this kind of weight, somebody on your team or in your peer group is carrying it too. And the recognition is what starts the way out.