Clear ideas for complex systems
Latest posts
Systems Dynamics

Overshoot and Collapse: The Growth Pattern That Ends in Decline

Rapid growth against a shrinking resource, plus delayed feedback, produces overshoot and collapse. Here is how the pattern works.

Table of ContentsNavigate this article

    Some systems do not simply grow and level off. They grow, sail past the level they could sustain, and then fall hard. A population outstrips its food supply and crashes. A company expands faster than its ability to serve customers and implodes. This dramatic pattern, rapid growth followed by steep decline, is called overshoot and collapse, and it is one of the most important shapes of behavior in system dynamics.

    The anatomy of overshoot

    Overshoot happens when a growing quantity depends on a resource that is being used up, and there is a delay before the system feels the limit. During the growth phase, everything looks healthy. The limit is still far away, or its signals arrive too late to change course. By the time the strain becomes obvious, the system has already grown well beyond what the shrinking resource can support, and a correction is unavoidable.

    Why delays make it worse

    The crucial ingredient is delay. If a system felt its limits instantly, it would slow smoothly and settle at a sustainable level. Instead, feedback about the eroding resource lags behind the growth. Decision makers keep pushing, because the numbers still look good, right up until the moment they do not. The longer the delay, the higher the overshoot climbs, and the deeper the eventual fall.

    Common examples

    • A herd that multiplies during good years, then starves when it has stripped the grassland bare.
    • A startup that scales spending against projected demand that never fully arrives.
    • A fishery harvested faster than the fish can reproduce, collapsing after years of strong catches.
    • Groundwater pumped far beyond its recharge rate, thriving until the wells run dry.

    Avoiding the crash

    The way out is to see and respect the limit before the delay hides it. That means watching the state of the resource itself, not only the output it produces. It means slowing growth as the limit approaches rather than waiting for a signal that arrives too late. Systems that avoid collapse usually do so by building in early warnings and by treating the underlying resource as something to protect rather than spend. Growth that ignores its foundation is not strength. It is borrowed time.

    Overshoot and collapse is not a rare accident. It is the predictable result of fast growth, a hard limit, and slow feedback. Change any one of those three and the outcome changes with it.

    About the publisher

    Systems Thinking Hub

    We are experts in delivering clear, practical knowledge about systems thinking, complexity, and better decision-making.

    Discussion

    Join the discussion

    Your email address will not be published. Required fields are marked.