I first heard the term "strip-mining" applied to teams from an engineering director at a mid-size fintech company. She'd just lost three senior engineers in two months. When I asked what happened, she didn't talk about compensation or competing offers. She said: "We were strip-mining them. We just didn't call it that."
Strip-mining in software isn't about tools or processes. It's about a mindset: extract maximum value from each person, measure throughput, and replace when depleted. It works until it doesn't — and when it breaks, it breaks fast.
Sign 1: Velocity Is Up, Satisfaction Is Down
This is the canary in the coal mine. When your sprint velocity charts keep climbing but your team's engagement is flat or falling, you're not becoming more efficient. You're extracting harder.
The pattern is familiar: same team, more output, less joy. Engineers who used to debate architecture now just close tickets. Standups that used to surface real problems now produce status updates. The work is getting done, but nobody cares about it anymore.
If your metrics are up and your people are down, you're not optimizing. You're extracting.
Sign 2: Knowledge Is Concentrated, Not Distributed
Healthy teams spread knowledge. Strip-mined teams hoard it — not because people are selfish, but because there's no time or incentive to teach. Senior engineers become bottlenecks not because they want to, but because nobody else was given the space to learn.
Ask yourself: when was the last time someone on your team learned something new because they had time, not because they were forced? If the answer is measured in quarters, not weeks, your soil is depleted.
Sign 3: Departures Cluster Around the Same Moment
In strip-mined teams, attrition doesn't follow a normal distribution. It clusters. Three people leave in six weeks. Then nothing for a year. Then four more.
Why? Because teams talk. When one person decides they've had enough, they tell the others. The decision to leave becomes contagious — not because people are followers, but because the conditions that pushed the first person out are still there. Everyone else was just waiting to see if it was them or the system.
The Cultivation Alternative
Cultivation isn't the opposite of productivity. It's the opposite of extraction. Cultivated teams ship more over time because they get stronger, not because they get squeezed harder.
The shift from extraction to cultivation is simple to describe and hard to do: invest in your people like you invest in your infrastructure. Not with perks and team-building. With time, autonomy, and real ownership over meaningful work.
The test: Would your best engineer be a better engineer in six months if they stayed? If you can't answer yes with confidence, you're cultivating by accident, not by design.