The Excuse Your Team Keeps Repeating Is Your Culture at Scale

You already know the sentence

You have heard it. Maybe this week.

"We didn't have time to log it."

"We didn't get the report in."

"The data wasn't there."

And in that moment you felt the heat rise, you looked at the person, and you heard yourself say something about accountability and expectations. Then you went back to your desk and quietly decided to remind them again next week.

Here is what I want you to see. The excuse is not the problem. The excuse is a readout. It is the most honest data your company produces, because it tells you exactly what your culture rewards and what it tolerates. You have been treating that readout as defiance when it was a report.

I know because I paid for that lesson twice, and both times the bill came with my name on it.

The data problem I priced at a year

Steve Derrington had a data problem. From where you are sitting it looks like a project. A tracking system, a few fields, a template, a week of setup.

I told Lyca it would take a year.

To explain why, I used our own company as the worked example. Eighteen months earlier, nobody here recorded what they did or whether it worked. Same business, same people, no data. The fix was never going to be the tracking, and it was never going to be the tooling.

The hard part was that the culture had to change in the three managers first. In Lyca, in Stephanie, in Mekka. Before it could reach the team.

Here is how I put it to them:

The thing I had to realize and understand is I had to change the culture between you, Stephanie, and Mekka. To get y'all to understand the importance of recording the data, and reporting the data. Which then had to permeate down into the team. Which is why it took so freaking long.

Read the middle of that again, because the hinge is right there. I did not tell those three how to record data. I told them the gap was between the three of them. Naming it out loud, to their faces, is what earned me the right to ask them to change anything at all.

If I had skipped that and pushed the recording discipline straight at the team while the three managers were not yet bought in, I would have gotten compliance for a few weeks and no data at all. Not less data. None.

That is why it took a year. Not the software. The conversation.

And the part I did not want to say out loud: the missing data was the culture I had created. Not a discipline problem my staff had. Mine. A company's chronic weakness is usually the owner's personal weakness at scale, and this one was mine, sitting in a spreadsheet nobody filled in. Own the gap and the fix becomes something you lead. Issue another rule and you have asked the same people to care about something you never cared enough to build.

The decision rule: delegate thinking, not tasks

Now the rule that decides what you do with the excuse, because everything above only works if you can tell two kinds of delegation apart.

Delegate thinking, not tasks: give the outcome and the reasoning, and let the person build the how. Hand someone a finished procedure and you have delegated a task. Hand them the reasoning and you have delegated the thinking.

Most delegation advice tells you to write the SOP and hand it off. Do that and you have delegated a task. You handed over your thinking and asked them to run it. An excuse is what you get when the task was delegated and the thinking never was, because the person has no ownership of the design and no good answer for the moment the design meets a busy Tuesday.

So when the excuse lands, your first question is not "who dropped the ball." It is: was the thinking ever delegated here, or did I hand over a task?

That one question sorts the excuse into four places, and each place has its own move. Never shown how? Train. Thinking was delegated and a real constraint is in the way? Fix the constraint. Task was delegated and the thinking never was? Audit the constant. Then hand the design back.

The constant I did not want to find

One of my stores needed six people to cover all the shifts. Six seats. Over two years I hired and lost two hundred people trying to fill them.

And I tried everything, because that is what you do. A different posting. Different interview questions. A different schedule. A different onboarding. A different pay structure. Every tactic you can name, and a few you probably cannot.

Nothing moved.

So I sat with it and asked the question I had been avoiding. What is the only thing that stayed the same through all of it? Through every hire, every exit, every tactic, every schedule, every conversation?

It was me.

Six seats. Two hundred people. Two years. The only constant in every one of them was me.

I was the thing that did not change. Once I could see that, the answer stopped being a mystery. That turnover was not a hiring problem. It was my own reactive leadership, showing up two hundred times in a row, in a different face each time.

Now bring it back to the sentence you keep hearing. A recurring excuse is not a person failing. It is a culture reporting. The constant behind the excuse is usually the leader, and you built that culture the same way I built that turnover, two hundred hires deep.

