Organizational Soil

There is a word that appears in almost every organizational conversation I have ever been part of, and it is the least useful word in the English language for: the purpose it is being asked to serve.

The word is culture.

I have sat in boardrooms where culture was named as the cause of every problem and the solution to every initiative. I have watched senior leaders commission culture assessments, culture transformation programs, culture change consultants. And I have watched nearly every one of those efforts produce something far short of what was intended.

I do not think these leaders were wrong to care about what they were pointing at. I think they were using the wrong word for something real.

Culture, as the word is typically used, is too big and too vague to touch. It explains everything and therefore nothing. When a senior leader says "our culture is the problem," they have named something without locating it. They have no lever to pull.

You cannot fix culture. You can fix conditions.

And conditions, unlike culture, are visible, specific, and changeable.

What Soil Does

When I think about what organizations call culture, I think about soil.

Soil is the medium in which things grow. It has properties: composition, moisture, pH, compaction, nutrient density: that determine what can survive in: it and what cannot. You can plant the same seed in ten different soils and get ten completely different yields. The seed has not changed. The farmer has not changed. The soil has.

Organizations work exactly this way.

Take a talented, motivated person: someone who produced exceptional results in their previous role, who came with a strong track record and genuine capability. Put them in an organization with compromised soil, and within eighteen months they look like a different person. They are slower. More careful. Less willing to raise: the hard question in the meeting. Their energy has shifted from building to navigating.

The leader who hired them looks at the result and concludes something is wrong with the person.

The builder looks at the result and asks what the soil is doing.

British Cycling offers one of the clearest institutional examples of this principle. For most of the twentieth century, British cyclists were largely irrelevant on the world stage. Then in 2003, a coach named Dave Brailsford was appointed to lead British Cycling, and he brought with him a concept he called: the aggregation of marginal gains. Brailsford did not import new athletes. He changed the conditions. He brought in a sports psychologist. He hired a surgeon to teach proper handwashing. He changed the pillows riders slept on. He optimized nutrition, recovery, and training surfaces. He made hundreds of small changes to: the environment in which his athletes were developing.

Within five years, British Cycling won sixty percent of the gold medals available in track cycling at the Beijing Olympics. Within ten years, British riders had won five of the previous six Tour de France titles.

The athletes were not new. The soil was.

When one field thrives and another struggles, the first question is never: what is wrong with the seed. The farmer asks about moisture. About pH. About what the soil has been growing for the past five years.

What Healthy Soil Produces

I have worked in organizations with healthy soil, and I have worked in organizations with deeply compromised soil, and the difference is palpable within the first hour.

Healthy organizational soil has a quality I can only describe as permission. Not permission in the bureaucratic sense: not the approval-and-sign-off kind. A deeper kind. The sense that things are allowed to be real here.

Ideas can grow. People raise them without first calculating whether raising them will be received as criticism of the current approach. Problems can grow visible. People name difficulties early, while they are still small, because the environment has taught them that naming a problem promptly is valued: not punished. People can grow. Someone tries something that does not work, and the conversation that follows is about what was learned rather than who is responsible. And direction can grow shared. People in different parts of the organization, doing different work, describe the same priorities in similar language, without having coordinated their answers.

That is healthy soil. You feel it when you walk into it. The conversations are different. The questions are different. The quality of the silence in a meeting is different.

You feel it leave when the conditions that produced it are allowed to erode.

The Managed Conversation

Unhealthy organizational soil is just as recognizable, and just as consistent in what it produces. The most common signal is what I call the managed conversation.

A managed conversation is one in which at least one person in the room is saying something different from what they actually believe. They are performing agreement. They are offering the answer they have calculated will be received well rather than the answer that is true.

I have sat in meetings where an executive asked for honest input and every person in the room told them what they calculated the executive wanted to hear. Every one of those people was capable of honesty. Every one of them wanted to work in an organization that moved well. Every one of them had the information that, if offered honestly, would have changed the decision in the room.

The soil taught them not to.

