Why next year will be the same (unless you read the script first)

Why will next year look like this year?

Next year will look like this year because a resolution changes the target, not the Life Script writing the target. Most people rewrite the list every December without ever looking at the thing doing the writing. The list gets a new number, a new deadline, sometimes a new category entirely, and the pattern that produced this year’s list produces next year’s in the identical shape, just aimed somewhere else.

This isn’t a willpower story. Miss a resolution and the standard verdict is that you didn’t want it enough, didn’t plan well enough, didn’t have the right system. Sometimes that’s true. But the more common failure isn’t missing the goal. It’s hitting the goal and immediately setting a version of the same one again, without asking why that shape of goal keeps showing up in the first place.

In the SuperstateX framework, that shape has a name: the Life Script. It’s the pattern doing the actual authoring: deciding what counts as worth chasing, what counts as enough, and whether the account ever gets marked paid. A resolution is downstream of that. Change the resolution and the Life Script writing it is still fully in charge come February.

That’s the layer most goal-setting advice skips entirely. Productivity systems, accountability partners, better calendars: all of it optimizes execution of whatever the script hands down. None of it touches the script itself. So you can get measurably better at hitting goals for five straight years running and still notice, honestly, that the shape of your life hasn’t moved. Same script. Better throughput.

How you know the same script is about to run again

You know the same script is about to run again when next year’s list reads like this year’s with the nouns swapped. The clearest tell isn’t the content of the goal. It’s the shape underneath it, repeating across categories that should have nothing in common with each other.

Six patterns show up often enough to be worth naming directly.

The category changes; the ratio doesn't

Last year it was revenue. This year it's a fitness number or a book count. The specific target moves, but the gap between hitting it and feeling anything about it stays exactly the same size.

The list gets written alone, fast, with no real resistance

Ten minutes, no deliberation, and it feels obvious, because it isn't actually a new decision. It's the same default filling in this year's blanks.

You can predict February's list before January ends

By the third week you already sense you'll be behind, and you can more or less name the next list before this one's been formally abandoned.

Hitting the list doesn't change what you do next

Every item gets checked off and the immediate move is a bigger list, not a pause to register what hitting it was actually supposed to give you.

The list never names what would make it stop

Every resolution names a direction to move in. None of them name a finish line the script would actually accept as closed.

Someone who knows you well could have predicted it

Someone close to you could write a rough draft of next year's list without asking you a single question about it.

If two or three of these are already true for next year’s draft list, the list itself isn’t the problem worth solving first.

The Operating System behind the resolution

The Operating System behind the resolution is one of the three Life Scripts SuperstateX names: the Warrior, the Achiever, or the Pleaser. A resolution is an application running on top of it: the specific, visible behavior on the surface. The Life Script is the layer underneath, deciding what that application is even allowed to try to prove this year.

SuperstateX uses that exact metaphor on purpose. The Life Script is the software; the Operating System is the deeper layer it runs on, and it’s the layer the SuperstateX framework actually works with directly. The Warrior sets resolutions around self-sufficiency and endurance: do more alone, need less, prove nothing can break you. The Achiever sets resolutions around winning and ranking: hit a bigger number, beat last year’s version of yourself, stay ahead of the field. The Pleaser sets resolutions around being more useful: say yes faster, give more, become harder to leave. Three people can write three completely different lists and still be running the identical mechanism: a script deciding what has to be proven this year, and a resolution built to try to prove it.

That’s why swapping the resolution rarely changes anything on its own. The Operating System doesn’t read the specific goal. It reads whether the behavior fits the proof it’s already running. A goal that doesn’t fit gets abandoned quietly by February. A goal that fits gets chased hard, hit, and replaced, because the Operating System was never actually asking for that specific number in the first place. It was asking for evidence, and evidence has no finish line built into it.

A composite case

This pattern shows up most clearly at the turn of the year, when you sit down to set next year’s targets and the list writes itself in under fifteen minutes.

A composite: a founder in their late thirties, on a second company, hits every number on the list for three straight years: revenue, headcount, a specific title change. Each January the next version gets set, a little larger, and each year it lands exactly the way it landed the year before: relief for about a day, then a flat return to execution. The flatness gets filed as normal founder life. Most founders nearby describe something similar, so nothing about it looks like a problem worth naming.

What breaks it open is one question: what was last year’s list actually supposed to prove? Not what it produced. What it was for. The pause before an honest answer arrives is usually the longest pause in the whole exercise. The list was real. The company was real. What the list was supposed to settle internally was never specified. The Achiever script just needed a target large enough to occupy a full year, and nearly any target would have done the job.

Traced backward, the pattern almost always predates the company by a decade or more: a competitive season in school, an early job where hitting the number was the only thing that registered as approval. The business didn’t create the pattern. It gave the pattern a bigger surface to run on, and a longer runway before the repetition became impossible to explain away as coincidence.

Next year isn’t a blank page. It’s the same page, retyped in a different font.

What repeats vs what changes

What repeats is the mechanism; what changes is only the label on the goal. Laid side by side, the pattern is easier to see on paper than it is to feel in real time, in the middle of writing the list.