Naming your own version of it out loud is what earns you the right to ask anyone to change. Not a speech about standards. Not a new tracker. You, saying plainly that this has never once been made to matter. That is the difference between a leader issuing a rule and a leader taking responsibility for the environment the rule has to live in.

The four moves, and what each one costs you

Do these in order. Do not skip to four, because four is the one that feels like progress and changes nothing on its own.

1. Write the excuse down, word for word. Do not answer it in the meeting. "We didn't have time to log it" is a sentence, and sentences carry data. Answer it and you get an argument. Write it down and you get evidence. Here is the cost. The in-room correction. You have to sit there with the sentence in the air and let it stand, in front of everyone, without taking the shot. That correction is a satisfying little hit of authority, and giving it up feels like losing the room. You are not losing the room. You are buying evidence instead of a moment. The rewiring: react and correct becomes collect and read.

2. Ask the one question. What would have to be true for this to be possible? This costs you the authority of having the answer. The second you ask, the floor belongs to them. They may hand you something you do not like. It may implicate your schedule, your budget, or a decision you already made and would rather not reopen. Ask anyway, because the answer tells you which excuse you are holding. If they can describe what would have to be true and it is real, you have a constraint to fix. If they cannot, the thinking was never delegated, and what you have is a training gap or an ownership gap. Two different problems, two different fixes, and you cannot tell them apart without asking. The rewiring: being the answer becomes asking the question.

3. Audit the constant. Before you change a person, a tool, or a deadline, ask what stayed the same every other time this failed. If the answer is you, say it out loud, to them. I had to say it to myself after two hundred people, and it is the least comfortable sentence in this article. This costs you the identity hit, and it costs you the fast answer. Naming your own gap means you can no longer promise a fix by Friday. So when someone asks you to install data discipline, or a reporting habit, or a new way of working, you size it as a culture change and you say up front that it is a year, not a sprint. Say that in a room full of people who wanted a quick win and you will feel the room cool. Pay it anyway. The alternative is a year of your life spent replacing people. The rewiring: change others becomes change self.

4. Hand back the thinking. Tell them the outcome you need and let the design be theirs. If the work will touch a whole team, hand it to the managers before the team, because the culture changes in them first. That is not a courtesy. That is the mechanism. This costs you control of the how. They will build something you would not have built. The first version will probably be worse than the version in your head, and you have to let it be worse, in public, while it gets better. That is the price of a process they will defend. You can shrug at a process you were handed. You cannot shrug at your own design. The rewiring: delegate tasks becomes delegate thinking.

The ranking. Which of these is minor? The tool you eventually pick. The template, the dashboard, the fields. Which one is not optional? Move three. If you do nothing else here, do move three, because one, two, and four all collapse when the constant is still standing in the room pretending to be a bystander.

The two leader versions, side by side

The framework at a glance

When NOT to run this play

Three times this is the wrong tool, and the decision rule tells you which one you are in.

If the person was never shown how, that is a training gap, not a culture gap. The thinking was never delegated because nobody taught it. Train them. Do not run an identity audit on someone who was never shown the work.

If it happened once, you do not have a constant. You have noise. Wait for the repeat before you go hunting for a pattern, or you will find one that is not there and blame the wrong thing.

If the excuse is actually true, fix the constraint and see what remains. Some excuses are accurate reports about a system that makes the right behavior impossible. Treating a real constraint as a culture problem is how leaders lose good people.

And do not perform the self-audit. Naming your own gap earns you the right to ask for change. Turning it into a speech about how humble you are spends the credit before you use it.

What to do Monday

Next time the sentence shows up, do not answer it. Write it down.

Ask what would have to be true for it to be possible, and listen for whether you delegated thinking or only a task.

Then go find the constant. If it is you, say so out loud, to them, before you ask them for anything.

Then hand them the outcome and let the design be theirs.

Slower than a reminder? Yes. It is also the only version of this where the excuse does not come back wearing a new face next quarter.

The sentence you keep hearing will not stop until the constant does. You already know who that is.