Home / Core building blocks / Nonlinearity

Core building blocks

Nonlinearity

Small changes can have huge effects, and big changes can have none - systems rarely respond in proportion

Also known as: Disproportionate response, Non-proportional effects

THE IDEA

The world doesn’t do straight lines

Most of us think in straight lines by default. Push twice as hard, get twice the result. Invest twice the money, get twice the return. Add twice the people, get twice the output. It’s tidy, intuitive, and almost always wrong.

In real systems, the relationship between cause and effect is rarely proportional. A small tweak to a recipe can ruin the dish. A single comment in a meeting can shift the direction of a whole project. An extra degree of warming can trigger the collapse of an ice sheet that was stable for centuries. The input is small. The output is enormous. That’s nonlinearity.

It works the other way too. You can pour enormous effort into something and see almost no result - because the system absorbs the input without changing. A struggling relationship doesn’t improve just because you try harder. A stalled project doesn’t accelerate just because you add more people. The system has thresholds, saturation points, and tipping dynamics that don’t respond to brute force. Nonlinearity means you can’t predict the size of the effect from the size of the cause. This is uncomfortable, because it means careful planning based on proportional thinking will routinely be wrong - not slightly wrong, but dramatically wrong.

IN PRACTICE

When more isn’t more (and less isn’t less)

Adding a ninth person to an eight-person team doesn’t increase output by 12.5%. It might increase it by 2% - because the communication overhead grows faster than the capacity. Or it might decrease output, because now there are coordination problems that didn’t exist before. The relationship between team size and productivity is nonlinear, and most of the time it curves in the wrong direction.

A city adds a single new road to reduce congestion. Traffic gets worse. More road capacity made driving more attractive, which drew more drivers, which overwhelmed the new capacity. This is Braess’s paradox - a well-documented nonlinear effect where adding capacity to a network can reduce its performance. The road planners were thinking linearly: more road, less congestion. The system was thinking nonlinearly: more road, different behaviour, more congestion.

A restaurant owner drops prices by 10% expecting a modest bump in customers. Instead, business doubles - because the price crossed a psychological threshold that made it the obvious choice for a whole new group of people. The 10% change didn’t produce a 10% effect. It produced a 100% effect, because it happened to hit a tipping point. Next month, they drop prices another 10%. Almost nothing changes. The threshold has already been crossed. The same-sized input, applied twice, produced wildly different results.

WORKING WITH THIS

Stop expecting proportional

The first step is letting go of the assumption that bigger inputs produce bigger outputs. They sometimes do, but in complex systems, you can’t count on it. Before investing heavily in something, ask: is this a system that responds proportionally, or one with thresholds and tipping points?

Look for the points where small changes might matter disproportionately. These are often at the edges - where a system is already close to a threshold, where a relationship is already strained, where demand is just below a tipping point. A small intervention at the right moment, in the right place, can do more than a massive effort at the wrong time.

And when a big effort produces no visible result, resist the urge to just push harder. The system might be absorbing the input, or the effect might be delayed, or you might be pushing in a direction the system is structured to resist. Stepping back and looking at the shape of the system - where are the thresholds, where are the feedback loops, where are the leverage points - is usually more productive than doubling down.

THE INSIGHT

The size of the push tells you nothing

In a nonlinear system, a whisper can cause an avalanche and a shout can change nothing. The size of the input doesn’t predict the size of the output. What matters is where you push, when you push, and what the system is ready to do.

RECOGNITION

Knowing it when you see it

You’re in nonlinear territory when a small change produces a surprisingly large reaction - or when a huge effort produces almost nothing. When the same action works brilliantly in one context and fails completely in another. When someone says “we just need to do more of what’s working” and it doesn’t scale. When adding resources makes things slower, when cutting costs increases spending, when trying harder makes things worse. The system is telling you that the straight-line assumption doesn’t hold here.

prediction cause-and-effect planning surprise