What looks new	What actually repeats	What it's really proving
This year's number is bigger than last year's	The gap between hitting it and feeling settled stays the same size	The script's proof was never really about the number
The category shifts: health, revenue, a relationship goal	The speed of setting the next list stays the same regardless of category	The proof-loop, not the domain, is what's running the list
The deadline moves: a new January, a new quarter	The response to hitting the goal is a new goal, not a pause	The account was never designed to close in the first place
The language sounds more deliberate, 'intentions' instead of 'resolutions'	The list still gets written in one sitting, without real resistance	Rewording the process doesn't reach the layer producing it

None of the left column is dishonest. The numbers are real, the effort behind them is real. But none of it is the layer that decides whether next year repeats. That layer is the Operating System, and it doesn’t respond to a better-worded goal.

Three starter moves to read the script before January

Three moves make the pattern visible enough to work with before you write next year’s list. None of them require waiting until December to start.

Write down what last year’s list was actually supposed to prove, after the fact, not before. Pick the resolution you hit and answer, in one sentence, what hitting it was supposed to settle internally. Most people take longer than expected to answer this. The length of the pause is the data: it tells you the target was clear and the proof it was chasing wasn’t.

Time the gap between finishing a goal and starting the next one. For your next completed target, a project, a number, a milestone, note the actual number of hours or days before a new target replaces it in your attention. A short, consistent gap isn’t ambition. It’s a script without a stopping condition built into it, and it’s worth knowing that before assuming next year’s list is a fully free choice.

Draft next year’s list two months early, then set it aside and don’t look at it until January. If the list you’d write in November is close to identical to the one you’d write in January under deadline pressure, that’s evidence the list isn’t coming from reflection. It’s coming from the same default running on a clock. A list built from an actual decision usually shifts when it’s given real time to sit.

None of these moves rewrite the Operating System. What they do is separate the resolution from the script writing it long enough to see the difference, a distinction that’s easy to miss without deliberately looking for it.

Why starter moves don’t usually rewrite the program

Starter moves make the script visible while it’s running. That’s real, and most people who try even one of the three above will read this year’s list differently than they did before starting.

What starter moves don’t typically do is change which script writes the list next January. A Life Script that installed itself before you had language for it, and has been writing your goals for two or three decades, doesn’t tend to release because it got named once. Naming it is the first step, not the last one. It changes when the layer underneath gets worked directly, addressed on its own terms rather than folded into a generic version of the pattern. A blog post, or a personal experiment run alone in November, isn’t built to do that.

That’s the layer the SuperstateX framework targets directly, and it’s also the subject of the annual life review, done honestly, a useful next read if this year’s list looked better on paper than it felt in the room. If the pattern in this post is already recognizable, the honest next step is finding out which Life Script has been writing your list, not guessing at it alone in December, but mapping it directly.

See which Life Script writes your list every year

The free 5-minute assessment names which Life Script is running you, what it costs you, and where the way out starts. From your results you can start a direct chat with Alex. No call, no pitch.

Find your script

Already know your script? The Rewrite Path is the guided version of the method: four stages and a four-week practice, built around it, and The Program is the full version, all 27 modules.

Part of: The SuperstateX Framework: The Three Life Scripts Running Successful Men

Frequently asked

Why do New Year's resolutions fail even when I have real willpower and a good plan? +

Willpower and planning improve execution, but they don't touch the layer deciding what's worth executing in the first place. That layer is the Life Script SuperstateX names: the Warrior, the Achiever, or the Pleaser. It sets the actual target underneath the stated resolution. A well-planned goal built on top of the wrong proof-loop still gets abandoned or immediately replaced, because the plan was never the part that was broken. The resolution changes every year. The script setting it usually doesn't, which is why the same shape of goal keeps returning even when the execution genuinely improves.

Is it bad to set goals at all if the Life Script is just going to write them anyway? +

No, goals aren't the problem, and this isn't an argument for setting none. The issue is treating the resolution as the actual decision point when it's usually downstream of one that already happened. A goal set with the Life Script named is a genuinely different act than one set on autopilot in December, even if the target on paper looks similar. Set the goal. Just don't mistake writing the list for having made the choice. The choice, if there was one, happened earlier, in whatever decided what had to be proven this year in the first place.

How is this different from just having bad habits or lacking discipline? +

Habits and discipline operate at the execution layer: how consistently you show up for the goal once it's set. The Life Script operates one layer below that, deciding what the goal is even trying to prove and whether hitting it will ever register as enough. You can have excellent discipline, hit every target on the list, and still find the list repeating in the same shape next year, because discipline was never the layer producing the repetition. That's the actual tell: if better execution keeps producing the same emptiness, the problem was never discipline to begin with.

How do I know which Life Script is writing my resolutions? +

Look at what the resolution is actually trying to prove, not what it's officially about. Resolutions built around enduring more alone, needing less help, or proving nothing can break you usually trace back to the Warrior. Resolutions built around winning, ranking, or beating last year's number usually trace back to the Achiever. Resolutions built around becoming more useful, more available, or harder to leave usually trace back to the Pleaser. A rough read is possible just from noticing the pattern honestly; a precise one requires mapping it directly, which is what the free assessment at superstatex.com is built to do.

Recognized yourself?

The free 5-minute assessment names which Life Script is running you, what it costs you, and where the way out starts. From your results you can start a direct chat with Alex. No call, no pitch.

Find your script

Already know your script? The Rewrite Path is the guided version of the method: four stages and a four-week practice, built around it, and The Program is the full version, all 27 modules.