You set the goal: lose ten kilos, hit a hundred thousand in revenue, run a half-marathon. Then it sat there. You'd look at it, feel the gap between where you are and where it says you should be, and feel slightly worse — because there was nothing in the goal you could actually do today. That's the trap of an outcome with no process behind it.
The fix that gets passed around is "set process goals, not outcome goals." It's good advice, and it's half the picture. The full picture is that process goals and outcome goals do two different jobs, and dropping either one leaves you stuck in a different way.
What's the Difference Between Process and Outcome Goals?
An outcome goal is the result you want — the number, the finish, the state you're aiming for. Lose ten kilos. Publish the book. Reach a hundred thousand in revenue.
A process goal is the repeatable action you actually control — the behaviour you'll run, regardless of the result on any given day. Strength-train three times a week. Write 500 words every morning. Make ten sales calls a day.
The difference that matters: you don't control the outcome directly, and you do control the process completely. You can't decide to lose ten kilos this week. You can decide to train three times and eat the way you planned. The outcome is downstream of the process — which is exactly why the popular advice points you at the process.
Why "Only Set Process Goals" Is Half Right
The case for process goals is real. You can't control results, only inputs, so staking your sense of progress on an outcome you don't govern is a recipe for anxiety and quitting. Worse, an outcome on its own gives you nothing to do today — it names the destination without naming a single step. Process goals fix both problems. They're inside your control, they tell you exactly what to do this morning, and they let you win the day even when the scale hasn't moved.
So far, so good. The overcorrection is throwing the outcome out entirely — tracking only the process and treating the result as none of your business.
Here's the failure that creates. A process with no outcome is just activity. You can run a disciplined daily routine for a year and end up somewhere you never meant to go, because the routine was never checked against a destination. It's the same mistake as "forget goals, just build systems": you feel productive, you're consistent, and a year later you realise the consistency wasn't pointed at anything. Process keeps you moving. Only the outcome tells you whether you're moving toward the thing you actually wanted.
Use Both: the Outcome to Aim, the Process to Move
The two aren't rivals. They're the destination and the engine, and a goal needs both to go anywhere.
The outcome is where you set the direction and the stakes. This is where you decide what "done" looks like, how hard it should be, and by when. Set it well — clear enough to aim at, ambitious enough to matter, but not so specific that you've scripted a path you can't yet see. (Setting the outcome so it actually holds is its own skill, and most people get it wrong by over-specifying.)
The process is what you run and what you measure day to day. Once the outcome is set, you reverse-engineer it into the handful of repeatable actions most likely to produce it, and those become your daily scorecard. You don't check the bathroom scale every morning and ride the mood swing. You check whether you did the three sessions — the input you control — and you let the outcome catch up.
Then you close the loop. Every so often you hold the process up against the outcome and ask the only question that matters: is the action I'm running actually moving the result? If it is, you keep going and ignore the daily noise. If weeks of honest effort aren't budging the outcome, the process is wrong and needs adjusting — not abandoning, adjusting. That feedback loop, tracking the right inputs and checking them against the result, is what separates a goal that closes from a routine that just spins.
This is the whole logic of a goal achievement system: the outcome points the direction, the process does the work, and a feedback loop keeps the two honest with each other. Motivation doesn't enter into it — you run the process on the flat days, not just the inspired ones.
If you want to put that into practice on a goal you're working on now, the free Momentum Method course walks you through it in seven short emails — no cost, and built around the small repeatable action that keeps the process moving.
Start the Momentum Method — free
Start the Free CourseThe Momentum Method walks you through turning an outcome into a process you'll actually run — one short email at a time. Free.
Frequently Asked Questions
What is the difference between process goals and outcome goals?
An outcome goal is the result you want — a number, a finish, a state, like losing ten kilos. A process goal is the repeatable action you control that produces it, like training three times a week. You don't control outcomes directly; you control the process, and the outcome follows from it.
Are process goals better than outcome goals?
Process goals are better for daily action and consistency, because they're inside your control and tell you what to do today. But they're not a replacement. A process with no outcome behind it is just activity with no direction. The outcome sets where you're going; the process gets you there. You want both.
Should I set process or outcome goals?
Set both, and use each for its job. Define the outcome first so you know what you're aiming at, then reverse-engineer it into the few repeatable actions most likely to produce it — and track the process day to day, checking it against the outcome every so often to make sure it's still working.