I used to be obsessed with goals.
Annual targets, quarterly breakdowns, monthly milestones. I tracked everything and reviewed everything. When things didn't go to plan, which happened more than I'd like to admit, I adjusted the number, recommitted with fresh energy and ran the same cycle again.
It took me years to see that my commitment was never the problem. The tool was.
What are goals actually good for?
Goals are a compass. They help you decide where to point yourself. "X revenue in 18 months." "Y clients by the end of the year." That direction matters. Without it you're just busy.
But a direction is not a plan.
Knowing where you want to go tells you nothing about how to get there, what to do tomorrow morning, or what to change when things go sideways. That's where most goal-driven entrepreneurs get stuck. They set the target, feel the buzz, and then have to figure out from scratch every week how to move towards it. Exhausting, and wildly inconsistent.
Goals have side effects
Researchers have looked at this too. In a well-known Harvard Business School working paper called "Goals Gone Wild", Ordóñez, Schweitzer, Galinsky and Bazerman argue that goal setting comes with real side effects: people narrow their focus, take on more risk, and when hitting the number is all that matters, cheating goes up.
That matches what I've seen. Goals create urgency without creating capability.
The quarter ends, the number is short, and everyone reaches for the same fix: try harder next quarter. More hours, more pressure, double the outreach. That might close the gap once. But the system that produced the shortfall is still there. Next quarter, same problem.
I've been in organisations where this ran for years. Leaders set bigger targets, teams worked harder, results stayed flat, and nobody asked the one question that mattered: what does our system actually produce, and is that enough?
What engineering outcomes looks like
Every result I've produced reliably came from the same place: a repeatable process I could trust, adjust and improve.
When I ran e-commerce, I didn't "try harder to find good products". I built a sourcing system that gave me a steady pipeline of vetted opportunities every week. I didn't "try to be more responsive to clients". I built a communication rhythm with clear touchpoints, so nothing fell through the cracks.
The outcomes were simply the outputs of processes I designed. Once I saw it that way, the question changed completely: from "am I working hard enough?" to "is this process good enough to produce what I need?"
That's engineering applied to business. "Try harder" isn't solvable. "What needs to change in the process?" is.
How I work now
I still have targets. Direction matters. But I spend far more time on process design than on goal reviews.
For every outcome I want, I work backwards:
- What steps, in what order, would make this result almost inevitable?
- How consistently do they need to happen?
- Build it, write it down, test it, refine it.
The goal becomes a checkpoint to see if the system is calibrated, instead of a motivational target I chase every week. When the outcomes are off, I go back to the system, not to the goal.
This isn't about being less ambitious
The people I know who made this shift completely are actually more ambitious than the goal-setters they replaced. They don't set bigger targets. They build better machines, and a better machine, run long enough, beats almost any goal you could set for it.
The goal-setter looks at a result and wonders how to want it more. The systems thinker looks at the same result and asks which change to the process would produce it reliably. One is a motivation problem. The other is an engineering problem, and engineering problems have solutions.
I made this shift slowly, over years. The results I'm proudest of weren't the ones I wanted badly enough to grind through. They were the ones where I'd built something that produced the outcome simply by running.
Start this week
Pick one result you keep trying to reach by working harder. Then ask: what process, done consistently for 90 days, would make it almost inevitable? Design it, write it down, run it, measure it, refine it.
One model makes you the engine. The other makes the process the engine and you the designer.
The goal is a guess. The system is how you make it real.
Sources: HBS Working Knowledge, "When Goal Setting Goes Bad" (2009), https://www.library.hbs.edu/working-knowledge/when-goal-setting-goes-bad