Unhealthy soil does this gradually, through a series of experiences that collectively communicate: honesty is not safe here. It rarely happens through, any single dramatic moment. It happens through the accumulation of small signals: the idea that was dismissed, the problem that was punished for being raised, the person who spoke up and watched nothing change.

The soil teaches. It is always teaching. The question is what it is teaching people to do.

What organizations say about themselves and what the organizational environment actually produces are two different things. The environment always wins.

Blaming the Seed

The seed-blaming instinct is nearly universal in organizational life. The employee who is not producing becomes a performance problem rather than a conditions problem. The team that cannot execute becomes a talent problem, rather than a design problem. The leader who cannot deliver becomes a capability problem rather than an environment problem.

The diagnosis is almost always wrong. And because the diagnosis is wrong, the intervention fails. You cannot fix a conditions problem by improving the seed.

Social psychologists call this the fundamental attribution error. Ross and Nisbett, in The Person and the Situation (1991), documented what decades of research had confirmed: observers consistently attribute behavior to the individual while underestimating the power of the situation. We are wired to look at the person rather than the environment the person is operating in. It takes deliberate practice to override that instinct.

The builder-leader has learned to override it. When performance is low, the first question is not what is wrong with these people. It is: what have I built: that makes it difficult for people to do what I need them to do?

That second question is harder. It puts the leader inside the problem rather than outside it. But it is the question that leads to real change. Because you cannot change what you are not willing to examine.

Farming Half as Good as You Know How

A young agronomist was driving through rural Kentucky when he pulled over beside an old farmer working a field that was clearly underperforming. The agronomist stepped out of the car and offered some advice.

The old farmer looked up. He thought for a moment. Then he said: "No, son. I ain't farming now half as good as I know how."

I have thought about that sentence for a long time. The farmer was not admitting ignorance. He was not saying he did not know what better farming looked like. He was saying that he already knew dozens of things he could do differently: and: the limiting factor was not knowledge. It was conditions. He did not have the equipment, the capital, the labor, or the time that better farming would require.

Most organizations I have worked with are in exactly that position. They are not operating half as well as they know how. Not because they lack ideas or ambition or capable people. Because the conditions have not been built to allow: what they know to be expressed.

That distinction changes everything about what the leader's job is.

Farmers Do Not Pull on the Corn

Every farmer understands this: you cannot make crops grow faster by tugging on them. You cannot impose a timeline on a biological process. What you can do is optimize the conditions, moisture, nutrients, light, drainage, and then get out of the way.

Leaders do what farmers never do. They pull on people. They push harder, demand faster, increase pressure when results are not arriving on schedule. And then: they are surprised when the crop does not respond.

I have sat in rooms where senior leaders described their most recent initiative to improve performance. They have added measurement. They have increased reporting cadence. They have set clearer expectations. They have escalated consequences. And results are still flat.

I ask them: what has changed about the soil?

The question is not always well received. But it is always the right question.

What You Can Change

You cannot change people. Not fundamentally, not by force of leadership will. You can create conditions that allow people to become more fully themselves. You can remove the constraints that are suppressing capability that was always there. You cannot substitute your will for their own.

You cannot mandate culture. You cannot declare that from this point forward people will be innovative, or collaborative, or candid. Declarations change: what people say. They rarely change what people do.

What you can change is soil.

You can change what gets rewarded and what gets ignored. You can change the distance between a decision and the person with the knowledge to make it well. You can change what happens when someone names a problem early: whether the messenger is thanked or quietly punished. You can change what happens when something fails: whether the conversation is about learning or about blame.

None of those changes are dramatic. None of them make headlines. None of them appear in the quarterly earnings call. But they change the soil. And the soil changes everything that grows in it.

My father spent a great deal of his working life thinking about what the ground needed before he could build on it. Not what he wanted to build: what the ground required first. The drainage. The compaction. The load-bearing capacity. The invisible infrastructure that would determine whether everything above it would hold.

That is the builder's work. Not managing what grows. Tending what it grows in.

Managers manage people. Builders design environments.