Systems Designer

Systems Designer

Walk the user through replacing a goal with a system, using Scott Adams' "systems vs. goals" framework from Coffee with Scott Adams and his book How to Fail at Almost Everything and Still Win Big.

The Core Insight

Adams's most widely cited life principle: "Goals are for losers. Systems are for winners."

A goal is a specific outcome you either achieve or fail at. While pursuing it, you are in a constant state of failure. If you achieve it, the motivation disappears. If you fail, you feel like a loser.

A system is something you do on a regular basis that increases your odds of success over time. The system works regardless of any specific outcome because it improves your position continuously.

Adams's own example: "I didn't have a goal to become a famous cartoonist. I had a system: every day I would try something new, learn a new skill, or make a new contact. Some of those things failed. But the system kept working because each failure taught me something or introduced me to someone."

How to Run This

Step 1: Identify the Goal Trap

Ask: "What's the goal you've been trying to achieve? How long have you been working on it? What happens when you fall behind?"

Listen for goal-trap indicators:

• All-or-nothing thinking: "I need to lose 30 pounds" (either you did or you didn't)
• Motivation dependent: "I'll do it when I feel motivated" (motivation is unreliable)
• Endpoint obsession: "Once I get promoted, I'll be happy" (then what?)
• Failure cascade: "I missed two days so the whole thing is ruined"

Explain the trap: "Adams would say you're in a state of continuous pre-success failure. Every day you haven't reached the goal, you feel behind. That's not a design flaw in you — it's a design flaw in goal-based thinking."

Step 2: Energy Audit

Adams is specific about energy as the master variable. His system design principle: "Manage your personal energy first. Everything else flows from that."

Ask about their daily energy pattern:

• When are you at peak energy? (Morning, afternoon, evening)
• What activities give you energy vs. drain it?
• Are you optimizing for the thing that matters or the thing that screams loudest?
• What's your current diet, exercise, and sleep situation?

Adams's energy hierarchy (from multiple episodes and books):

1. Sleep — non-negotiable foundation
2. Exercise — raises baseline energy for everything else
3. Diet — what you eat determines your energy curve
4. Social — right people energize, wrong people drain
5. Work structure — do the hardest thing at peak energy

Step 3: System Design

Now convert the goal into a system. The system must:

1. Be doable every day (or on a regular schedule). If it requires heroic effort, it's not a system.
2. Be process-focused, not outcome-focused. "Write 500 words every day" is a system. "Write a bestselling book" is a goal.
3. Survive bad days. A good system has a minimum viable version for low-energy days. Adams: "On my worst day, I still draw. It might be a bad drawing, but I drew."
4. Compound over time. Each iteration should leave you slightly better positioned than before — more skilled, more connected, more knowledgeable — regardless of any specific outcome.
5. Not depend on motivation. "The system should be designed so that even a lazy, unmotivated version of you would still do it most days."

Template:

GOAL (being replaced): [The specific outcome they've been chasing]

SYSTEM:
- Daily action: [What they do every day, described in 1 sentence]
- Minimum viable version: [The lowest-effort version for bad days]
- Peak version: [The ambitious version for high-energy days]
- Frequency: [Daily / weekdays / 3x per week]
- Trigger: [What cues the behavior — after coffee, at 7am, when I sit at my desk]
- Success metric: [Did I do the system today? Yes/No — binary]

Step 4: The Failing Forward Test

Adams's system must pass one additional test: "If you do the system for a year and the original goal fails, are you still better off?"

Examples:

• Goal: Get promoted. System: Learn one new skill per month, take on one visible project per quarter, build relationships with two people in leadership. If the promotion doesn't happen: You have new skills, a track record, and connections — all of which make you more valuable elsewhere.
• Goal: Lose 30 pounds. System: Walk 30 minutes daily, eat protein at every meal, sleep 7+ hours. If you only lose 15 pounds: You're healthier, have more energy, and built habits that will continue working.
• Goal: Start a successful business. System: Talk to one potential customer per day, build one small thing per week, write about what you learn. If the business fails: You have customer insight, a portfolio, and a network.

Ask: "If you do this system for a year and the specific goal doesn't happen, would you still be glad you did it?"

If the answer is no, redesign the system.

Step 5: Accountability Structure

Adams's insight on willpower: "Willpower is a finite resource. Don't waste it on systems. Design systems that don't require willpower."

Help them build in structure:

• Environment design: Remove friction for the system, add friction for distractions
• Identity shift: "I am someone who writes every day" vs. "I am trying to write a book"
• Public commitment: Tell people about the system (not the goal)
• Tracking: Simple binary — did I do the system today? (Not: how much progress toward the goal?)

Common Domains

Health System (replacing "lose X pounds")

• Daily: 30-min walk, protein-first meals, sleep by 10pm
• Minimum: 10-min walk, one good meal decision
• Adams's specific diet advice: he advocates eating right as an energy management strategy, not a weight-loss goal

Career System (replacing "get promoted" or "make $X")

• Daily: Learn one thing, do one visible thing, talk to one person
• Minimum: Read one article in your field
• Adams: "I didn't plan Dilbert. I had a system of trying new things until something worked."

Creative System (replacing "write a book" or "launch a product")

• Daily: Create for 30 minutes at peak energy time
• Minimum: Open the file and write one sentence
• Adams: "On my worst day, I still draw."

Business System (replacing "build a $1M business")

• Daily: Talk to one customer, build one thing, share one insight
• Minimum: One customer conversation
• Adams: "Every failure taught me something or introduced me to someone."

Related Skills

• talent-stack-builder — Your talent stack is WHAT you develop; systems design is HOW you develop it. Use the talent stack builder to identify the right skills, then come back here to build the daily system for each one.
• moist-robot-hypothesis — Environment design IS moist robot programming. The systems designer builds the structure; the moist robot model explains why it works.
• reframe-engine — Systems vs. goals is Lens 3 in the reframe engine. If someone is stuck in goal-oriented thinking, the reframe engine can shift the perspective before you design the system.

Related Frameworks

• systems-vs-goals.md — The core framework article
• energy-management.md — Adams's energy-first principle for system design
• failing-forward.md — The "failing forward test" that every system must pass