The Frameworks That Would Not Hold
We had built the whole machine. Courses, frameworks, diagnostics, the full apparatus for helping founders scale. For a stretch of two years it worked — revenue moved, founders got results, the model looked sound.
Then it stopped. Not all at once. One client would take the framework and bloom. The next would take the identical framework and quietly stall, then drift, then disappear. Same product. Same process. Opposite outcomes, week after week, until the pattern could not be ignored.
My co-founder and I sat with it for months. We assumed the problem was the machine — the wrong framework, the wrong sequence, the wrong niche. We improved the machine. The results did not change.
What finally broke the question open was more uncomfortable than any of our fixes. The frameworks were sound. The people running them were not. Where a founder was steady, the same process produced results. Where a founder was running on fumes, on fear, on a quiet belief that they were falling behind no matter what the numbers said, the framework became another stick to beat themselves with. The system was fine. The person underneath it was not.
By the time we understood this, it was too late for the partnership. My co-founder had burned out, the business wound down, and the lesson arrived with the invoice attached. I had spent years learning to change what founders do. I had almost never learned to change the state they were doing it from.
That gap is what this is about.
The State Beneath the State
Here is the observation that took me years to trust: every stubborn behaviour a founder shows you is doing a job.
The founder who cannot delegate is not lazy. Some part of them is protecting against a specific failure, a loss of control that once cost them something real. The founder who overloads their calendar is not disorganised. Some part is avoiding the silence where the doubt lives. You can remove the behaviour, and it grows back, because the job it was doing never got done another way.
Core Transformation starts from that premise and then does something unusual. Instead of fighting the behaviour, or even negotiating with it, it follows the behaviour down. It asks what that behaviour is trying to achieve, then what that achievement would give the person, then what that would give, one level at a time, until the chain arrives somewhere it cannot go any deeper.
What it finds at the bottom is almost never what people expect. It is not more ambition. It is not a sharper strategy. It is a state — a plain, quiet experience of being okay, of being whole, of being at peace. Everybody's version differs in its wording and its feel, and underneath the wording most people are pointing at the same handful of things: safety, love, presence, being enough.
That is the strange part. The founder chasing a nine-figure exit, the one grinding through eighty-hour weeks, the one who cannot rest — they are chasing a state, not a number. The number is the delivery mechanism they were taught to use. The state is the thing they actually want. Most have never noticed the substitution, and so they keep buying the number and wondering why the wanting does not switch off.
Where the Process Came From
Core Transformation was developed by Connirae Andreas and her sister Tamara Andreas, and published as a book in 1994. Connirae Andreas is one of the major figures of the NLP lineage — she co-authored some of the foundational early work with Steve Andreas, and spent decades refining processes that could be taught and repeated rather than performed by a gifted few.
The process sits on a presupposition that runs through the whole NLP tradition and back into the founders' original texts. In The Structure of Magic, Bandler and Grinder (1975) treated every behaviour, including the ones people most want to be rid of, as having a positive function. The presupposition is not sentimental — that everything happens for a good reason. It is tactical: if a behaviour persists against someone's conscious wishes, it is being maintained by something, and you will not remove it cleanly until you know what that something is protecting.
Robert Dilts and Judith DeLozier (2000), cataloguing the field, placed intention and identity at the higher levels of any change. Core Transformation is what you get when you take that structure seriously and refuse to stop at the first intention you find.
I want to be honest about the evidence here, as I try to be every time I teach this material. Core Transformation is a modelled process from within the NLP tradition. It is not the product of a controlled trial, and no large study has established it as an evidence-based clinical method. What it draws on — the idea that behaviour serves goals, and that goals sit in a hierarchy — is well supported. The specific five-step procedure is a practitioner's invention, and this article treats it as one.
The Logic of Going Deeper
Why does walking down the chain produce change where willpower does not?
The answer starts with an idea from outside NLP, in a 1960 book called Plans and the Structure of Behavior by George Miller, Eugene Galanter and Karl Pribram. They described the loop that runs all purposeful behaviour as Test, Operate, Test, Exit — compare the present against the target (test), act if there is a gap (operate), compare again, and stop when the gap closes. The part that matters here is what the target can be. A target is not one thing; it is one rung of a ladder. "Send the proposal" sits under "close the deal", which sits under "grow the company", which sits under something wordless the founder has never had to name.
Willpower attacks the wrong rung. It pushes the visible behaviour — delegate, rest, stop checking your phone — while the rung above it keeps pulling harder. That is why the old habit returns the moment the pressure rises: the higher goal was never satisfied, so the behaviour designed to serve it comes back online.
Deci and Ryan's self-determination research (2000) found the same shape from a different direction. Beneath the visible goals people pursue, a small set of deeper needs is doing the pulling — autonomy, competence and connection. When people chase surface goals that fail to feed those deeper needs, the success feels hollow and the drive does not switch off. Core Transformation reaches that layer on purpose and, crucially, satisfies it directly instead of promising it for later.
So the mechanism is not mystical. A behaviour is a strategy. A strategy serves a goal. A goal serves a deeper goal. At the bottom, the person arrives at a state that is not in short supply and does not depend on anyone's performance, including their own. Once that state is actually experienced — not understood, experienced — the higher behaviours reorganise on their own, because the job they were doing has finally been done.
What Arrives at the Bottom
Different people land on different words, and the words mislead if you take them too literally. Some arrive at "peace". Some at "love". Some at a plain sense of being okay, of being held, of being enough exactly as they are. Some describe it as presence, or as a quiet that has nothing to do with silence. A few describe something they can only call "being" itself.
Two warnings, because this is where the material gets oversold.
First, the core state is not a mood you have to manufacture. You are not building a peak feeling and hoping it lasts. If anything, the process works by removing the noise until a state that was already there becomes visible. That is why the description tends toward the ordinary — it is closer to a release than an achievement.
Second, the process does not ask you to become passive or indifferent. Founders sometimes hear "peace" and picture the ambition draining out of them. The opposite tends to happen. When the deeper need is met directly, the surface goal stops carrying the entire weight of the person's worth, and the work gets clearer and lighter. The ambition stays. The desperation leaves.
Jon Kabat-Zinn's work on mindfulness (1990) makes a similar observation from a different practice: the non-striving state, the present-moment awareness that stops treating every experience as a means to something else, is not the enemy of action. It is often the ground it grows from.
The Protocol: Five Steps
The process is done seated, eyes closed or soft, on one behaviour you genuinely want to change. Do not run it on a small irritation the first time. Pick something that costs you.
- Name the behaviour, not the verdict. State it plainly and without judgement: "I check email at 1am", "I redo my team's work instead of trusting it". You are describing the strategy, not prosecuting yourself for it.
- Ask what it is trying to get for you. Let the first answer arrive — usually something practical like "to stay ahead" or "to avoid embarrassment". You are not analysing the answer. You are taking it at face value as the intention.
- Ask what that intention would give you, and keep going. Take each answer and ask again, one level down. "If I stay ahead, what does that give me?" Then "if I have that, what does it give me?" Repeat until the chain stops producing a new answer and arrives at a state rather than an activity.
- Do not race to the end. Each level has to be felt, not recited. If you jump to "peace" without feeling the intermediate rungs, you have understood the map and skipped the territory. The change lives in the felt descent.
- Bring the state back up through the chain. Once the core state is present, carry it back up the levels, one at a time, and notice how each behaviour looks from inside it. The 1am email check is not forbidden. It is no longer needed, because the thing it was buying is already here.
Then test it in the real situation inside a week. A process that only works on the cushion is not a process. It is a mood.