Process Goals vs Outcome Goals and Which One to Set
You set a clear target, such as losing 6 kg or finishing a novel by summer, and three weeks later you feel further from it than when you started. Most of the time the target was fine.

You set a clear target, such as losing 6 kg or finishing a novel by summer, and three weeks later you feel further from it than when you started. Most of the time the target was fine. The trouble is that you only had an outcome to stare at, and nothing that told you what to do on a wet Tuesday evening.
Understanding process goals vs outcome goals fixes that gap. This article explains the difference with real examples, shows how to turn one into the other in about ten minutes, and covers the cases where the popular "just focus on the process" advice falls short.
Process goals vs outcome goals in plain terms
An outcome goal describes a result: run a half marathon in under two hours, save £3,000, get promoted to team lead. You do not fully control it. Injury, a market downturn or a manager leaving can all change the result even if you did everything right.
A process goal describes a behaviour you repeat: run four times a week, transfer £250 on payday, ship one visible piece of work every Friday. You control it almost completely. Either you did it this week or you did not.
Sports psychologists also talk about performance goals, which sit in the middle. They measure your own result against your own past, such as cutting your 5 km time from 29 minutes to 27. They are less exposed to outside factors than outcome goals but still not fully in your hands.
| Type | Example | How much you control it |
|---|---|---|
| Outcome | Pass the accounting exam with 70 percent | Partly |
| Performance | Score 75 percent on two full practice papers | Mostly |
| Process | Study 45 minutes, five days a week, for 12 weeks | Almost entirely |
Why process goals keep you moving
Outcome goals are good at giving direction and terrible at giving feedback. If your target is six months away, every day before then is technically a "not yet". That feeling wears people down long before the deadline arrives.
Process goals give you a win you can count the same day. Research on athletes going back to the 1990s found that people who set a mix of goal types, with process goals doing the daily work, performed better and reported less anxiety than people who set outcome goals alone. The same pattern shows up in office work. A writer who aims for 500 words a day knows by 10 pm whether the day counted. A writer who aims for "finish the book" only finds out months later.
Process goals also make problems visible early. If you planned four runs and managed one, you know by Sunday that something in your week needs to change. With only an outcome goal, you might not notice the drift for two months.
How to turn an outcome into a process goal
Keep the outcome. It tells you where you are heading. Then work backwards with these four steps.
- Write the outcome with a number and a date. "Save £3,000 by 30 June" is workable. "Be better with money" is not. If you struggle here, our guide to setting a goal you can actually measure walks through it.
- List the two or three behaviours that drive it. For saving, that might be an automatic transfer, a weekly spending check and cooking at home on weekdays.
- Give each behaviour a frequency and a minimum. "Transfer £250 on the 1st and 15th" and "cook at home at least four weeknights" are clear enough that you cannot argue with yourself about whether they happened.
- Pick one weekly check. Ten minutes on Sunday to tick off what you did and adjust next week. That is your performance layer.
If the outcome feels too big to even start, split it into stages first using the method in how to break down a big goal into steps you can start, then attach process goals to the first stage only.
Where "trust the process" goes wrong
A lot of advice now says to ignore outcomes entirely and fall in love with the process. It sounds wise, and for habits like reading or stretching it works. For anything with a real deadline or a real standard to meet, it can quietly fail you.
The reason is that a process can be faithfully followed and still be the wrong process. Someone can study 45 minutes a day for 12 weeks and still fail an exam if they spent that time rereading notes instead of doing practice questions. Someone can send ten job applications a week for months and get nowhere because the CV has a problem nobody pointed out.
So keep the outcome in view, and check it on a schedule. A useful rhythm is:
- Daily: did I do the process? Yes or no.
- Weekly: did I hit my process targets most days?
- Every four weeks: is the outcome actually getting closer? If not, change the process, not your effort level.
That four week review is what separates a process goal from a ritual you keep doing out of habit. If the numbers are not moving, the honest move is to swap the behaviour for one that works.
Examples you can copy this week
Here are a few common outcomes rewritten with process goals attached. Adjust the numbers to your situation.
- Outcome: run a 10 km race in March. Process: three runs a week, one of them at least 40 minutes, plus one rest day after every long run.
- Outcome: read 20 books this year. Process: 20 pages before bed, six nights a week. At around 300 pages per book, that comes to roughly 20 books.
- Outcome: get a new job by spring. Process: five tailored applications and two networking messages each week, every week.
- Outcome: learn conversational Spanish for a summer trip. Process: 20 minutes of practice daily and one 30 minute conversation session each weekend.
Notice that every process goal has a number small enough to hit on a bad day. If your minimum only works on a perfect day, it is too big. Cut it in half and build up once the streak is steady.
Tracking without turning it into a chore
A process goal is only useful if you can see that you did it. Keep tracking dead simple: a tick on a paper calendar, a single row in a spreadsheet, or a basic app. Two or three process goals is the realistic limit most people can track for long. Any more and the tracking itself becomes the project.
If you have tried trackers before and abandoned them by the second week, the setup tips in our piece on a habit tracker that lasts past week two will help. The short version is to track only what you will review, and to review it at the same time every week.
Frequently asked questions
What is an example of a process goal?
"Practise guitar for 20 minutes, five days a week" is a process goal because it describes a behaviour you control and can tick off. The matching outcome goal might be "play three full songs at a family gathering in December". The process goal is what you actually do each day to get there.
Are outcome goals bad?
No. Outcome goals give you direction and a reason to care. They become a problem only when they are the only goal you have, because they offer little daily feedback and depend on things outside your control. Pair each outcome with one to three process goals.
How many process goals should I have at once?
Most people do best with two or three in total across their life, not per outcome. Each one takes attention to track and protect. Start with fewer, keep them for at least four weeks, and only add another when the first ones feel automatic.
More in Goals
Goals
How to Pick the Right Difficulty for a Personal Goal
Two people I know set a reading goal last January. One picked 52 books, one picked 12.
Goals
The Planning Fallacy and How to Estimate Your Goals
I told myself a side project would take six weeks. It took eight months.
Goals
How to Set Goals With a Partner Without Arguing
You sat down to plan next year together and ended up arguing about whether a holiday counts as a goal.