You Explained the Why. Your Team Still Has No Idea What They’re Doing.

You’re Not Failing Your Team. You’re Just Not Feeding Them.

Photo by Alexandru Acea on Unsplash

It hits 6pm and my partner asks me: “What’s for dinner?”

I don’t know, I say.

He disappears back into his office. At 7pm he shows up again, opens the fridge, and starts moving things around — a container here, some leftover rice there — not really cooking, just… looking. Hoping, maybe.

But are we eating dinner? I ask.

“Yes,” he says, turning around like I’d just asked something obvious. “What are we making?”

And there it is. The question lands on me like it always does. I go to the kitchen, scan the fridge, flip through the mental recipe book I’ve built over years of figuring it out, and start cooking. He waits. Patient enough, but watching — the way people watch someone parallel park — like I once again hold the answer to a question nobody wrote down.

And while I’m cooking, a thought creeps in that I can’t shake:

We can’t even agree on what’s for dinner — and yet we expect our teams to figure out how to hit goals we never set them up to achieve.

The Two Beliefs That Are Both Right (And Somehow Making Things Worse)

There’s a tension in leadership that I find fascinating, and also a little maddening.

On one side, you have the belief that explaining the why is everything. That if people understand the purpose behind the work, they’ll move mountains. And there’s truth in that.

On the other side, you have something Steve Jobs said — that “it doesn’t make sense to hire smart people and tell them what to do. We hire smart people so they can tell us what to do.” And there’s truth in that too.

Both beliefs are real. Both are valuable. And somehow, together, they’ve quietly created two problems that are quietly destroying teams everywhere.

The first: leaders who overcommunicate the why until it becomes noise — long documents, all-hands meetings, Slack messages about the vision, follow-up emails about the Slack messages — until the team is drowning in context and starving for clarity.

The second: leaders who hire talented people, hand them a goal, and step back — because they trust them, because they’re smart, because that’s what good leaders do — and then wonder six months later why nothing is moving.

Here’s the thing neither camp wants to admit: the why doesn’t work without clarity, and trust doesn’t work without structure.

And the missing piece — the one almost nobody talks about — is this: setting your team up for success.

The Scientist Who Almost Saved the Ocean

Let me tell you a story.

A visionary scientist discovered a breakthrough — a real, working method to remove plastic from the ocean. He secured funding. He got the green light. And he did what every ambitious leader does: he hired an exceptional team: An accountant. An engineer. A business strategist. A communications director…

He gathered them in a room, looked them in the eyes, and told them:

“By 2028, we will clean the Atlantic Ocean. Every piece of plastic, gone. This matters because future generations will inherit a dying sea if we don’t act. Humanity is counting on us.”

The room was electric. You could feel it.

And then he said: “I trust you completely. I know you’ll figure it out.”

And he meant it. Every word.

The team left the room energized. Each person went to their desk and started doing what they do best. The accountant began modeling costs. The engineer started researching filtration systems. The strategist mapped out partnerships. The communications director drafted a press release.

Nobody talked to each other outside the usual… Not because they didn’t want to — but because nobody had said who was supposed to coordinate them as a team. Three weeks in, the CEO checked in. “Have we started procurement on the first filtration units?”

Silence.

The accountant looked at the engineer. The engineer looked at the strategist. The strategist looked at the communications director. Each one privately thinking: I assumed that was someone else’s job.

The CEO asked again. A little more edge in his voice this time.

Nobody answered. Not because they were irresponsible — but because responsibility had never been assigned. The room felt the weight of that failure, and without a word being said, something shifted. Trust quietly cracked.

It happened again the following month. And the month after that.

By month four, the CEO was holding weekly tracking meetings .He started re-explaining the mission more often, sometimes passionately, sometimes desperately, like repetition might do what clarity hadn’t. He wrote a six-page document about why clean oceans matter. He shared it on a Friday afternoon.

The team read it. They already knew why it mattered. They had always known.

What they didn’t know — what nobody had ever told them — was who was responsible for what, how decisions should be made together, and what the actual path from today to 2028 looked like.

