How to Track Progress on Goals (Without Fooling Yourself)

By Michael K., goal-achievement trainer since 2013 and creator of the Smooth Goals System

Most people track the wrong thing, feel good about it for a while, and quit anyway.

Here's the pattern. You set a goal, you start checking your progress against the result — the weight, the revenue, the word count total — and for the first stretch it's motivating. Then the result stalls, the way results always do in the middle, and the tracking that used to lift you starts doing the opposite. Every check confirms you're not there yet. So you stop looking, and not long after, you stop trying. The tracking didn't just fail to help. It helped you quit.

The problem isn't that you tracked. It's what you tracked, and what you thought tracking was for.

Why Tracking the Outcome Quietly Backfires

The outcome — the number you actually want — is the worst thing to track day to day, for two reasons.

It's laggy. The result moves slowly and unevenly, and it lags well behind the work. You can do everything right this week and see nothing on the scoreboard, because the scoreboard is reporting on decisions you made a while ago. Judge today by today's outcome and you'll punish yourself for good work that simply hasn't shown up yet.

And it's out of your direct control. You can't do the outcome. You can only do the inputs that eventually produce it. So a tracker pointed at the outcome measures the one thing you can't act on — which means when it stalls, it gives you nothing to change except your mood.

That's why outcome-tracking so reliably ends in quitting. It's built to demoralise you in exactly the stretch where you most need to keep going.

Track the Process — the Part You Actually Control

The fix is to point the tracker at the process instead: the repeatable input you control, marked simply, every day. Not "am I there yet," but "did I do the thing today." This connects directly to the difference between process goals and outcome goals — you set the outcome to aim at, but you track the process to move.

Here's the kind of shift that means in practice:

A process tracker is honest in a way an outcome tracker isn't. On a slow week it still shows you winning — because you did win the part that was yours to win — and that's the evidence that carries you through the flat middle, the same way a protected streak keeps you consistent when motivation is gone.

What a Tracker Is Actually For: Feedback, Not a Record

Even process-tracking goes wrong if you treat it as bookkeeping — a wall of checkmarks you collect and admire. A tracker isn't a record of the past. It's a feedback signal you use to steer.

The loop is simple to state:

You run the process, you track the input, and then you do the part almost everyone skips: you check that input against the outcome and ask the only question that matters — is the thing I'm doing actually moving the result? If it is, you ignore the daily noise and keep going. If weeks of honest, tracked effort aren't moving the outcome at all, the process is wrong, and the tracker just told you so. You adjust it. You don't abandon the goal — you change the input and watch the signal again.

That's the whole point of tracking: not to prove you showed up, but to catch a process that isn't working early enough to fix it, instead of grinding a dead routine for months or quitting a good one too soon.

The Hard Part — and Where the System Takes Over

Here's where it gets genuinely difficult, and where most self-built trackers fall apart.

Deciding to track the process is easy. Knowing which process to track is not. For any given goal there are a dozen things you could measure, and only a few of them actually forecast the outcome — the rest are busywork that feels like progress and predicts nothing. Pick the wrong inputs and you'll diligently track your way to a result you never wanted, checkmarks all the way. And even with the right inputs, reading the signal well — how much movement is enough, how long to hold a process before you call it dead, when a stall means adjust versus when it means wait — is a judgment most people get wrong in both directions.

Working out the handful of inputs that actually predict a specific outcome, and how to read them, is the part the goal achievement system is built to do — it's the difference between a tracker that steers you and one that just keeps score. That's the machinery behind the loop above, and it's what the system teaches rather than something you'll reverse-engineer from a checklist.

If you want to start on the right foot today, the free Momentum Method course gets you tracking the one small daily input that keeps a goal moving — the honest, in-your-control kind. Seven short emails, no cost.

Frequently Asked Questions