What ecology’s carrying capacity theory can teach us about detecting collapse before it happens.
In 1944, 29 reindeer were introduced to St Matthew Island off the coast of Alaska. There were no predators. There was abundant lichen. By 1963, the population had grown to around 6,000. Then, in a single winter, it crashed to 42. The island looked like a success story right up until it became a catastrophe.
No individual reindeer could see what was happening at the population level. No single warning moment announced the collapse. The environment’s carrying capacity, its ability to sustain that population, had been silently, steadily, exceeded.
I see the same pattern play out in technology organisations every year. And the most unsettling part? The warning signals were always there. We just didn’t know how to read them.
What Carrying Capacity Actually Means
In ecology, carrying capacity is simply the maximum population size an environment can sustainably support given its available resources: food, water, space, nutrients. It isn’t a fixed ceiling that flips from green to red. It’s a threshold that populations approach gradually, expressing warning signals long before the actual collapse.
Those signals follow a predictable sequence. Growth slows even as inputs remain constant. Internal competition intensifies, individuals competing with each other rather than with external threats. Stress responses emerge: reduced reproductive success, greater disease susceptibility, behavioural changes. And then, often suddenly, collapse.
The critical insight is this: carrying capacity violations don’t announce themselves loudly. They accumulate quietly, then express suddenly.
There’s another concept worth understanding here, called overshoot. This is when a population exceeds carrying capacity before the feedback mechanisms can correct the trajectory. It happens because there’s a lag between resource depletion and population response. The reindeer kept reproducing because no individual animal could perceive the collective consumption rate. By the time the signal was visible, the damage was irreversible.
The Same Dynamics Play Out in Technology
Technology environments have carrying capacities too. The resources just look different: engineering capacity, cognitive load, architectural flexibility, organisational attention, psychological safety, and the informal connective tissue of shared knowledge and trust that allows complex systems to actually function.
All of those resources have limits. All of them can be depleted faster than they regenerate. And when they are, the warning signals are remarkably consistent with what ecologists observe in stressed populations.
Slowing throughput despite constant input
When a team is adding engineers but delivery velocity isn’t improving( or is declining) this is the technology equivalent of a population growth curve flattening as it approaches K. The environment can no longer convert inputs into outputs at the same rate. Something is constrained. Most organisations respond by hiring more people, which is the equivalent of introducing more reindeer to St Matthew Island.
Intensifying internal competition for shared resources
When teams are fighting over the same platform components, the same senior engineers, the same deployment pipelines, the same data infrastructure — when internal negotiation consumes more energy than actual delivery — carrying capacity pressure is expressing itself organisationally. The system is competing with itself. Ecologists call this the most damaging form of competition: not battles with outside rivals, but the draining friction of a population at war with its own members.
Rising incident rates and slower recovery
Systems under capacity stress show elevated failure rates not because they’ve been changed, but because accumulated load has pushed them beyond their sustainable operating range. Mean time to recovery lengthens because the cognitive and operational resources needed for rapid response are themselves depleted. This is stress physiology at the organisational level.
When knowledge quietly concentrates in one person
In ecology, stressed populations show reduced redundancy. Specialist individuals become critical single points of failure. In technology organisations, this manifests as the gradual concentration of critical knowledge in fewer and fewer people, as the system optimises for short-term throughput by quietly eliminating the ‘expensive’ redundancy of cross-training and documentation.
Cultural stress responses
Perhaps the most important and most ignored signal of all. In animal populations approaching carrying capacity, behavioural changes precede physiological collapse. Aggression increases. Cooperative behaviour decreases. In organisations, this looks like declining psychological safety, increased blame culture, reduced willingness to flag problems early, and a gradual retreat into siloed, defensive behaviour. People stop sharing information freely because information has become a scarce competitive resource.
There’s a particular version of this worth watching for in technology: the slow overloading of foundational systems. An API, a data platform, a shared service, each new team that builds on it adds what feels like a modest, reasonable dependency. But the load accumulates invisibly. No single addition tips the balance. And then, without warning, the whole thing becomes brittle. Not because anyone made a bad decision, but because nobody was watching the collective weight.
What You Can Actually Do About It
The good news is that ecology has spent decades developing sophisticated approaches to detecting at-risk populations before collapse occurs. The core principle translates directly: instrument for leading indicators, not lagging ones.
Lagging indicators (production incidents, delivery failure, staff turnover) tell you that carrying capacity has already been violated. You need signals that tell you you’re approaching the threshold, not that you’ve already crossed it.
Track the ratio of planned to unplanned work over time
Rising unplanned work is one of the clearest signals of accumulated capacity pressure. When the proportion of reactive, firefighting work grows relative to planned delivery, the system is telling you it no longer has the spare capacity to absorb disruption. This is a measurable metric, not a feeling. Track it consistently.
Map cognitive load distribution across teams
Concentration is a warning signal. When critical knowledge resides in one or two people, when certain teams are perpetually overwhelmed whilst others are underutilised, when the informal network through which things actually get done has narrowed to a few key nodes — these are ecological red flags. The formal org chart tells you little. The informal flow of knowledge and decision-making tells you everything.
Age your deferred decisions
Decisions that keep getting deferred are usually deferred precisely because the system lacks the capacity to address them. Create a simple register of decisions that have been postponed more than once. Their age and accumulation is a direct proxy for capacity pressure. When this list starts growing, you’re approaching a threshold.
Monitor the net rate of dependency creation
Track how quickly new connections and dependencies are being created relative to how quickly old ones are being retired. In healthy ecosystems, new growth and natural decomposition exist in balance. In technology systems, dependencies almost always accumulate faster than they’re retired. When the ratio becomes extreme, the system’s architectural carrying capacity is under serious pressure.
Design in enforced regeneration before depletion, not after
This is the most important structural principle. Natural ecosystems that persist over geological timescales contain built-in mechanisms (seasonal cycles, disturbance regimes, predator-prey dynamics) that prevent any single population from consuming resources faster than they can regenerate. Technology systems need designed-in equivalents.
That means building automated checks that surface capacity pressure before it becomes critical — think of them as ecological sensors embedded in your systems. Team structures that explicitly limit cognitive load rather than allowing it to accumulate indefinitely. And investment in regeneration — technical debt reduction, knowledge redistribution, platform modernisation — treated not as optional maintenance squeezed into spare capacity, but as the ecological equivalent of a fallow period: essential for future productivity.
The St Matthew Island Lesson
Every technology leader should keep the St Matthew Island story in mind. Not as a cautionary tale about reindeer, but as a precise model of what happens when a system expands into available capacity without any mechanism for detecting or responding to the limits of that capacity.
The island looked like a success story right up until it became a catastrophe. Many technology programmes follow exactly the same trajectory (impressive growth metrics, accelerating investment, confident roadmaps) whilst the leading indicators of carrying capacity pressure accumulate quietly and unread in the background.
The difference between organisations that navigate disruption and those that collapse under it is always about strategy, talent, or funding. It’s about whether anyone was paying attention to the signals that the environment was telling them, long before the environment stopped being able to support what they’d built.
Ecology has been solving this problem for 3.8 billion years. We’d do well to start listening.
If this way of thinking resonates with you, I’m developing these ideas and more in my forthcoming book Digital Ecosystems, Naturally Resilient — which applies rigorous ecological science to enterprise technology strategy. I’d love to hear what carrying capacity signals you’re seeing in your own systems. Drop a comment below.
The views and opinions expressed here are entirely my own and do not reflect the position of any organisation I work for or am associated with.