The project eventually stalled. Not from lack of talent. Not from lack of passion. Not because the CEO didn’t explain the why.

It stalled because nobody told them what they were having for dinner.

So What’s the Actual Difference?

Let’s slow down here, because I think this is where leaders get lost — in the language.

What’s the difference between setting your team up for success and micromanaging?

One tells the engineer how to be an engineer. The other tells the engineer what they’re responsible for, what decisions are theirs to make, and how their work connects to everyone else’s. The engineer already knows engineering. They don’t need you for that. They need you to draw the map, not hold the wheel.

What’s the difference between independence and autonomy?

This one is subtle but it changes everything.

Independence is freedom from — from control, from coordination, from needing to share context or account for others. It feels like trust. It looks like trust. But in a team, it’s actually isolation. AND this doesn’t work!

Autonomy is something different. Autonomy is the ability to make decisions and take action within a shared context — with clear responsibilities, clear boundaries, and a genuine accountability to the people around you. Autonomy is what makes teams scale. It’s a psychological need and an organizational necessity. Without it, people feel controlled. But without structure, autonomy collapses into chaos — talented individuals all heading in slightly different directions, each convinced they’re doing the right thing.

What we see in most teams isn’t autonomy. It’s independence. And independence, in a team context, is one of the quietest reasons teams fall apart.

The Three Things You’re Probably Skipping

You already know to explain the why. You already know to trust your team. But here’s what you also need — and what I’d ask you to really sit with:

1. Make responsibility visible, not implied.

Not in a meeting. Not in a document nobody will re-read. Somewhere clear, permanent, and shared. Who owns what — not in general terms, but specifically: at each stage of this project, who is responsible for what, and where do those responsibilities hand off? People regularly assume others are handling things. Sometimes the same task is owned by three people. Sometimes it’s owned by no one. This isn’t a character flaw. It’s what happens when clarity is skipped.

2. Give them a skeleton, not a script.

You don’t need to plan every meal of the week. But your team shouldn’t be opening the fridge every Monday wondering what they’re supposed to be doing and what they should buy. A basic framework — here’s where we’re starting, here’s where we’re going, here are the milestones, here’s how we’ll make decisions together — gives people a structure to move inside. Without it, they spend more time coordinating, second-guessing, and meeting about meetings than actually building anything.

3. Remove the noise before adding more signal.

Here’s a thing I’ve noticed: most teams don’t suffer from too little communication. They suffer from too much of the wrong kind. Your team has almost certainly read your documents. They understand why the mission matters. What they’re quietly drowning in is the list of urgent tasks that changes weekly, the side conversations that spawn new priorities, the meetings that interrupt the work that was supposed to come from the last meeting.

More vision doesn’t fix unclear responsibility. Another all-hands doesn’t replace a clean process. And no matter how many times you open the fridge hoping a pizza will appear — it won’t.

The Part That Actually Matters

There’s something that only you, as a leader, can see: the full picture.

L E T M E S A Y T H A T A G A I N

There’s something that only you, as a leader, can see: the full picture.

You know what each person was hired for. You know what they’re capable of, what they’re working toward, what keeps them up at night. You know how the pieces fit together — because you put the team together.

That visibility is a privilege. And it comes with a responsibility that doesn’t go away just because you explained the vision or gave people space to work.

You are responsible for the success of the project and the success of each person on it. Not because you’ll do the work for them — but because without that foundation, no amount of talent, trust, or passion will get you to 2028.

Setting a team up for success isn’t the opposite of trusting them. It’s what trust actually looks like in practice.

“A coach is someone who tells you what you don’t want to hear, who has you see what you don’t want to see, so you can be who you have always known you could be.” — Tom Landry

And one last thought: if your team can consistently answer “what are we doing this week and why does it matter?” without calling a meeting — you’re probably doing this right.

If they can’t — well.

You know what to make for dinner.

If this resonated, follow me here on Medium. I write about the things in leadership that are obvious in hindsight and invisible in the moment — usually while cooking.