Goals vs Systems: Worked Examples You Can Copy

A goal is the result you want: finish a novel, speak Spanish, have three months of expenses saved. A system is the thing you do repeatedly that produces that result: write 500 words every weekday, study for 20 minutes after dinner, move money on payday.

The popular advice says to forget goals and focus on systems. That's half right. Systems are what you actually do each day, so they decide whether anything happens. But a system with no goal has no direction and no finish line. The useful question isn't "goals or systems?" It's "how do I turn this goal into a system I'll keep running?"

This post answers that with three worked examples, each laid out as a goal, the subgoals and microgoals under it, and the daily rule that keeps it moving.

Where the idea comes from

Two books made "goals vs systems" a common phrase. Scott Adams argued in How to Fail at Almost Everything and Still Win Big (2013) that goals leave you in a state of pre-success failure until you reach them, while a system is something you either did today or didn't. James Clear took the idea further in Atomic Habits (2018): "You do not rise to the level of your goals. You fall to the level of your systems."

Both make the same practical point. Everyone who ran a marathon wanted to run it, and so did plenty of people who never did. The wanting doesn't separate them. What separates them is the training plan, followed on the days they didn't feel like it.

Goals vs systems, side by side

• A goal is judged at the end. A system is judged every day. "Save $3,000" is either done or not done in a year. "Move $60 to savings every Friday" is either done or not done this week.
• A goal is an outcome you don't fully control. A system is an action you do control. You can't decide to be fluent by March. You can decide to study for 20 minutes tonight.
• A goal ends. A system can keep going. When you finish the half marathon, the goal is over. The habit of running three times a week can outlast it.
• A goal tells you where. A system tells you how. You need both. A system without a goal is busy work. A goal without a system is a wish.

Why you still need the goal

It's tempting to drop goals entirely, but a goal does three jobs a system can't:

1. It picks the system. "Write every day" only makes sense because you want to finish the book. The goal is how you decide which system is worth running.
2. It gives you a stopping rule. Without an end point, you can't tell whether the system is working. "Three months of expenses saved" tells you when to stop, or when to change pace.
3. It lets you check the system. If you're writing 500 words a day and the draft still won't be done for three years, the system is too small for the goal. You only notice that because the goal exists.

So keep the goal, but hold it lightly. Look at it once a week. Spend your days on the system.

How to turn a goal into a system

The method is the same for all three examples below:

1. Write the goal as a result you could check. "Get better at Spanish" becomes "Hold a 10-minute conversation in Spanish with a tutor, by 31 March."
2. Work out the smallest daily action that gets you there in time. Divide the work by the days available. If the answer is uncomfortable, change the deadline, not the maths.
3. Name the daily action as a concrete output. Not "study Spanish" but "one lesson: past tense of -ar verbs." You should be able to tell, without thinking, whether today counts.
4. Make a visible record that shows a missed day. A streak is the simplest one: a number that goes up each day you do the work and resets when you skip.

In GoalTracker this maps onto the three levels of the tree. The goal is the result. Each subgoal is one unit of the system, sized so you can finish one in a day. Microgoals are the small checkable steps inside a subgoal (for more on those, see the microgoals framework). The flame counter at the top of the app counts the days in a row on which you finished at least one subgoal. That count is your system's score.

Worked example 1: Write the first draft of a novel

The goal: a 60,000-word first draft.

The system: 500 words every weekday. That's 120 writing days, about 24 weeks, or just under six months. If six months is too slow, the maths tells you the fix: 750 words a day brings it to roughly 16 weeks.

The tree:

