The art of the operating intervention

An operating intervention is the smallest change that produces the largest second-order effect, and most leaders get it exactly backwards. They reach for scale because scale feels like seriousness: a big rollout, a new framework, a steering committee that now exists and needs something to steer. Size and impact are not the same thing, and confusing them is the most expensive mistake I see in operating design. The best operating intervention looks small from the outside and feels enormous from the inside, because it removes the one constraint the whole system was quietly bending around. If your fix needs a launch deck, the diagnosis was probably wrong.

Scale feels like seriousness. It is not the same as impact.

Most operating problems get solved twice. Once badly, with a big programme that treats the symptom. Once properly, months later, with a change so small the organisation barely notices it happening.

I watched a scale-up spend four months building a performance enablement framework. New competency matrix, new review cycle, calibration workshops for every manager, a rating scale redesigned from five points to four. The underlying problem was that one VP was rubber-stamping every review his direct reports submitted without reading them. Fix the VP's habit, not the framework. Instead they rebuilt the framework, and the VP kept rubber-stamping, just against new paperwork.

That is the pattern. A big rollout signals that the problem was taken seriously, so leaders reach for scale to prove they care. But the size of the response is not evidence about the size of the fix. It is evidence about how anxious the room was. This is the same instinct that turns a stalled behaviour into a training programme and a missing document into a company-wide tool migration. If you want to understand the machinery behind it, most change programmes fail for reasons that trace straight back to this reflex: a heavy response chosen before anyone named the specific thing that broke.

The four-month framework cost roughly £180k in facilitator time and lost manager hours. The actual fix, a fortnightly fifteen-minute review between the VP and his own manager, would have cost nothing and worked in three weeks. Nobody chose the expensive path on purpose. They chose it because the small path did not feel like enough.

The diagnosis is the operating intervention

Diagnosis has to come before intervention, not alongside it. If you cannot name the specific behaviour, the specific person, and the specific moment where the system breaks, you are not ready to intervene. You are ready to redecorate.

Here is what a real diagnosis does that a programme skips. It triangulates. It asks what the data shows, what the quiet and competent people say when you ask them directly, and where the actual work visibly stalls on a normal Tuesday. Those three rarely agree at first, and the gap between them is the whole job. The loudest complaint in an org design review is almost never the real bottleneck. It is the thing that annoyed someone most recently. Loud and true are different axes, and a diagnosis that cannot tell them apart will aim the intervention at the wrong target with total confidence.

The reason this matters is that the intervention itself is usually small and obvious once the diagnosis is right. The work is not inventing a clever fix. The work is being sure enough about what actually broke that you can afford to make the fix tiny. When I audit one process end to end, the ranked plan that comes out of it is valuable because of the diagnosis attached to each item, not because the fixes are surprising. Reading the signals of operating health tells you where to point before you spend a penny changing anything.

Why small beats big

Small interventions are cheap to test and cheap to reverse. That is the entire argument. A big intervention, once launched, has its own momentum: sunk cost, internal comms already sent, a steering committee that now needs to justify itself. You cannot quietly retire a company-wide OKR rollout after six weeks even when it is obviously not working. You can absolutely retire a two-line change to a channel's notification settings.

Small interventions also get taken more seriously by the people living inside the system, which is the opposite of what most leaders expect. A manager told to stop scheduling 1:1s back to back with no gap will actually do it, because it is a concrete instruction they can start tomorrow. A manager handed a forty-page manager excellence framework will nod, file it, and change nothing. Specificity is what makes a change executable. Scope is what makes it ignorable.

There is a sizing test I run with clients before anything gets a green light. Can you describe the change in one sentence, with no noun like framework, programme or initiative in it? "We are removing the requirement for VP sign-off on offers under £5k." Yes. "We are launching a hiring excellence initiative." No. If the sentence needs a capitalised noun to hold it together, the intervention is bigger than the diagnosis warrants, and the extra size is doing emotional work, not operating work.

Interventions that fit the grain compound

Every organisation has a grain: the way work actually flows when nobody is watching, the tools people genuinely open, the rituals they genuinely run. A carpenter does not argue with wood. They read it first. The grain metaphor for reading your organisation is the whole reason smallness works: an intervention that fits the grain repoints a mechanism the organisation already trusts, so adoption is automatic. You are redirecting an existing muscle, not building a new one.

A sales team that already runs a rigorous weekly pipeline review does not need a new ritual to fix a forecasting problem. It needs one extra column in the review they already run, and one extra question the sales lead already knows how to ask. The muscle exists. An intervention that fights the grain does the opposite: it invents a new ritual, a new owner and a new cadence, on top of a culture that has no attention left for any of them.

Where interventions go wrong

Big interventions usually fail for one of three reasons, and all three trace back to a weak diagnosis. The pattern is always the same: leaders build a visible response to a visible symptom, while the real constraint sits one layer down, untouched.

The third row is the one worth sitting with. Most organisational dysfunction is not a missing process. It is an existing process that nobody has permission to skip when it clearly does not apply. The fix is very often subtraction: remove the sign-off, remove the meeting, remove the form. Subtraction is unglamorous, which is exactly why it gets skipped in favour of a new framework that looks like effort. Adding a layer photographs well in a board update. Removing one does not, even when removing one is the entire answer.

The first row hides the same mistake in a different coat. The visible problem is that managers are not giving feedback. The structural problem is that the manager's own manager never asks about it, so there is no accountability loop above the behaviour you want to change. Training the managers harder does not fix a missing loop. It just makes the people inside a broken system feel personally blamed for the shape of the system.

Test in one place before you touch the whole organisation

Run the intervention in one team, one function, or one week before it touches everyone. Not a pilot programme with a launch deck and a steering group. Just do it, quietly, somewhere reversible, and watch what actually happens against what you predicted would happen. A pilot proves a change can work in one place. It does not prove the organisation can absorb it, and that second question is the one that kills rollouts.

The three things to watch are precise. Does the behaviour change without anyone having to be reminded twice. Does a second-order effect show up that you did not predict, good or bad. And does the team ask for more of it unprompted, which is the closest thing to proof that it fits the grain rather than fighting it. If all three come back clean, scale it exactly as it ran in the test.

That last instruction is where most good small interventions die. The temptation to add scope during scaling is enormous. Someone in a steering meeting asks "should we also," and the smallness that made the thing work gets diluted by the third addition, and now you are back to a programme. Protect the smallness on the way out the door as hard as you protected it going in.

Document the diagnosis, not just the fix

An intervention without its diagnosis attached is a trick, not a method. If you cannot explain why the fifteen-minute VP check-in worked, you cannot tell whether it will work in the next organisation, with a different VP, in a different market. Write the diagnosis down next to the intervention: what was actually broken, what evidence proved it, what constraint the intervention removed or rerouted. That pairing is what makes the intervention repeatable rather than a one-off story you tell in a proposal deck.

This is the actual deliverable in most of my engagements. Not the intervention itself, which is often embarrassingly small once you see it written down, but the diagnosis that got us there, because that is the thing the client's own team can reuse the next time something in the system quietly breaks. A Grain Audit is exactly this discipline run once, in public, on one process end to end: the diagnosis, the ranked plan, and the smallest change that moves each thing, handed over so your team can run it again without me.

This is what operating leadership looks like at close range. Not the size of the response, but the judgement about where to point it. The intervention is the easy half. Knowing which small thing to change, and being sure enough to keep it small, is the half worth keeping.