The Zen of Phil Jackson: Lessons from the NBA’s Most Fascinating Coach

Your team is underperforming. Tensions are high. Two senior people won’t talk to each other. Someone keeps going rogue on decisions.

Most managers respond the same way: more meetings, clearer processes, team building exercises. Maybe bring in a consultant. Hope everyone starts acting like adults.

Phil Jackson won 11 NBA championships with teams full of massive egos and dysfunction. He didn’t do it with more structure. He did it by understanding something most managers miss.

Here’s what actually works.

Two types of leadership problems

Execution problems: add structure

The team doesn’t know who owns what. Decisions take forever. Work gets duplicated or falls through cracks. Basic coordination is broken.

This needs structure. Clear ownership. Defined processes. Someone needs to know what they’re responsible for and when things are due.

You’re not being controlling. You’re removing ambiguity. People can’t execute well when they don’t know what “well” means.

But most leadership problems aren’t execution problems.

Ego problems: remove yourself

Your best engineer thinks their way is the only way. Your designer and PM are in a power struggle. Someone’s trying to prove they’re smarter than everyone else.

Adding more structure makes this worse. More processes mean more opportunities for conflict. More checkpoints mean more chances to dig in.

Phil Jackson’s solution: give them less of you, not more.

The triangle offense

Jackson’s teams ran the triangle offense. It’s a system where there’s no single ball handler. No star making all the decisions. Everyone has to read the defense and make choices.

Sounds chaotic. Actually creates clarity.

Why it worked: Players couldn’t succeed individually. Kobe couldn’t iso-ball his way to a championship. Shaq couldn’t just demand the ball. They had to trust each other or lose.

Jackson didn’t convince them to trust each other through speeches. He created conditions where trust was the only option.

The management version: Stop being the decision maker.

When two people come to you with a conflict, don’t solve it. “You two figure it out and tell me what you decided.”

When someone wants approval on an approach, don’t approve it. “Use your judgment. You’re closer to this than I am.”

When a project is stalled, don’t step in and direct it. “What do you think needs to happen?”

This feels irresponsible. It’s the opposite.

What actually happens

First week: Panic. People are used to you solving things. They’ll escalate again. Send them back.

First month: Frustration. “Why won’t you just tell us what to do?” Because if you do, they’ll never learn to work together.

Second month: Something shifts. The two people who wouldn’t talk? They talked. They had to. The person going rogue? They started consulting others. They had to.

Not because you convinced them. Because you stopped being the escape hatch.

The one meeting that matters

Jackson’s teams had film sessions. Players watched themselves. Watched each other. No coach commentary. Just: here’s what happened.

You don’t need film sessions. You need one retrospective that actually works.

End of every project or sprint: “What happened? What should we do differently?”

Not: “Let me tell you what went wrong.”

Not: “Here’s my feedback on everyone’s performance.”

Just: What did we see? What do we think?

You facilitate. You don’t evaluate. The team evaluates itself.

Most managers talk 60% of the retrospective. Jackson talked maybe 10%. His teams figured it out themselves because they had to.

When to actually intervene

You’re not absent. You intervene in two specific cases.

Someone’s being destructive. Not difficult. Destructive. Undermining others. Creating toxicity. You remove them or you fix it directly. Fast. No process, no triangle offense. Some things don’t get delegated.

The team asks for direction. Not “tell me what to do” but “we’ve hit something genuinely unclear and need organizational input.” That’s your job. Answer it.

Everything else? They figure it out.

Why this is hard

Because it feels like you’re not leading. You’re used to being needed. Used to solving things. Used to being the one with answers.

Jackson’s teams called him “Zen Master” like it was a joke. It wasn’t meditation. It was discipline. The discipline to not step in. To let people struggle. To trust that struggle creates teams.

Your instinct when things are messy: take control.

The actual solution: let go.

The rule

If it’s an execution problem, unclear ownership, broken process, add structure.

If it’s an ego problem, conflict, territorialism, distrust, remove yourself.

Don’t add more management to ego problems. Don’t try to inspire your way out of execution problems.

Most teams are over-managed and under-led. Leading means creating conditions where people lead themselves.

That’s it. No vision speeches. No team building. Just: structure for execution, space for everything else.