Somewhere in your home there is a number that has been quietly grading you for years. Maybe it lives on a bathroom scale, maybe in a bank app, a word count, a running watch, a follower tab. You step up to it hoping for approval, and when it moves the wrong way, something in your chest moves with it. Here is the uncomfortable part: that number has never once known you were trying. It cannot see the salad you chose, the run you did in the rain, the paragraph you rewrote four times. It only reports a result, and a result is the thing you control least.

The number doesn't know you're trying

Most of us set goals the only way we were ever shown: pick a finish line and point yourself at it. Lose fifteen pounds. Save ten thousand. Finish the novel. Run a sub-two-hour half. These are outcome goals, and they are not wrong. They are just not the goals that get you out of bed.

Sport psychologists noticed this decades ago, because athletes are a brutal test case. In the 1990s, Kieran Kingston and Lew Hardy ran a study with golfers, giving some of them score-based targets and others process goals focused on the components of a good swing. The process group improved more and reported less anxiety along the way. Around the same time, Barry Zimmerman and Anastasia Kitsantas taught dart throwing to students and found that those who began with process goals, focused on the mechanics of the throw, outperformed those who began by aiming at a score. Edwin Locke and Gary Latham, whose goal-setting theory is the backbone of this entire field, later found with colleagues that when a task is complex and the skill is not yet acquired, telling people to hit a performance target can actually hurt, while asking them to pursue a learning goal, to discover strategies and master the steps, helps.

The pattern across all of it is the same. The outcome is the thing you want. The process is the thing you can do.

What a process goal actually is

The distinction gets muddled, so here is the clean version. An outcome goal is a result that depends partly on factors outside you: your weight (water, hormones, sleep), your savings (the car that breaks), your finishing time (the weather, the course, the other runners). A process goal is a behavior that is fully within your control and can be judged complete today: walk twenty minutes after lunch, transfer fifty dollars every Friday, write three hundred words before opening email.

Notice what a process goal is not. It is not a vaguer goal. "Be healthier" is not a process goal; it is an outcome goal with the number sanded off. A real process goal is more specific than the outcome, not less. It names the action, the trigger, and the amount, so that at the end of the day there is a yes or a no.

Why your brain treats the two so differently

Three mechanisms explain why this works, and none of them are motivational-poster stuff.

The first is controllability. Bernard Weiner's attribution research showed that how we explain our results shapes what we feel and what we do next. When you attribute a failure to something uncontrollable, the response is helplessness, not effort. An outcome goal invites exactly this. The scale is up two pounds after a good week, and the honest explanation (water, salt, timing) is also the demoralizing one, because it tells you your effort and your result are only loosely connected. A process goal cannot do this to you. Either you walked or you didn't, and the explanation is always yours.

The second is feedback. Outcomes are noisy and slow. Weight drifts, savings jump and dip, a manuscript does not get visibly better in a day. Process goals give you a clean signal every single day, and clean daily signals are what self-efficacy, Albert Bandura's term for the belief that you can actually do the thing, is built from. Bandura identified mastery experiences, small completed actions, as the strongest source of that belief. You cannot have a mastery experience with a number that only moves once a month.

The third is the one people do not say out loud. Jennifer Crocker's work on contingencies of self-worth describes how we tie our sense of being okay to particular domains: appearance, achievement, approval. When a goal lives in one of those domains and the goal is an outcome, every measurement becomes a referendum on whether you are enough. This is why the research on achievement goals, from Carol Dweck and Andrew Elliot among others, keeps finding that performance-avoidance goals (do not look bad, do not fail) are linked to anxiety and worse persistence, while mastery goals (get better at this) are linked to the opposite. An outcome goal in a domain you care about slides toward avoidance almost on its own. You stop stepping on the scale. You stop opening the bank app. You stop looking, because looking hurts, and the habit quietly dies in the dark.

The handoff: when the number comes back

None of this means outcomes are the enemy. In the dart study, the students who did best of all were the ones who started with process goals and then, once the mechanics were automatic, shifted their attention to the score. Zimmerman and Kitsantas framed this as a developmental shift, and it maps onto what skill acquisition generally looks like: early on, attention belongs on the components; later, once the components run themselves, attention can move to the result without wrecking the form.

So the honest rule is a sequence, not a ban. Set the outcome once, write it down, and then put it away. Spend the next weeks or months living inside process goals you can complete before lunch. Check the outcome on a schedule, not on a whim, and treat it as information about the process rather than a verdict on you. If the number is not moving after a fair stretch, the answer is to adjust the process, not to feel worse about the result.

Your next moves

  • Translate one outcome into one process. Take the goal that has been grading you and write a single sentence that names an action, a trigger, and an amount: after I make coffee, I write 200 words. Keep it small enough that a bad day cannot stop it.
  • Put the number on a schedule. Decide right now how often you will check the outcome (weekly for weight, monthly for money, at the end of a draft for writing) and do not look in between. Move the app off your home screen if you must.
  • Make the yes/no visible. At the end of each day, mark whether the process goal happened. Not how well, not how much progress, just whether. A line of yeses is the feedback your outcome was never going to give you.
  • Run the attribution check. The next time you feel the sting of a disappointing result, ask one question: was today's action within my control, and did I do it? If yes, the result is noise, and you move on. If no, you have found the one thing to fix.
  • Rename the goal's domain. If the goal lives somewhere your self-worth is tangled up, describe the process in neutral terms (I'm practicing walking after lunch) instead of loaded ones (I'm fixing my body). The words you use to describe a goal shape which kind of goal it becomes.

This sequence is the whole idea behind Cadence. You hold the outcome loosely and give your attention to the small, controllable step you can mark done today, one day at a time, so the number gets to take as long as it honestly needs. Small steps, big change is not a slogan about patience; it is the research, compressed. If you want a quiet place to keep the process honest while the outcome catches up, you can start at https://cadence.lumenlabs.works.