Mindset & Motivation

Setting running goals that survive February

Most running goals are set in January and abandoned by February — not from weak will, but because they were the wrong shape. Here is how to set ones that hold.

Aug 25, 2026
Setting running goals that survive February
Illustration generated by AI
Table of contents
  1. Outcome goals versus process goals
  2. Make it specific enough to fail
  3. The minimum version matters more than the target
  4. Timeframes that work
  5. Distance goals for a first year
  6. When to change a goal
  7. The one worth writing down

Most running goals fail in the same way. They are set in a burst of enthusiasm, they depend on things you do not control, and there is no plan for the week everything goes wrong.

Outcome goals versus process goals

An outcome goal is a result: run a sub-25 5K, finish a half marathon, lose weight.

A process goal is a behaviour: run three times a week, do the strength session on Tuesdays, keep easy runs easy.

Outcome goals are motivating and mostly outside your control. Weather, illness, work and simple biology all get a say. Process goals are entirely inside your control and, awkwardly, are the only things that actually produce the outcomes.

Keep one outcome goal if you like the direction it gives you. Then translate it into two or three process goals and pay attention only to those.

Make it specific enough to fail

"Run more" cannot be failed, which sounds pleasant and is the problem — you cannot succeed at it either. There is no moment where you know you did the thing.

"Three runs a week, Tuesday, Thursday, Sunday" can be checked. That is what makes it useful.

The minimum version matters more than the target

For every goal, define the smallest version you would still count on the worst possible week. Ten minutes instead of forty. One run instead of three.

This is the part people leave out, and it is the part that decides whether the goal survives. A goal with no floor gets abandoned entirely the first time it cannot be met in full — and the abandonment, not the missed week, is what ends it.

Timeframes that work

  • Twelve weeks is about right for a training goal. Long enough for real adaptation, short enough to stay in view.
  • A week is about right for a process goal. Reviewed on Sunday, adjusted for the week ahead.
  • A year is too long for anything except direction. You will not be the same person, and neither will your circumstances.

Distance goals for a first year

If you are starting out, a sensible sequence looks like: run 5K continuously, then run it comfortably, then build to 10K, then decide whether you want to go further. The eight-week beginner plan covers the first step and has a section on what to do when you miss sessions.

Resist stacking a time target on top of a distance target in the same block. Do one at a time.

When to change a goal

Changing a goal is not the same as failing at it, though it feels similar. Change it when:

  • Your circumstances genuinely changed — new job, injury, a different life
  • The goal is producing dread rather than direction
  • You picked it because it sounded impressive rather than because you wanted it

Abandon it entirely if it is making running worse. The running is the point. The goal was only ever a device for getting you out of the door.

The one worth writing down

Whatever else you set, write this one somewhere visible: never miss twice in a row. Missing one session is life. Missing two is where habits actually die — more on building one that lasts.