Knowledge base › Goals

One piece of advice has travelled further than any other in recent self-improvement writing: don’t set goals, build systems. It’s good advice — and most people read it wrong. It doesn’t mean goals are useless, and it certainly doesn’t mean it’s enough to do something daily and hope it adds up. This article is about what each one is actually for, how they connect, and when letting go of the goal is a bad idea.

What the advice says, and why it spread so far

The idea is simple: a goal is a state you want to reach (“I’ll lose ten kilos”), a system is the recurring operation that gets you there (“I train three times a week”). The argument goes that a goal on its own does nothing — it only produces longing — while a system produces a small result every day.

It spread so far because part of it is true, and it brings relief. Anyone who has written the same resolution every January for years finds it freeing to hear that the problem isn’t them but the method. That part holds up: someone who only writes the goal down, and never decides when and where they’ll do it, really won’t make progress.

The trouble starts because the sentence is easy to read as though the goal were unnecessary. But a system without a goal isn’t neutral: it drifts. Train three times a week without knowing why, and in six months you’ll be exactly where you started — only more tired.

What people misread: a goal isn’t about completion, it’s about the decision

Here is the heart of this article, and it’s rarely said out loud. A goal’s primary use isn’t that one day you tick it off. It’s that today it tells you what to say no to.

In a single week a dozen good-looking opportunities come at you: a new project, a course, a request, an idea. Without a goal, the same answer suggests itself for all of them — “why not”. With a goal there’s something to measure against: does this bring me closer or not? A goal, then, isn’t a promise about the future but a filter on the present.

And the reverse: a system’s value isn’t that you’re “disciplined”. It’s that it removes the daily decision. If you’ve settled that you write on Tuesday and Thursday mornings, then Tuesday morning holds no deliberation — and deliberation is precisely what drains the energy. Our article on building habits covers this too.

The four cases where “systems, not goals” is BAD advice

This is the part almost nobody writes. The advice isn’t universal — in four situations it does real harm.

1. 1. A one-off project with a deadline. A thesis, a house move, a tax return isn’t a habit. There’s nothing to repeat: here you plan backwards from the deadline, and “I’ll work on it regularly” is precisely the recipe for slipping.
2. 2. When you don’t know where you’re going. You can only build a system if you know what it should produce. Without that, system-building becomes pleasant pseudo-progress: you have a lovely routine that leads nowhere.
3. 3. When the system is the escape. For some people daily repetition is comfortable precisely because it means not facing the fact that they’ve been in the same place for years. The system then isn’t a tool but a hiding place.
4. 4. When the work is shared. On a team or in a relationship, “this is how I do it” isn’t enough: you need a jointly stated outcome, or everyone is diligent in a different direction.

The division of labour: what the goal does, what the system does

It’s cleanest not to make them compete but to split the job. The goal does four things, the system does four, and neither can do the other’s.

The goal supplies direction, the basis for saying no, the measure (“how will I know it worked”) and the possibility of an ending — without it nothing ever finishes, it only stops. The system supplies repetition, freedom from decisions, survival on bad days, and compounding: the fact that small units add up.

When one is missing it has a characteristic symptom. With a system and no goal the sentence sounds like this: “I’m doing it, but I don’t feel I’m getting anywhere”. With a goal and no system, like this: “I know what I want, I just never get there”. Our article on why I’m not making progress covers the second case in detail.

How to connect the two — three steps

The practical part is short. You don’t have to choose: the two translate into each other, and it takes fifteen minutes.

1. Write the goal as an outcome, not an activity. Not “move more” but “in June I run ten kilometres”. That gives you the measure and the possibility of an ending.
2. Translate it into a weekly repetition. What is the smallest unit you can do three times a week? That’s the system. If it doesn’t fit into your week, motivation isn’t the problem — the goal is too big.
3. Give it a review day. Once a month, the same day: is the system producing towards the goal? This step is what links them — without it the system runs beautifully and nobody notices it’s pointed the wrong way.

What not to do

Three reflexes come by themselves, and all three lead to the same dead end.

