Cut the Target. Cut the Resources. Wonder Why It Happens Again.

Nobody discusses this part.

When a mine regularly misses its production target, the target is reduced and resourcing follows. That's obvious. What's less obvious is how this affects the people who keep the operation running.

They've been working flat out, coming in early, covering gaps, solving problems that never should have reached them. Then the message arrives: the target they couldn't hit has been lowered, and so has the resourcing.

Think about what that conveys. Not "we're going to fix the system." But "now that the production target is lower, you need less to meet it."

Here's what happens next.

The seasoned people, those with institutional knowledge and the ability to recover when things go wrong, update their CVs. Not because they can't handle pressure, but because they recognise the pattern. They've seen targets missed, resources cut, and the remaining team asked to carry the extra load. They know how this ends.

Those who stay get pulled into longer meetings, more reporting, more KPI reviews. Not because anyone thinks that's productive, but because leadership needs to show rigour. The supervisor who used to spend the shift on the floor now spends half of it explaining yesterday's variance.

Meanwhile, the real issue, the physics of the production chain, stays unaddressed.

A mine is a series of dependent, variable processes. When each step is only resourced to meet average demand, there's no buffer/sprint capacity for normal shift-to-shift variability. If one unit falls over, the whole chain stops. Goldratt explained this forty years ago: when you balance capacity across dependent processes, output doesn't average out. It drops well below it.

So the budget drops, resources get trimmed "to maintain efficiency," and output settles 20-25% below the reduced target. Again.

This is not a people problem. It's a design problem that becomes a people problem.

But it can be turned around. When an operation identifies its constraint and subordinates everything to protecting it, the first thing people notice isn't the production uplift. It's the quiet. Experienced staff stop leaving. Not because of a motivational speech, but because the system made sense again.

If your operation is caught in this cycle, ask yourself: are you solving a production problem or a systems design problem?

Your best operators already know the answer.