Your Team Doesn't Need the What Until They Believe the Why
By Atiba de Souza
The play that should have worked
Late in a game we were losing, we needed one first down to keep the drive alive. I called the play. The kid took the handoff and ran like his life depended on it. Everybody on the sideline was up, screaming, because the effort was real. He came up short.
We were half-celebrating the hustle and half-annoyed at the result, and then he said the sentence that changed how I coach: "I didn't know I needed to get a first down."
He wasn't lying and he wasn't making an excuse. Nobody had told him. We told him to run the ball. We never told him where the line was.
That's not a story about effort. Effort was never the problem. The problem was that we handed him a task and skipped the thinking that should have come with it.
Delegate thinking, not tasks
This is the whole of what I teach about building teams that act like owners instead of employees waiting for instructions: delegate thinking, not tasks.
Most delegation advice stops at the task. Write the SOP. Hand off the checklist. Watch it get executed. That works right up until the situation doesn't match the checklist, which is every situation eventually, and then the person holding the task has no thinking to fall back on, because you never gave them any.
Delegating thinking: handing someone the target and the reason it matters, not just the motion to perform, so they can still make the right call when the situation doesn't match the plan.
The kid had the motion. Run the ball. He didn't have the target. First down, that specific line, right there. One sentence, said out loud, before the snap, and the exact same effort gets him across it. Nobody said the sentence.
The order people get backwards
Here's where most leaders think they've solved it once they've heard this story: they go back and start stating the target loudly, in every meeting. Then they're confused when it still doesn't stick.
It doesn't stick because there's a step before the target, and it's the one nobody wants to do, because it's slower and it costs them something personal.
Steve Derrington's staff, Lyca, Stephanie, Mekka, had a data problem. Nobody was recording what they did or whether it worked. Lyca wanted it fixed. On paper it's a tracking problem: build the sheet, teach the team to fill it in, done in a week.
I told her it would take a year.
Eighteen months before Lyca asked for the fix, my own company had the same gap: nobody recorded what they did or whether it worked either. The fix she pictured taking a week took a year, not because the tooling was hard, but because the culture had to change in three managers before it could reach the team at all.
Not because the tooling was hard. Because the culture had to change in the three managers first, before it could reach the team at all. I used our own company as the example, because eighteen months earlier we hadn't been recording anything either. If I'd pushed the recording discipline straight at the team while the three of them weren't bought in yet, I'd have gotten compliance for a few weeks, a spreadsheet that looked good in a meeting, and then nothing. No data. Because they never believed it mattered, they just did what they were told until they stopped.
That's the order, and it's the opposite of what feels efficient: belief in the why has to exist in the people above the team before the what has any chance of surviving contact with the team. State the target to people who don't believe in it yet, and you get exactly what Lyca would have gotten. Compliance with an expiration date.
Why the why is the expensive one
Rank these honestly, because treating them as equally important is how you fail at both. The why costs more than the what, every time. Stating a target is a sentence. Building belief in three managers so the target survives past week three is a year of someone's life, told to them up front so they don't quit at month two thinking it isn't working.
I didn't get to tell Lyca "install the software" and walk away. I had to name that her staff's missing data was the same gap I'd had in my own company eighteen months earlier. That's the harder move, and it's the one that actually works: a company's chronic weakness is usually the leader's personal weakness, just running at scale. You don't fix it by writing the staff a new rule. You fix it by naming your own version of it out loud, because that's what earns you the right to ask them to change at all.
That's uncomfortable in a specific way. It costs you the version of authority that comes from never being wrong. It costs you the fast win, because a year is a real year, not a slogan. And it rewires something in how you lead: from "I hand down the correct instruction" to "I show them I've had the same gap, then I ask them to close it with me."
Most leaders skip this because naming your own gap feels like weakness in the moment they most want to look strong. It's the opposite. It's the only thing that makes the target you eventually state land on people who are actually listening.
When not to run the whole sequence
Don't run the full why-first sequence when the why is already shared and the only thing missing is the specific target. If your team already believes in the mission and just doesn't know the exact number, the exact deadline, the exact line on the field, skip straight to the sentence. Say the target, have them say it back, move. Building belief that already exists is wasted motion, and it's a convenient way to procrastinate on the fifteen seconds of clarity that would have solved it.
The sequence is for when the target keeps not landing no matter how clearly you state it. That's the signal the problem was never the what. It's that nobody upstream believes the why yet, and you're the one who has to go first.
What inconsistent and consistent actually look like
| Task delegated (no thinking) | Thinking delegated | |
|---|---|---|
| What's said before execution | "Run the ball" / "Start recording" | "We need that line, right there, one sentence" / "Here's why this matters, and here's my own version of the gap you're closing" |
| Who's convinced first | Nobody, the order goes straight to the team | The managers, then the team |
| What happens under pressure | Full effort, wrong target, or full compliance, no belief | Judgment that adjusts, because the person understands the target and believes it matters |
| Timeline you tell yourself | A week | A year, said out loud up front |
| What it looks like at week three | A spreadsheet that looks good in a meeting | Slower, and still there in month twelve |
The gate, at a glance
The target was never missing. The sentence stating it was. But the sentence only lands after somebody upstream has paid for the belief underneath it.
What Monday actually costs you
If the diagnosis is a target problem, Monday is easy. Stop before the snap, have each person say back what winning looks like in one sentence, and if the sentences match, you're clear to run it. That part takes ten seconds and I'm not going to pretend it's harder than it is.
But if what you're staring at is a belief problem, Monday isn't the day this resolves. It's the day it starts, and it won't be finished by Friday, or by the quarterly review, or by the point where someone above you starts asking why the numbers still aren't there. That's the part I told Lyca up front, because she needed to hear it before she committed, not after: a year, not a week, and the slow part is not the spreadsheet.
It will cost you the authority that comes from always looking like you already have the answer, because the move that works is naming your own gap out loud before you ask anyone else to close theirs. Most leaders won't do that on a Monday, because it doesn't look like progress, it looks like admitting something. The memo looks like progress. The year does not, not for months.
Do it anyway, and know what you're signing up for going in. That's the whole difference between the fix that survives past week three and the one that doesn't.
Questions