Process goals: setting targets that depend on you

Productivity

Process goals: setting targets that depend on you

Process goals: setting targets that depend on you

Introduction

"I want to lose ten kilos." "I want to run the marathon under four hours." "I want a promotion this year." They're legitimate goals, and they share a problem: none of the three is entirely within your control.

You can do everything right and have your weight stall for weeks through water retention. You can prepare impeccably for a marathon and have race day hit thirty degrees. You can perform excellently and see the promotion go elsewhere for reasons you'll never know.

Sport psychology has worked for decades with a goal hierarchy that solves this, and its usefulness reaches far beyond sport.

A goal that can fail without you doing anything wrong is badly formulated.

The three levels

Outcome goals. Winning, qualifying, finishing top ten. They depend on others and on chance. Highly motivating at the start and highly anxiety-producing at the end.

Performance goals. Your own marks, independent of rivals: running under 45 minutes, lifting 100 kilos, improving your success rate. More within your control, though not entirely.

Process goals. The concrete actions you execute: holding cadence in the final kilometers, running your routine before every serve, training three times a week. They're one hundred percent within your control.

The usual recommendation isn't to pick one but to combine them: the outcome goal provides direction, the performance goal serves as an intermediate reference, and the process goal governs day-to-day work and is the only one you evaluate after each session.

Why the difference matters

It reduces anxiety. Much competitive anxiety comes from focusing on the uncontrollable. Shifting the focus to process reduces that load.

It defuses self-focus. Thinking about the outcome during execution is exactly what produces choking. A process routine occupies attention with something executable.

It gives useful information. If you miss an outcome goal, you don't know what to correct. If you miss a process goal, you know exactly what failed.

It sustains motivation through bad patches. An athlete measured only by results goes through bad runs with nothing to hold on to. One measured by process still has daily wins.

How to formulate them

The SMART framework — specific, measurable, achievable, relevant, time-bound — remains a useful guide, with an honest caveat: it's a management mnemonic, not a validated theory, and its empirical evidence as a specific formula is limited. What does have solid backing is the core of Locke and Latham's goal-setting theory: specific, challenging goals produce better performance than vague ones or "do your best", provided there's commitment and feedback.

A well-formulated process goal answers four questions: what, how much, when and where.

  • Bad: "train more".
  • Better: "train three times a week".
  • Good: "Monday, Wednesday and Friday at 7 p.m., 40 minutes of strength work at the neighborhood gym".

And it's worth adding a plan for the predictable obstacle: "if X happens, then I'll do Y". Implementation plans with that structure have reasonable empirical support for closing the gap between intention and action. For example: "if I leave work late, I do the short 20-minute session at home".

A complete example

Outcome (12 months): run a half marathon.

Performance (3 months): complete 15 km continuously at a comfortable pace.

Process (this week):

  • Three runs: Tuesday and Thursday 30 easy minutes, Sunday the long run.
  • The long run increases by 1 km per week at most.
  • Two 25-minute strength sessions.
  • If it rains on Sunday, run anyway; if there's a storm, treadmill or move it to Monday.

How it's evaluated on Sunday night: did I do the three runs and the two sessions? That's what gets scored. The marathon time will be settled in a year.

Common mistakes

Setting only outcome goals. It's the default pattern and the one that generates the most frustration.

Too many goals at once. Two or three process goals, not ten.

Vague process goals. "Eat better" isn't a goal; "bring fruit to work five days a week" is.

Never reviewing them. A goal that isn't reviewed every few weeks stops operating.

Setting them too high "for motivation". An unreachable goal demotivates as soon as the first failures pile up. Better one that's demanding and achievable, then raise it.

Confusing process with outcome when evaluating. If you met the process and the result didn't come, the process wasn't a failure: it may need adjusting, or it may need more time.

When a goal stops serving you

A goal is a tool, not a contract. It deserves review if circumstances change — injury, a new job, illness — if it creates pressure that makes your life worse, or if it stopped mattering to you. Abandoning a goal that no longer fits isn't a lack of discipline: it's information that arrived after you set it.

Final thought

The difference between a goal that sustains you and one that wears you down usually comes down to whether it depends on you. Translate your most important goal right now into the concrete actions that produce it — what, how much, when and where — and add a plan for the obstacle you already know is coming. From there, evaluate only that. The outcome will come or it won't, but it will stop being the only thing deciding whether the year was worth it.

Oops, something didn't go as expected. Your data is safe. Reload the page to keep building your habits.
Reload ×

Reconnecting…

The connection to the server was lost and is being restored automatically.

Could not reconnect

Check your internet connection and try again.