Systems vs goals: the operator's case

A goal is a description of a future state; a system is the set of repeated actions that produces states. Goals set direction, but only systems produce results, because a target of "£1m revenue" changes nothing about what anyone does on Monday morning. The operator's case is not that goals are useless — it is that a goal without a system is a wish with a deadline.

This argument sits inside a larger toolkit — loops, stocks, delays — that I have laid out in A Systems-Thinking Guide for Founders. Here I want to make the narrow, practical case, because "systems over goals" has become a slogan, and slogans get nobody paid.

What's actually wrong with goals?

Three things, and none of them is motivational.

First, a goal contains no instructions. "Grow 30% this year" is compatible with hiring a salesperson, cutting prices, running outbound, or hoping — the goal cannot arbitrate between them. Teams with vivid goals and no system simply do what they did last year, more anxiously.

Second, goals invite gaming the measure rather than improving the machine. When the target is "20 proposals this quarter", proposals get sent to unqualified prospects and the number is hit while nothing improves — Goodhart's law in its natural habitat.

Third, and least discussed: a goal tells you nothing when you miss it. Revenue came in 20% short — now what? The goal has no diagnostic content. A system does: you can inspect each stage, find where the numbers broke, and fix that stage.

What does a system look like instead?

A system is specified by inputs, rules, and a cadence — things you control directly — rather than by outcomes, which you influence at a distance. The contrast in outbound terms:

The right-hand column is checkable every single day. Either the sends went out or they didn't; either replies were handled or they weren't. Nobody can be vaguely "on track". The wider argument that this machinery, not channel fashion, is what decides outcomes is one I have made in The Complete UK B2B Outbound Playbook.

So do goals have any job left?

Yes — two, and they are worth keeping.

Goals choose which system to build. "Reach £1m" doesn't tell you what to do, but it does tell you that a referral-only inflow probably won't carry you there, so a new system is required. Goals are design criteria.

Goals also calibrate systems once they run. If the system executes cleanly for a quarter and the outcome still falls short, the system needs redesign — more volume, tighter targeting, a different offer. The goal is the test the system sits, not the work itself.

What goals must never be is the management method. Manage the system; let the goal audit it.

How do you convert a goal into a system?

Here is the mechanism, step by step:

1. State the outcome and work backwards through the arithmetic. When the goal is roughly four new clients a quarter, and one client typically needs a handful of proposals, and proposals come from meetings, and meetings come from conversations, then the chain tells you the weekly conversation count the system must produce.
2. Convert the top of the chain into daily and weekly actions with owners. When "conversations" becomes "n sends per day, replies triaged by 5pm", then the system exists on a calendar rather than in a slide.
3. Instrument each link. When each stage reports weekly, then a shortfall shows up at the stage that caused it, not as a mystery in the revenue line.
4. Review the system on a cadence, not the goal. When the weekly question is "did the machine run, and where did it leak?", then improvement compounds; when the question is "are we going to hit the number?", then the answer is anxiety.

Run that conversion once and you feel the difference immediately: the goal stops being a judgement hanging over the team and becomes a spec the machine is built to meet. Choosing which link in the chain to strengthen first is its own discipline — the subject of Leverage points: where small changes move revenue — and the habit of asking what each fix does downstream is covered in Second-order effects in business decisions.

One vertical illustration: recruiters live and die by exactly this conversion, because their pipeline is two-sided — candidates and clients — and a goal like "more placements" dissolves into two separate systems, as I've set out in Outbound for recruiters: the two-sided pipeline.

Set the goal once a year. Run the system every day.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.