Goals are outcomes you want to hit. Systems are the processes you run that make outcomes more likely. The systems-vs-goals frame says: focus on the system. If you run the right system consistently, results follow. If you fixate on the goal and neglect the system, you might hit the target once but not sustain it, or you might miss and have no way to improve. The goal tells you where you're going; the system is how you get there. The leverage is in the system.
The distinction comes from Scott Adams (and others): "Goals are for losers; systems are for winners." The point is not that goals are useless — they set direction. The point is that goals alone don't change behaviour. "Lose 10 pounds" is a goal. "Eat this way and move this way every day" is a system. The person who only has the goal will yo-yo. The person who builds a system will get there and stay there (or close). In business, "hit $10M ARR" is a goal. "This is how we acquire, retain, and expand customers every week" is a system. The system is what you can control; the goal is a lagging indicator.
Systems also handle uncertainty. You can't control whether you hit a specific number by a specific date. You can control whether you run the right process every day. When you optimise the system, you improve the distribution of outcomes. When you optimise for the goal, you often distort the system — short-term moves, gaming, stress — and the long-term distribution worsens. Systems scale; single goals don't. Build the system; let the goals emerge.
Section 2
How to See It
Systems vs goals shows up wherever someone is trying to achieve an outcome and the question is whether they're investing in the process (system) or only in the target (goal).
Personal
You're seeing Systems vs Goals when someone says they want to "get fit" or "write a book" but has no daily or weekly routine. They have a goal and no system. Contrast: someone who has a system — "I run three times a week and eat by these rules" or "I write 500 words before breakfast" — and lets the outcome (fitness, finished manuscript) emerge. The second person is systems-oriented.
Business
You're seeing Systems vs Goals when a team is measured only on a quarterly number (revenue, sign-ups). When the number is at risk, they scramble — discounts, one-off campaigns, pulled-forward deals. When the number is safe, they ease off. The goal drives behaviour, but there's no stable system. Compare to a team that has a system: pipeline discipline, outreach volume, product velocity. The number is a result of the system; the system is what they manage.
Investing
You're seeing Systems vs Goals when an investor targets "20% IRR" and chases deals or takes extra risk when they're behind. The goal distorts the process. The systems-oriented investor has a process: criteria, checklists, position sizing, rebalancing. They run the process; returns are the outcome. They don't change the process to hit a number.
Scaling
You're seeing Systems vs Goals when a company sets a growth target but hasn't built repeatable acquisition, onboarding, and retention. They hit the target once with heroics, then miss the next quarter. Scaling requires systems — playbooks, metrics, feedback loops — that work without the founder in the loop. Goals without systems don't scale.
Section 3
How to Use It
Decision filter
"Before you set a goal, ask: what system would make this outcome likely? Invest in the system — the daily and weekly process — not just the target. If you can't describe the system, you don't have a path; you have a wish. Run the system; measure the goal as feedback, not as the thing you manipulate directly."
As a founder
Define the system that produces your key outcomes: how you get leads, how you close them, how you deliver and retain. Make the system explicit — playbooks, metrics, rhythms. Hire and manage for the system: do people run the process? Goals (revenue, NPS) are outputs; review them to see if the system is working, but don't optimise by moving the goal post. Optimise by improving the system. When you scale, you're scaling the system, not the goal. New people run the same system; the goal grows because the system is replicated.
As an investor
Have a system for sourcing, evaluating, and supporting companies. Don't target a number of deals or a return target and then force the process to hit it. Run the process; let the portfolio and returns be the result. When you're behind target, the wrong move is often to do more of the same or to lower the bar. The right move is to check whether the system is right — criteria, network, decision quality — and to fix that. Systems reduce the temptation to chase or to panic.
As a decision-maker
For any important outcome, write down the system: what do I do every day or every week that makes this likely? If the answer is vague, you have a goal without a system. Build the system first. Track the goal to see if the system works, but don't let the goal dictate short-term behaviour at the expense of the system. When you miss, ask what in the system failed, not how to hit the number by any means.
Common misapplication: Ditching goals entirely. Goals set direction and give you a read on whether the system is working. The mistake is only having goals and no system, or manipulating the goal (e.g. moving the deadline, changing the definition) instead of fixing the system. Keep goals; add systems.
Second misapplication: Confusing activity with system. A system is a repeatable process that plausibly leads to the outcome. Busywork or ritual that doesn't affect the result is not a system. Test: if I run this process for a year, do I have good reason to expect the outcome? If not, refine the system.
Hastings built Netflix around systems: culture as a repeatable set of behaviours (freedom and responsibility, candid feedback), not a vague goal like "be innovative." The famous culture deck describes how people are expected to operate — that's the system. Hiring and performance are run against that system. Growth and market leadership are outcomes of running the system at scale. Goals follow from the system.
Walton built Walmart around systems: distribution, store layout, inventory, and "meet the customer" culture. He had growth goals, but the emphasis was on the system — could the process run in the next store, the next region? Scaling was system replication. The goal (size, share) followed from running the system in more places. His famous store visits were system checks: is the process running as designed?
Section 6
Visual Explanation
Systems vs goals: the goal is the outcome; the system is the repeatable process that makes the outcome likely. Invest in the system; use the goal as feedback. Control the process, not the number.
Section 7
Connected Models
Systems vs goals sits with models about habits, feedback, process, and compounding. The connections below either implement the idea (habits, repeatable systems) or explain why it works (feedback loops, compounding).
Reinforces
Habits
Habits are personal systems: automatic behaviours that run without a single goal in mind. "Exercise daily" is a habit/system; "lose 10 pounds" is a goal. Habits are the building blocks of systems. Systems vs goals says to invest in the habits (and other repeatable elements) that make the goal likely.
Reinforces
Feedback Loops
Systems need feedback: did running the process move the needle? Feedback loops close the circle — you run the system, you measure the result, you adjust the system. Goals are one source of feedback (did we hit the target?). The system is what you change based on that feedback. Feedback loops make systems improvable.
Reinforces
Process Overhead
Process has a cost. Systems vs goals doesn't mean "add as much process as possible." It means "have a repeatable process that drives the outcome." Process overhead is the cost of the system; the benefit is consistency and scalability. Balance: enough system to get results, not so much that overhead kills execution.
Leads-to
Compounding
Good systems compound. You run the process today; you're slightly better tomorrow. Over time, the outcome distribution shifts. Goals don't compound; they're one-off targets. Systems compound because they're repeated. The systems-vs-goals frame points you toward building something that compounds.
Section 8
One Key Quote
"Goals are for losers. ... The system is something you do on a regular basis that increases your odds of success over time."
— Scott Adams, How to Fail at Almost Everything and Still Win Big (2013)
Adams's formulation is deliberately provocative. The point: goal-focused people often fail because they fixate on the endpoint and don't build the engine. System-focused people run the engine; the endpoint is a byproduct. "Losers" here means people who don't get the result they want, not a moral judgment. The quote captures the shift in focus: from target to process.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Define the system for every key outcome. For revenue, what's the system? (Pipeline, outreach, close process, expansion.) For product, what's the system? (Discovery, build, ship, learn.) For hiring, what's the system? (Sourcing, screening, interviewing, closing.) If you can't describe it, you don't have a system; you have a hope. Write it down. Make it runnable.
Measure the goal; manage the system. Use the goal (revenue, NPS, retention) to see if the system is working. When you miss, ask what in the system failed — not how to hit the number by any means. Don't move the goal post; fix the process. When you hit, ask what in the system worked and double down there.
Scale the system, not the goal. Adding people or locations means they run the same system. The goal grows because the system is replicated. If you don't have a system, scaling is chaos — everyone does their own thing. Build the system first; then scale it.
Avoid goal-induced distortion. When the only thing that matters is the quarterly number, people game it: pull forward deals, cut quality, burn out. The system degrades. The goal was supposed to be feedback; it became the only lever. Prevent that by making the system visible and by rewarding running the process well, not just hitting the number.
Personal outcomes need systems too. Fitness, writing, learning — have a process (workouts per week, words per day, reviews per week). Let the outcome emerge. You'll stick longer and get better results than if you only have a target and no default behaviour.
Section 10
Test Yourself
Is this mental model at work here?
Scenario 1
A sales team is told to hit $2M this quarter. With two weeks left they're at $1.2M. They offer big discounts and pull forward renewals to make the number. Next quarter they miss.
Scenario 2
A writer aims to finish a book in a year. They commit to 500 words every morning before checking email. They don't think about the total page count; they just run the daily process.
Scenario 3
A company sets a goal of 50% revenue growth. They hire more salespeople and tell them to 'sell more.' There's no playbook, no pipeline discipline, no shared process.
Scenario 4
An investor has a checklist for every deal: market, team, product, terms. They run the checklist on every opportunity. They don't have a target number of deals per year; they do as many as pass the checklist.
Section 11
Summary & Further Reading
Summary: Systems vs goals is the frame that says: invest in the repeatable process (system) that makes your desired outcome likely, rather than fixating on the outcome (goal) itself. Goals set direction and give feedback; systems are what you control and improve. Run the system; let the goal emerge. Use it in personal productivity, in team and company execution, and in scaling. Avoid goal-induced distortion — gaming, short-term moves — by making the system explicit and managing it. The following resources develop the idea.
The source of "goals are for losers." Adams argues for systems over goals and illustrates with his own path (cartooning, fitness, business). Accessible and memorable.
Clear builds a full framework for habits as systems: small behaviours that compound. "You fall to the level of your systems." Practical and evidence-based. The habits lens is the systems lens for personal change.
Build-Measure-Learn is a system; product-market fit is the goal. Ries emphasises running the loop and letting the outcome emerge. The startup version of systems vs goals.
Drucker stresses focus on contribution and on doing the right things repeatedly. Execution as system rather than one-off goals. Foundational for management as process.
Newport argues for systems of focused work (rituals, blocks, rules) that produce output. The goal is quality work; the system is how you create the conditions for it. Complements Adams and Clear.
Leads-to
Margin of Safety
Margin of safety is buffer so that small failures don't cascade. Systems can build in margin: redundancy, review steps, quality checks. When you focus on the system, you can design for robustness. When you focus only on the goal, you often strip margin to hit the number. Systems support margin; goal obsession often removes it.
Tension
Repeatable Systems
Repeatable systems are the organisational version: a playbook that can be run by many people in many places. Systems vs goals says to build that. The tension: repeatable systems can become rigid. The goal (e.g. customer outcome) can remind you what the system is for. Use goals to validate and refine the system, not to replace it.
