But if you build your entire mindset around that scoreboard, you’re setting yourself up to fail more often than you succeed, and worse, you’re setting yourself up to stall out even when you’re winning. This is the core of process-over-outcome thinking, and it’s the single biggest mindset shift I bring into organizations today.
Process Goals vs Outcome Goals
The difference between process goals vs outcome goals comes down to one question: can you act on it directly, right now? An outcome goal sounds like motivation. It’s not. It’s a verdict handed to you after the work is already done. “Win gold” isn’t something I could act on in the moment. I couldn’t will myself across the finish line first through sheer desire.
What I could control was my starting gate reaction time, my line choices through each section of the track, and how I recovered from a bad jump mid-race. Those were process goals, and they were the actual levers.
Outcome goals are the scoreboard. Process goals are what you’re actually doing when the scoreboard isn’t looking. Teams that understand this distinction stop wasting energy stressing about a number they can’t directly move, and start putting that energy into the specific actions that move it.
Why Outcome Goals Create the Wrong Kind of Pressure
When athletes, or teams, fixate purely on outcome goals, they end up anxious about something they can’t directly influence in the moment it matters most. That anxiety doesn’t sharpen performance. It erodes it. I’ve watched competitors ride tense, second-guessing every line because they were thinking about the podium instead of the turn directly in front of them. The scoreboard was too loud in their head, and it drowned out the process that actually gets you to the scoreboard in the first place.
This is exactly what I’ve seen happen inside companies too. When leadership only talks about the target number, the team’s attention narrows to anxiety about hitting it, rather than execution of the steps that would actually get them there. Outcome-obsessed teams often underperform teams that stayed disciplined about process, because process discipline is what holds up when things get hard, and outcome obsession is what falls apart under pressure.
Performance Goals Examples: What This Looks Like in Practice
Talking about process over outcome in the abstract only goes so far. Here are performance goals examples that show the shift in action, both from my own training and from the teams I work with now.
Athletic examples. Instead of “win the race,” my real training goals looked like: hit a specific reaction time off the gate, hold a target line through a technical section three times in a row, or complete a strength session at a set output. None of those guarantee a win. All of them make winning more likely, and all of them were fully within my control.
Business examples. Instead of “hit the quarterly number,” a process-focused version might be: improve response time on top accounts by a set percentage, run every deal through the same qualification checklist before it advances stages, or increase the number of qualified discovery calls booked per week. These are boring compared to a big outcome target, and that’s exactly why they work. Boring is repeatable. Repeatable is what compounds into results.
Outcome Goals Fall Apart Under Pressure
Here’s the part most people don’t expect. Outcome-focused thinking tends to fall apart precisely when the stakes are highest, which is exactly when you need your mindset to hold together. Standing at the gate before a start with an Olympic medal on the line, thinking about the medal does nothing for you. It’s already too abstract, too far removed from the next two seconds of the race. What holds up under that kind of pressure is trained, specific process, built from thousands of reps where the process, not the outcome, was the focus.
How to Focus on the Process When the Outcome Still Matters
Learning to focus on the process doesn’t mean outcomes stop mattering. Obviously they do. The scoreboard is real, and eventually it has to move. But the way you move it is by getting relentlessly specific about the process that produces it, and then holding people accountable to that process rather than to a number they can’t directly control in the moment.
There’s a second benefit to this that I learned the hard way. Outcome goals only give you information after the fact, and only in binary terms. You won or you didn’t. That’s a brutal way to evaluate months or years of work. Process goals give you a way to evaluate progress even when the final result doesn’t go your way. I could have a race where I didn’t finish where I wanted, but still walk away knowing my start was faster than it had ever been. That’s real signal. It tells you the work is compounding, even when the scoreboard that day says otherwise.
Building a Process-First Culture
If you’re leading a team, ask yourself what the process equivalent of your outcome goal actually is. What’s the gate start? What’s the line through the technical section? Get specific there, build the discipline around it, and the scoreboard tends to take care of itself.
If you want to bring this conversation to your organization, learn how my experience as a corporate performance speaker can help your team build the mindset, discipline, and habits needed to perform under pressure and achieve meaningful results.
– Connor Fields
