Where to Push a System

Why does so much effort change so little?

The idea

Some interventions barely move a system while others reshape it, and the powerful ones are rarely the obvious ones.

In the real world

Changing what a team is rewarded for outperforms adding staff to the same process.

Going deeper

Effort applied inside a structure rarely changes what the structure produces. Adding staff, hours and tooling to a slow process leaves the rules, priorities and incentives that create the slowness untouched.

The interventions that reshape a system operate at a different level: what gets prioritised, who has authority to decide, what is rewarded, what information reaches whom. These are usually harder to change politically and cheaper to change materially, which is the opposite of resource-based interventions — and it is why the obvious lever is so often the weak one.

Where it stops applying

Structural change is disruptive and its effects are hard to predict or reverse. Adding resource is sometimes genuinely the right answer, particularly where the constraint is simply capacity.

Why it matters

It stops effort being spent where it is easiest to apply rather than where it does most.

Try this today

For one stubborn problem, list an intervention at the level of rules rather than effort.

Test yourself

A company has tried more staff, longer hours and new tooling on a slow process, with no change. What kind of intervention has not been tried?

Show the answer

One that changes the rules or the goals rather than the effort inside them — what gets prioritised, who decides, what is rewarded. Adding resource to a process leaves its structure intact, and the structure is what is producing the result.

Learn this in the feed Answering from memory, then again days later, is what makes it stick.

More in Product & Systems Thinking

Local Optimisation Hurts Solve a Real Job Scope Grows Unless Bounded Bottlenecks Govern Flow Feedback Loops Design for Failure

All Product & Systems Thinking lessons