Process goals versus outcome goals: what to focus on

Focus mainly on process goals, which describe actions you control, and use outcome goals to show the direction you are heading. An outcome goal names a result, such as having a short story accepted for publication or passing a certification exam on a set date. A process goal names the repeatable action that makes that result more likely, such as writing for 45 minutes on four mornings a week. Most useful plans include both, but they do different jobs, and confusing the two is a common source of frustration.

What each type of goal actually measures

An outcome goal depends on many factors, and only some of them are in your hands. A process goal depends mostly on your own choices. Consider two goals for the same skill: passing a certification exam on a set date, and studying for 30 minutes on five weekdays. You can complete the study schedule every week, but the exam result also depends on the difficulty of the questions, the day you sit the test and how much you remember that morning.

This difference shapes how the feedback arrives. Process goals give you a signal every day or every week, because the action either happened or did not. Outcome goals give you a signal only at the end, which can be too late to change course. A plan built only on outcome goals can feel silent for weeks and then suddenly succeed or fail, which makes it hard to learn from.

When outcome goals help most

Outcome goals work well when a result is fixed and visible. An exam date, a submission deadline or the date of a scheduled event creates a clear finish line that anyone can recognize. They are also useful when you need a reason to start, because a concrete result is easy to picture and easy to care about.

Outcome goals can cause trouble when the result is strongly affected by things you cannot control. If you aim only for an outcome and it does not arrive on schedule, the usual response is to work harder in the same way, which may not help at all. Use outcome goals as the destination, and check them at a planned point, such as once a month, rather than every day. Checking them too often mostly produces anxiety about a result that has not had time to show. Writing the date next to the outcome gives the monthly check a clear question to answer: has enough time passed for the result to appear, and if not, what does the process record say?

When process goals do the most work

Process goals are most useful when results take months to appear or when the main task is to build a habit. Writing a draft is easier to control than getting a story accepted. Attending three practice sessions a week is easier to check than the skill level you hope to reach. Process goals also make it easier to tell whether the method is working. If you complete every planned session for four weeks and the skill has not moved, you have learned something specific about the method, and you can change it.

Write process goals as counts that fit into a week. "Practice more" is vague. "Three practice sessions of at least 20 minutes, Monday to Friday" can be checked in under a minute at the end of the week. Keep the number small enough that you can meet it on an ordinary week, not only on a good one, because a target that works only in ideal weeks will break the first time a normal week arrives.

Using both without mixing them up

A workable setup pairs one outcome goal with two or three process goals. For example, the outcome goal might be having one short story accepted for publication by the end of the year, and its process goals might be writing for 45 minutes on four weekday mornings, sending one finished story to a suitable publication each month and revising one story each week using notes from a reader. Review the process goals weekly, because that is where the daily action happens. Review the outcome goal monthly, because that is when a result has had enough time to show. This keeps the daily work tied to a clear destination without making every day feel like a test. To find process goals in the first place, ask what the most consistent version of the work would involve each week. Those actions usually look plain on paper, which is exactly why they are easy to count and to repeat.

Pay attention to two patterns. If the process goals are met but the outcome lags for several weeks, the method may be the problem, so review what you are doing rather than adding more hours. If the outcome arrives but the process goals were often skipped, the result may have come from luck or from a short burst of effort, which will be hard to repeat. In both cases the two types of goal give you a way to see what is actually happening, and that is the reason to keep both.