They Said They'd Do It. They Didn't. Here's Why It's Probably Not What You Think.

Prefer to listen?

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

You asked your team member to do something.

They said yes.

Then they didn't do it.

You went into the conversation ready. You knew how you wanted to say it. You'd thought about the tone. You knew the line you wanted to land.

And the conversation went sideways.

Maybe they got defensive. Maybe they shut down. Maybe they said something that sounded like an excuse. And you walked away thinking here we go again.

If you've been in that conversation, this is for you.

Because there's a question hiding underneath that conversation. Almost nobody asks it. And it changes everything.

What we tell ourselves

When your team member doesn't follow through, your brain goes to the same place.

They didn't want to.

They're not committed.

They don't care like I do.

It feels true in the moment. It explains what happened. And it's clean. The failure has a name. The name is them, not you.

But here's the thing. Most of the time, that read is wrong.

I'm not saying everyone is an angel. Some people really aren't committed. Some really are dragging their feet. But after years of watching this play out in real stores with real teams, I'll tell you what I've seen.

The "they didn't want to" read is usually a misread.

The real problem is one layer down.

Let me tell you a story

A franchise group I worked with just got a brand visit. The big push was customer friendliness in the drive-thru window.

The Director of Operations went to one of the stores. She was doing a walk-through with the shift manager. The shift manager was newer. Still in her training window.

While they were walking, the Director noticed the cashier at the window. The cashier was saying one thing to every customer. "Order when you're ready." That was it. No hello. No smile. No name. Just "order when you're ready."

The Director pointed it out. "There's something you want to be aware of here."

The shift manager turned and started to coach the cashier. The cashier got defensive right away. Said something sharp. The shift manager backed off.

The Director stepped in. Asked what was going on.

The cashier said this:

They always want us to be fast. Now you want me to round up for charity. Now you want me to sell the add-on. Now you want me to be friendly in three seconds. It's too much. So yeah, I've been taking shortcuts.

Now stop right there.

If you're a manager, that line can land two ways.

The first way is the one most of us jump to. It sounds like attitude. She's making excuses. She's blaming the company for her own bad behavior.

The second way is the one most of us miss. She just told you exactly what's broken in your operation.

Let's walk it back

She shut down. That's what you can see.

Why did she shut down? Because she didn't agree to do what was being asked.

Why didn't she agree? Because she didn't think she could actually pull it off.

Read her words again. "It's too much. So yeah, I've been taking shortcuts."

That's not refusing.

That's a report.

She's telling you the job, as it's currently set up, can't be done. Round up. Push the add-on. Be friendly. All in three seconds. While moving fast. It physically doesn't fit.

So she dropped what she could and kept the line moving.

Why didn't she think she could pull it off? Because the rules changed and nobody told her.

She was trained to go fast. Friendliness used to be one ask. Now it's been piled on top of speed, the round-up, and the add-on. But nobody slowed down the speed standard to make room. So she's stuck doing the old job while being graded on the new one.

When you walk the failure back, you see three layers.

She didn't know the rules changed. So she didn't have the ability to keep up. So she couldn't really agree. So she shut down.

The shift manager was trying to land the conversation at the top. "Be friendlier." But everything underneath was missing. The cashier didn't know the priority had shifted. She didn't have what she needed to deliver all four asks at once. So her agreement wasn't real. It was a nod in the moment and a math problem in real time.

Won't versus can't

This is the part most managers miss.

There are three things that have to be true before accountability works. Awareness. Ability. Agreement.

If any one of them is broken, the conversation blows up on contact.

But here's what we do. We jump straight to Agreement. "You said you'd do it." "You committed." "I need you to follow through."

Agreement is the top of the ladder. That's where most accountability talks try to land.

And when the talk goes sideways, we usually push harder. "I don't get why you're not just doing what we agreed to."

The reason it's not landing? The steps underneath are missing.

You can't get a real yes from someone who doesn't believe they can pull it off. They might nod. They might walk out of your office having technically said yes. But the yes isn't real. The conditions to keep it aren't there.

This is the difference between won't and can't.

Won't is an Agreement problem. The person could do it. They chose not to. You handle it by naming the refusal. Calling out the cost. Holding the line.

Can't is an Ability problem. The person would do it if they could. Something's missing. A tool. A piece of information. A skill. A window of time. Permission they don't have. You handle it by finding what's missing and putting it in place.

If you treat a can't like a won't, you'll get the cashier conversation. Every time. The person shuts down. The talk falls apart. You walk away sure they don't care.

But the truth is you were asking for something they couldn't do.

One question before you walk in

Before your next accountability talk, ask yourself one question.

Can they actually do this?

Not are they motivated.

Not do they care.

Not did they say yes.

Can they. With the tools they have. With the time they have. With what they actually know.

If the answer is a clear yes, then Ability isn't the problem. The breakdown is somewhere else. Maybe Agreement. Maybe Awareness. But you can rule out the most common invisible break.

If the answer is I think so or probably or they should be able to — pay attention to that. That's the signal. The ability isn't there. You're about to walk into a talk that won't land because the ground under it is soft.

The whole conversation changes once you ask this.

Instead of "why didn't you follow through," you walk in with "what's getting in the way."

Same person. Same failure. Totally different talk.

One escalates.

The other gets to the truth.

This isn't just restaurants

I know this story happened in a drive-thru. If you're in restaurants, the lesson lands easy.

If your team works with contracts, the can't is the renewal nobody touches because they're not sure what the trigger date means in the system.

If your team works with cases, the can't is the file that sits at one stage for thirty days because the next person doesn't have what they need to move it.

If your team works with calls, the can't is the callback nobody makes because the list was never cleaned up and they can't tell which numbers were already worked.

The work changes. The team changes. The problem doesn't.

And the question doesn't.

Can they actually do this?

If you want a tool that walks this for a real breakdown in your operation, I built one. Seven minutes. Walks you through the three rungs. Awareness, Ability, and Agreement. Applied to one specific failure you're sitting with right now. You leave knowing which rung is actually broken and what to do about it. No pitch. Free.

Take the AAA Diagnostic →  Here

Try it on the next conversation you've been avoiding. See what you find.

— Kwan