Every engineering team has soil underneath it.

Not metaphorical soil; real soil. The accumulated conditions — cultural, structural, relational — that determine what can grow there and what can't. Most teams don't know their soil type. They know their output. They know their velocity. They know whether this quarter's roadmap shipped. But the soil? They assume it's fine until something dies.

The agricultural metaphor isn't poetic; it's diagnostic. Farmers don't wait for the crop to fail before checking the soil. They test it, they amend it, they rotate it. They know that the visible plant is the last indicator, not the first.

I developed this framework from a talk I gave called The Soil Under Your Team. It started as a way to make the cultivation concept concrete, and it turned into something I use every time I walk into a new organization.

The Four Nutrients

Healthy soil requires four things. Deplete any one of them and the whole system weakens. Deplete two and you're in crisis. Deplete three and you're wondering why nobody told you the team was dying.

Nutrient One: Tall Stalks (Technical Excellence)

In a field, tall stalks are the visible sign of health. In a team, they're the engineers who can solve the hard problems, who know the system deeply, who make the rest of the team better by proximity.

Tall stalks aren't just your senior engineers. They're the people who raise the ceiling for everyone else. When they leave, the whole field gets shorter. When they're depleted, the whole field gets weaker.

Here's what depletes tall stalks: using them as the answer to every hard problem instead of growing more tall stalks. The "let's ask Sarah" pattern where Sarah becomes the bottleneck, the crutch, the person who can't take a vacation because the system relies on her being available.

Cultivation means identifying your tall stalks and asking: are we growing more, or are we burning the ones we have?

Nutrient Two: Ground Cover (Psychological Safety)

Ground cover prevents erosion. It holds the soil in place during storms. In teams, psychological safety is what keeps people from leaving when things get hard.

Not comfort. Not absence of conflict. Safety. The confidence that you can say "I don't know" without penalty. That you can raise a concern without retribution. That you can fail without becoming a failure.

Teams with poor ground cover erode fast. One bad quarter, one difficult reorg, one toxic hire, and the soil starts washing away. People don't leave because of the storm; they leave because the soil wasn't held in place.

Ground cover is built in small moments. The manager who responds to a missed deadline with "what do we need to fix?" instead of "what went wrong?" The senior engineer who admits uncertainty in a meeting. The team ritual that celebrates learning from failure.

These moments seem trivial in isolation. They're the difference between a team that weathers storms and one that washes away.

Nutrient Three: Nitrogen Fixers (Knowledge Transfer)

In agriculture, nitrogen fixers are plants that improve the soil for others. Legumes pull nitrogen from the air and make it available to neighboring plants. In teams, nitrogen fixers are the people who make others better through proximity.

They're not always the best engineers. Sometimes they're the best teachers. The person who writes documentation that actually gets read. The person who answers questions in public channels so the answers accumulate. The person who pairs with juniors not as a burden but as a practice.

Nitrogen fixers are invisible in most performance reviews because their impact is indirect. They make the soil richer for everyone else. Remove them and the whole field starves slowly, nobody knows why.

Organizations that optimize for individual heroics deplete their nitrogen fixers. Why fix the soil when you can just hire more fertilizer? But fertilizer runs out. Nitrogen fixers compound.

Nutrient Four: Pollinators (Cross-Functional Connection)

Pollinators move between plants, carrying what one has to what another needs. In teams, they're the people who bridge silos. The engineer who understands product context. The PM who can read architecture diagrams. The designer who speaks fluent API.

Pollinators are deceptively powerful because they make the system coherent. Without them, each function optimizes locally and the overall product becomes incoherent. Engineering ships fast features that product didn't prioritize. Product asks for things engineering can't build. Design creates experiences that don't match technical constraints.

The cost of poor pollination isn't visible in any single team's metrics. It shows up in the product. In the user experience. In the technical debt that accumulates because nobody was carrying context between decisions.

Pollinators need time to move between functions. That time looks like overhead to managers optimizing for individual utilization. It's not overhead; it's architecture.

The Deep Roots Layer

There's a fifth element that doesn't show up in the four nutrients because it's not a nutrient; it's the foundation.

Deep roots.

In agriculture, deep roots access water and minerals that surface roots can't reach. They anchor the plant against wind. They're invisible most of the time; you only see them when you dig or when the storm comes.

In teams, deep roots are the accumulated trust, shared history, and mutual understanding that lets a team move fast without breaking things. You can't build deep roots in a quarter. You can't hire them. You grow them, slowly, by staying together through hard things.

Teams that reorg every six months never develop deep roots. Teams that treat people as interchangeable resources never develop deep roots. Teams that optimize for short-term flexibility sacrifice the long-term stability that deep roots provide.

The organization that rotates people every 18 months for "career development" is harvesting the crop and wondering why the soil gets poorer every year.

Reading Your Soil

Here's the diagnostic. Ask these questions honestly:

Tall stalks: Who raises the ceiling for this team? Are we growing more, or burning the ones we have?

Ground cover: Can people here say "I don't know" without penalty? Can they fail without becoming failures?

Nitrogen fixers: Who makes others better through proximity? Do we value that, or do we only value individual output?

Pollinators: Who carries context between functions? Do we give them time to move, or do we treat that time as overhead?

Deep roots: How long has this team been together? What have they survived? What trust have they accumulated?

If you can't answer these, you don't know your soil. And if you don't know your soil, you're farming blind.

The Cultivation Assessment

I use a simple cultivation assessment when I walk into a team:

Rate each nutrient 1-5. Not relative to some ideal team in a blog post; relative to what this team needs to do what it's trying to do. A team building critical infrastructure needs more tall stalks than a team running marketing automations. A team in rapid growth needs more nitrogen fixers than a mature maintenance team.

The goal isn't a perfect score. The goal is honesty about what's depleted and a plan to amend it.

A team with 2/5 ground cover isn't failing; it's eroding. A team with 1/5 pollinators isn't broken; it's incoherent. The assessment gives you language for what you already feel but couldn't name.

What Healthy Soil Feels Like

You can feel soil health. Healthy soil is loose, fragrant, alive with microorganisms. Unhealthy soil is compacted, sour, dead.

You can feel team health too. Healthy teams move with coherence. Decisions make sense in retrospect. People know what's expected without being told. Conflict happens and resolves. There's margin for learning, for experimentation, for the thing that wasn't in the roadmap.

Unhealthy teams feel different. Everything requires explicit coordination. Decisions seem arbitrary. People are careful in ways that cost energy. There's no margin; every sprint is a sprint to survive.

The feeling is data. Trust it. Then test the soil to find out why.

Amendment, Not Replacement

Here's what you don't do: you don't fire the team and hire a new one. That's not cultivation; that's starting over on depleted soil.

You amend. You add what's missing. You reduce what's toxic. You give it time.

Tall stalks depleting? Stop using them as the answer to everything; grow more through deliberate mentorship. Ground cover thin? Create small moments of safety and let them accumulate. Nitrogen fixers invisible? Change what you measure so knowledge transfer counts. Pollinators absent? Give people time to move between functions. Deep roots shallow? Stop reorging and let people stay together.

None of this is fast. None of it shows up in this quarter's metrics. All of it compounds.

The Question Underneath

The framework isn't really about soil. It's about a question: what are we growing here?

Most teams can't answer. They're shipping features, hitting OKRs, moving tickets across boards. They're not cultivating anything; they're extracting. And extraction depletes soil whether you name it or not.

The diagnostic is the first step. The hard part is what comes after: choosing to cultivate in a system that rewards extraction.

That's the work. That's always the work.