Ecology: Carrying Capacity

Every system operates within limits. Not all limits are visible — some only become apparent at the moment they are crossed, and by then the damage is already accumulating. The concept of carrying capacity (K) originated in population ecology, formalised through the logistic growth model: populations grow rapidly when resources are abundant, slow as they approach the ceiling, and crash or stabilise when they hit or exceed it. Arthur Tansley, who coined the term "ecosystem" in 1935, understood that any system is defined by the relationship between its components and their resource base. Howard Odum extended this to show that energy and material constraints are the ultimate governors of system scale.

The insight transfers directly beyond biology. Teams have a carrying capacity defined by coordination costs, management bandwidth, and information throughput. Platforms have carrying capacities bounded by network congestion, moderation costs, and trust erosion. Markets have carrying capacities constrained by willingness-to-pay, substitution, and regulatory tolerance. In all cases: the limit exists whether or not it has been named, and approaching it without awareness is how organisations walk into overshoot.

Your Process

Step 1: Define the System and the Resource Axis Name the system being analysed and identify the primary resource or condition that limits growth. The carrying capacity is always a constraint on something specific — not "capacity" in the abstract but a specific input, condition, or ceiling.