• Goal: First draft of the novel, 60,000 words
  • Subgoal: 500 words: Mara arrives at the station
    • Microgoal: Reread yesterday's last paragraph
    • Microgoal: Write 500 words
    • Microgoal: Note one thing to fix later (don't fix it now)
  • Subgoal: 500 words: the argument with her brother
  • Subgoal: 500 words: the letter under the door

Each subgoal is one writing session, named after what it produces. You add tomorrow's subgoal at the end of today's session, while you still know what happens next. That removes the worst moment of any writing habit: sitting down and not knowing where to start.

What the streak measures: days in a row with a finished session. It doesn't measure how good the words are, and that's deliberate. A first draft is a volume problem. Quality is the second draft's job.

Worked example 2: Hold a conversation in Spanish

The goal: a 10-minute conversation in Spanish with a tutor or language partner, by 31 March.

The system: 20 minutes of study every day, plus one speaking session every Sunday.

The tree:

• Goal: 10-minute conversation in Spanish by 31 March
  • Subgoal: Lesson: present tense of -ar verbs
    • Microgoal: Review 15 flashcards
    • Microgoal: Read one short dialogue out loud
    • Microgoal: Write three sentences about your day
  • Subgoal: Lesson: asking questions (qué, dónde, cuándo)
  • Subgoal: Sunday speaking: 10 minutes with a language partner

The daily subgoals keep the streak alive. The Sunday one is the real test of whether the system is working: if the conversations aren't getting easier after a month, change the lessons, not the goal.

Why microgoals help here: on a tired evening, "study Spanish" is easy to skip. "Review 15 flashcards" takes four minutes, and once you've done it the rest of the lesson usually follows. That's the same trick as the embarrassingly small minimum in how to build a daily streak.

Worked example 3: Build an emergency fund (a system that isn't daily)

The goal: $3,000 saved within 12 months.

The system: move $60 to a separate savings account every Friday. That's about $3,120 over 52 weeks, so a couple of missed weeks won't sink it.

The tree:

• Goal: $3,000 emergency fund by next September
  • Subgoal: Set up a separate savings account
  • Subgoal: Friday transfer: $60
  • Subgoal: Monthly check: total saved vs. $250 a month
    • Microgoal: Check the account balance
    • Microgoal: Note one expense to cut next month

This one is included on purpose, because not every system is daily. A daily streak is the wrong score for a weekly habit. It would reset every Saturday and teach you that the streak doesn't matter. For systems like this, the better check is a short weekly review: did this week's transfer happen, and is the total on pace?

If you want a daily streak alongside it, pair the savings goal with a genuinely daily system, such as logging every purchase before bed. Don't stretch a weekly system to fit a daily score.

How streaks keep a system honest

A goal can't tell you whether you did the work today. A streak can. That's why the two work well together: the goal points the direction, and the streak shows whether the system actually ran.

A few details about how the flame counter in GoalTracker works, so it doesn't surprise you:

• It counts a day when you tick off at least one subgoal that day. Ticking microgoals alone doesn't count, which is another reason to keep subgoals day-sized.
• If you haven't finished anything yet today, yesterday's streak still shows. It only resets if a whole day passes with nothing ticked.
• Unticking a subgoal removes that day's credit, so the number stays honest.
• Days are counted in your local time, so a daylight-saving clock change doesn't cause a false miss.

If you'd rather track a habit on paper, the printable 30-day habit tracker template does the same job: one box per day, and an empty box is impossible to ignore.

Common mistakes

• Making the system too big. "Write 2,000 words a day" survives about a week. Start with a daily action small enough that you'd do it on your worst day, then grow it.
• Only tracking the goal. A progress bar that sits at 4% for a month is discouraging. Track the system daily and look at the goal weekly. A short Sunday weekly review of your goals is the place for that look.
• Changing the goal instead of the system. If you're behind, first ask whether the daily action is the right size. The goal is usually fine; the system is usually too vague.
• Floating tasks with no goal. A system that isn't attached to any goal slowly turns into a to-do list. That's one of the reasons most goal trackers fail.
• Waiting for a clean start. A system can start on a Wednesday afternoon. Do today's smallest version and let the streak begin.

Try it with your own goal

1. Pick one goal and write it as a result you could check, with a date. If nothing comes to mind, browse these bucket list ideas grouped by category.
2. Divide the work by the days available to find the daily action.
3. Open GoalTracker and add the goal. Add today's action as a subgoal, named after what it produces, with two or three microgoals if it has steps. It's free, needs no account, and your goals stay in your browser.
4. Finish it and tick it off. That's day one of the streak.

If the goal is still too big to see the first subgoal, start with how to break a big goal into subgoals, then come back and turn the result into a system.