Measure results, not activity

Track whether you achieved the result, not whether you were busy — the two are not the same.

Why it works

Activity metrics (hours worked, tasks completed) are easy to generate without moving toward any real result. Measuring results instead creates an honest feedback loop: either the result moved or it did not, regardless of how hard you worked. This prevents the motivational trap of feeling productive while making no progress on what actually matters.

How to do it

1. For each committed result, define a simple check: at the end of the day or week, is this done or not?
2. Review your results list, not your task list, to assess the day.
3. When a result did not move, ask why — which action failed or was missing — rather than just working longer.
4. Update or drop results that remain unmoved for more than two review cycles.

Evidence

The distinction between process and outcome goals is studied: outcome goals focus effort on what matters, while process goals support the how. Robbins’ emphasis on result-tracking is consistent with outcomes-oriented goal-setting, though exclusively tracking outcomes (without process) can raise anxiety when outcomes feel out of control. (mechanistic)

Pure outcome tracking without attention to the process can be demotivating when results lag despite good execution, particularly for long-horizon goals.

Common mistake

Substituting activity tracking ("I did 12 tasks today") for result tracking and calling the day successful without asking whether any of those tasks moved the committed results forward.