The First Milestone Should Measure What You Can Do

A long project often begins with a number written in a margin: a completion date, a funding target, a promised result. In a public works office, that number sits beside work no single clerk can command, from permits and weather to contractor schedules. A first milestone has a narrower job. It should give the people doing the work something they can complete, check, and adjust before the distant result arrives.

That distinction is the difference between a process goal and an outcome goal. One describes an action under your control. The other describes a result influenced by other people and conditions. For a long-range goal, the process is usually the better first milestone, provided it has a clear volume or frequency.

The result still matters. The point is to make the path toward it visible early enough to learn from the work, rather than waiting for a final figure to reveal that the plan needs revision.

What the two kinds of goals measure

A process goal names a behavior you can perform on demand. Sending ten cold emails every weekday is one example. An outcome goal names a result you want but cannot execute directly, such as closing $200,000 in revenue this year. You can send the emails and record whether you sent them. You cannot make a customer buy simply by writing the revenue target down.

Sport psychology also distinguishes a third category, the performance goal. It measures your own result against a standard, such as running a 10K in 40 minutes. That benchmark is more directly tied to your performance than winning a race, but it still differs from a process goal: the time is an achieved result, while training sessions are actions.

The useful question is not which kind of goal sounds more ambitious. It is how much of the result you can produce yourself. A market can shift, a competitor can make a different offer, or an approval can take longer than expected. Those conditions can frustrate an outcome target even when the underlying work is sound. A process target gives the team a daily unit of progress that does not depend on those conditions.

What the evidence can, and cannot, say

A Griply guide summarizing a systematic review of goal setting in sport reports that process goals produced large performance gains, while an outcome goal on its own had little effect. The review also found that following through on a process goal can build self-efficacy day by day. An outcome goal offers that evidence only when the result is reached.

That difference matters at the beginning of a long effort. A distant result may take months to show movement. A behavior can be checked after the first working day. The same guide reports that precise wording mattered less than setting the goal on a behavior a person could control. That is a useful correction to the habit of polishing a target until it sounds exact while leaving the daily work unspecified.

The evidence should be kept in scope. The review concerns sport, and the cited guide does not establish a universal timeline for long-range goals in business, public administration, or personal projects. It describes high school girls moving from process goals toward outcome goals as they improved at a complex motor skill. That is an example of a phase change, not a calendar rule for every kind of work.

Make the first milestone observable

Start with the process when the desired outcome depends on factors outside your control. Then give the action a count, frequency, or other visible measure. Ten emails each weekday is more informative than a vague promise to do outreach regularly. A process goal with no target can turn into activity for its own sake, and it will be hard to tell whether the effort is substantial enough to test the plan.

Keep the outcome beside the process goal. If the revenue target is $200,000, record the outreach behavior and the revenue in a connected view, rather than in separate places that hide the relationship. If the outcome stays flat, the record can prompt a more useful question: is this the wrong action, or is the action happening too rarely? The tracking does not answer that question by itself, but it makes the gap easier to see.

This is especially useful when the first milestone is meant to establish a working rhythm. The process measure tells you whether the planned behavior is happening. The outcome measure tells you whether the broader aim is responding. Neither substitutes for the other. A full count of actions is not proof that the strategy is effective, and a slow outcome does not automatically mean the work was not done.

Shift phases without dropping the behavior

The recommended sequence is to lead with the process goal, then shift emphasis toward the outcome once the behavior is reliable. The source does not define a numerical threshold for reliable, or say how many weeks or months that phase should last. That uncertainty is worth stating plainly. A long-range plan should not pretend there is a tested universal number where process tracking becomes unnecessary.

In practice, the shift means the outcome gets more attention as the behavior becomes repeatable. It does not mean deleting the behavior from the record. The guide warns that performance can fall back when the behavior stops. Keeping the process measure visible helps distinguish a change in results from a change in the work that produces them.

The first milestone, then, is best treated as a stage rather than a permanent setting. Build a measurable action, observe whether it can be repeated, and keep the desired result in view. Move toward outcome-focused tracking when the behavior is dependable enough to assess, while retaining the action as a check on the system. The evidence does not supply a fixed review schedule for goals spanning years, so the milestone’s duration remains a decision to make in context, not a number to borrow from a study.

Common misreadings

One mistake is to treat an outcome goal as useless because it cannot be completed directly. It still gives the work direction and a way to judge whether the effort is serving its purpose. Another is to mistake activity for progress when the activity has no defined target. A count makes the commitment testable; the outcome keeps the count accountable to a larger aim.

A final mistake is to split the two measures so far apart that they cannot inform each other. If the action is tracked in one place and the result in another, a flat outcome may be harder to diagnose. Keep both visible, and resist inventing a certainty the evidence does not offer. For a long-range goal, the first milestone should track a repeatable action. The result belongs beside it, ready to be examined as the work accumulates.