• Don’t swap the goal for a system when it gets hard. When a goal becomes uncomfortable it’s tempting to rephrase it as a daily routine — because that gives an immediate sense of success. That isn’t a change of strategy, it’s a detour.
• Don’t build several systems at once. A system is good when you don’t have to think about it. Four new daily operations at once demand exactly as much thinking as you were trying to save.
• Don’t judge the system by daily results. Daily results are noisy: the scale, the word count, the revenue all jump around. Measure the system by whether it happened; look at the result monthly.

When building the system becomes the procrastination

This deserves saying separately, because it’s very common and from the outside it looks exactly like diligence.

It goes like this: you start a goal, then realise you first need a good system. You try three methods, pick the right app, build the template, refine the weekly rhythm — and three weeks later the system is lovely and the output is zero. It’s the same pattern our article on procrastination describes, just far better disguised: it doesn’t look like procrastination, because you really are working.

The distinction comes down to one question: has your system produced anything you could show? If there’s no output after three weeks, you aren’t building a system, you’re building scenery. The right move then isn’t further polishing but one small, finished thing — however ugly.

Four weeks that show which one is missing

You don’t have to work out in theory whether it’s the goal or the system you’re missing. Four weeks settles it, one line a week.

1. A number from zero to ten: how much you feel this week moved you closer to something.
2. Half a sentence about what. If you can’t name it — that is the answer, and the goal is missing.
3. And one word about the week: repetitive, rushed, empty or productive.

After four weeks look at the two columns. If the number is low but you can always write the same thing under “what”, the system is weak. If the number is high but the “what” changes weekly — or is blank — the goal is missing, and the diligence scatters. If both are stable, there’s nothing to do: it works.

Where a system helps

The difficulty here is that the two are measured on different clocks. The system is a daily signal, the goal a monthly one. Nobody holds both in their head: either you watch the daily ticks and lose the direction, or you watch the big goal and lose today’s step.

That’s why in Mirrify the goals, the habits and the daily entry sit in one place — not to add screens, but so that at the monthly review there is something to put side by side. That is the step that almost never happens by hand.

What it doesn’t give: it won’t tell you what your goal should be, and it won’t do the daily repetition for you. The four lines are yours to write — the system only helps you have something to look at in week four.

The one sentence worth taking away

If you take one thing from all of this, let it be: the goal exists so you know what to say no to; the system exists so you don’t have to decide every morning. Keep only one of them and you’ll call the absence of the other a lack of discipline — when it’s a structural fault.

And if you can only do one thing now: write your goal down as an outcome, in one sentence, with a date. Five minutes. After that the system is a matter of translation.

Frequently asked questions

Are systems really better than goals?

Not better — different. The goal supplies direction, the measure and the basis for saying no; the system supplies repetition, freedom from decisions and compounding. A system without a goal drifts (“I’m doing it but not progressing”), a goal without a system stays a wish (“I know what I want but never get there”).

What is a goal actually for?

Not primarily so you can tick it off one day, but so that TODAY it tells you what to say no to. In a single week a dozen good-looking opportunities come at you; without a goal the same answer suggests itself for all of them. A goal isn’t a promise about the future — it’s a filter on the present.

When is “systems, not goals” bad advice?

In four cases: a one-off project with a deadline (a thesis, a move) — there you plan backwards; when you don’t know where you’re going — then system-building is pseudo-progress; when daily repetition is an escape from facing something; and in shared work, which needs a jointly stated outcome.

How do I turn a goal into a system?

Three steps: write the goal as an outcome, not an activity (“in June I run ten kilometres”); translate it into the smallest weekly repetition you can do three times; and give it a monthly review day. If the repetition doesn’t fit into your week, motivation isn’t the problem — the goal is too big.

How do I know whether I’m missing the goal or the system?

Four weeks, one line a week: a number from zero to ten for how much the week moved you closer; half a sentence about what; and one word about the week. If the number is low but you always write the same thing under “what”, the system is weak. If the number is high but the “what” changes weekly or is blank, the goal is missing.

How many systems should I build at once?

One. A system is good when you don’t have to think about it — four new daily operations at once demand exactly as much thinking as you were trying to save. The same principle applies to habits: one at a time.

What if building the system has become the procrastination?

Ask: has your system produced anything you could show? If there’s no output after three weeks, you aren’t building a system, you’re building scenery. The right move then isn’t further polishing but one small, finished thing — however ugly.