Systems vs Goals: Why Scott Adams Is Right
Years ago, Scott Adams (the creator of Dilbert) wrote something that contradicts everything we're taught about productivity and entrepreneurship:
"Goals are for losers. Systems are for winners."
It sounds provocative. You've probably heard the opposite your whole life: "Define clear goals", "Be specific with your targets", "Measure your progress".
But there's something profound here that most entrepreneurs (anywhere) don't understand until it's too late.
The Problem with Goals
A goal is a singular destination. When you reach it, it ends. Then what?
Think about it:
- You want to make money → You get the money → Now what?
- You want a thousand followers → You reach a thousand → The dopamine fades
- You want to launch a SaaS → You launch it → Then reality hits
Goals have a fatal flaw: they depend on motivation to be achieved.
And motivation is a finite resource. Some days you have it. Other days you don't. Goals that depend on it are fragile.
Plus, when you reach a goal, there's a void. That moment you thought would be epic often feels... anticlimactic.
I've seen many entrepreneurs launch their first product, see it work, and then get stuck without knowing what to do next. The goal was the journey, not the destination.
Systems Are Different
A system is a repeatable process. It has no end. It doesn't depend on motivation.
Scott Adams describes it this way in his career:
He didn't set the goal "Become a famous cartoonist". Instead, he created a system:
- Draw every day (the system)
- Study what works in humor (the system)
- Submit to publications regularly (the system)
The system worked regardless of whether he felt motivated or not. Some days he drew well, other days poorly. But the system continued.
Eventually, Dilbert exploded. But not because it was the goal. It was because the system created enough attempts, enough learning, enough exposure.
How I See This in My Own Projects
When I built my first directories (like Gestorías Cerca de Mí with 900+ businesses), I didn't set the goal "Have a thousand companies in the database".
I created a system:
- Scrape data daily (automatic)
- Validate and clean information (process)
- Iterate on the UI based on feedback (cycle)
The goal emerged from the system. Not the other way around.
With my AI agent that discovers, analyzes, and publishes content automatically, the same thing. It wasn't "I want to publish 100 articles". It was "I want a system that publishes content autonomously".
The number of articles is a consequence of the system, not its purpose.
Why Systems Work Better for Entrepreneurs
In the context of bootstrapping without external investment, this is critical.
You can't depend on motivation when:
- You're validating an idea and nobody wants it yet
- You've been three months without revenue
- Your first SaaS has 5 users
- Nobody sees the potential you see
Motivation will evaporate. Guaranteed.
But if you have a system, you can keep going even when motivation is zero.
A system tells you: "Tomorrow I do this, regardless of how I feel". And that's what separates builders from talkers.
How to Design a System (Not a Goal)
Here's the practical difference:
Goal: "I want my SaaS to have a thousand users in six months"
System: "I publish a post about how I solved the problem my SaaS solves, twice a week. I respond to every comment. I iterate the product based on feedback. I talk to 5 new users every week."
See the difference?
The goal is the result. The system is the process that generates the result.
To design a good system:
1. Identify the activity that produces the result (not the result itself) 2. Make it repeatable (it can be automated, or a habit) 3. Measure consistency, not results (Did you execute the system today? Yes/No) 4. Iterate the system, not chase the goal
The Role of Automation
As a developer, I've discovered that the most powerful systems are those that can be automated.
My AI agent that iterates content automatically is a system that works even when I sleep. It doesn't depend on my daily motivation.
That's the ideal: a system that executes itself.
But even without automation, a system is stronger than a goal because:
- It's predictable
- It's scalable
- It's transferable (you can teach it to others)
- It doesn't depend on you being "inspired"
The Right Mindset
Scott Adams sums it up well:
Winners think in systems. Losers think in goals.
It's not that goals are bad. It's that they're weak as a starting point.
A goal without a system is a wish. A system without a goal is a direction.
What you need is both: a clear system you know works, and a general direction (the goal) so you know where the system is heading.
But your mental energy should be on the system, not the goal.
Practical Application Right Now
If you're building something:
1. Forget the short-term goal 2. Define the system you believe will generate that result 3. Execute the system consistently 4. Measure if the system works, not if you hit the goal 5. Iterate the system based on data
This is the opposite of what most people do. Most set an impossible goal, artificially motivate themselves, and when it fails, blame lack of discipline.
None of that. The problem was the starting point: a goal without a system.
Conclusion
Scott Adams isn't a billionaire by luck. He's a billionaire because he understood something fundamental: systems generate results. Goals only generate disappointment.
On your next project (whether it's a SaaS, a directory, an AI agent, whatever), start here:
What's the system?
Not "What's the goal?"
The answer to that question is what will take you where you want to go.
---
*What system are you using in your business right now? Or are you chasing goals without a process behind them? Tell me in the comments.*
