You Can't Install an Orchard

I've watched a lot of leaders try to install a culture.

They bring in a framework. They run the workshop. They post the values on the wall — sometimes literally — and then wait for something to change. When it doesn't, they bring in another framework. Run another workshop. And the cycle continues, each pass leaving the organization slightly more cynical than the one before.

What they're missing isn't a better system. It's an understanding of what they're actually tending.

You can't install an orchard. You cultivate one. And cultivation is a different discipline entirely — slower, less dramatic, and far more demanding than fixing things.

I have a client I've been working with for some time now. He is, by any operational measure, exceptional. The kind of leader who walks into a problem and walks out with a solution before most people have finished describing the situation. His metrics are strong. His instincts are sharp. He is, in the language his organization uses, a high performer.

He's also being considered for VP Operations. And the feedback giving his promotion pause is this: he's too direct, and he doesn't utilize his team.

Which means he's fixing things. He's just not growing anything.

I recognized him immediately — because I was him.

Early in my career, I was a problem solver. A lone ranger, if I'm being honest about it. I could walk onto a floor, read the situation, and make something better by end of shift. I got results. I got attention. My daily metrics looked good, and that external validation had become more important to me than I knew at the time. I was good at attacking what Deming would later help me understand as special cause — the specific, identifiable problems that flare up and demand immediate attention. I was very good at that.

What I was neglecting — what my client is neglecting — is common cause. The systemic, chronic, underlying conditions that no single intervention fixes. The soil, if you want to stay in the orchard. You can chase special cause your entire career and post impressive numbers. But you won't change the system. You'll just keep fixing the same orchard with slightly different tools.

There's something else worth naming, because I've seen it often enough to trust the pattern.

Leaders who are promoted for technical excellence frequently carry a quiet uncertainty about their leadership. They were hired — rightly — for what they could do. And now they're being asked to work through other people, which is a different skill set entirely, one that doesn't come with the same immediate feedback loop. So when a problem surfaces, something pulls them back toward what they know. They jump in. They fix it. It feels like contribution. It feels, if they're honest, like proof that they still have it.

What it actually does is bench the team, build dependency on one person, and send a signal — unintentional but unmistakable — that says: I don't trust you to handle this.

That's not a competence problem. That's an identity problem wearing the mask of competence.

The work of leadership culture isn't the dramatic intervention. It's the long tending. It's improving the soil — removing the toxins, whether those are broken processes, unspoken norms, or leaders who confuse activity with growth. It's finding the right seeds. It's knowing that what you plant this season you may not harvest for two or three seasons more. And it's understanding that the point isn't just this year's fruit.

The point is the next generation of keepers.

An orchard that outlives its planter doesn't happen by accident. It happens because someone made a decision — probably more than once, probably when the easier thing was to just go fix something — to tend instead. To develop instead. To trust the soil and the people and the slow, unglamorous work of cultivation.

That's what leadership culture actually is. Not a framework you install. An orchard you spend years learning how to tend.

A few things worth sitting with:

Where are you fixing when you could be growing? Think about the last time you stepped in to solve something your team was capable of handling. What pulled you back in — urgency, or something quieter? The answer is worth knowing.

What are you building that can outlast you? Your metrics tell you what the orchard produced this season. They don't tell you whether you're improving the soil. Take an honest look at the people around you — are they more capable than they were a year ago? Are they learning to read the trees, or are they waiting for you to read them?

What would it mean to tend instead of fix? Not abdication — tending requires more skill than fixing, not less. But the next time a problem surfaces, before you step in, ask: who on my team could grow by working through this? What would it cost me to let them? What would it cost them if I don't?

The orchard is always telling you something. The question is whether you're listening — or just harvesting.