The GROW Model Grows Everything Except the Foundation
By Vasti Krügel
You had a good coach. The sessions were structured — GROW, or something adjacent, or a framework you learned to navigate over time. The goals were clear. The current reality was mapped honestly. The options were generated. The commitment was genuine. You left the session believing the plan.
And then, at some point between the session and execution, something interrupted it. Not dramatically. Not with a crisis. Just quietly — the same internal friction that had been present before you had the coach. The resistance that arrived at the same point it always does. The momentum that built and then, reliably, didn't hold.
The plan was not the problem. The coach was not the problem. You were not the problem.
The ground the plan was built on was.
What GROW Actually Does
The GROW model — Goal, Reality, Options, Will — is the global standard for structured personal development coaching. Developed in the 1980s and adopted across executive coaching, life coaching, and organisational development worldwide, it is a genuinely effective framework for what it was designed to do: map a clear path from a current state to a desired outcome.
It asks the right questions. What do you want? Where are you now? What could you do? What will you commit to?
What it does not ask is whether the architecture beneath those questions supports the answer.
GROW assumes the architecture is functional. It assumes that once the goal is clarified, the reality mapped, the options generated, and the commitment made — the person is capable of holding the goal and executing toward it. For a significant proportion of people, that assumption is correct. For the person whose operating architecture has a specific instruction that prevents holding certain outcomes, it is not.
The model is sound. The ground it assumes is sometimes not.
Why Doesn't Life Coaching Produce Lasting Change?
Because coaching, in almost every framework, works at the execution layer.
Goal-setting, accountability, action planning, mindset reframing, progress tracking — these are all execution-layer interventions. They work on what you do, how you plan, how you follow through. They are downstream of the architecture that determines what you can hold.
The ICF coaching framework, GROW, the Tony Robbins model, the various accountability-based programs — all of them ask: how do we get you from where you are to where you want to be? None of them ask: is the ground between here and there stable enough to hold the journey?
The person who has had a good coach, built good plans, committed genuinely, and still finds execution stalling at the same internal friction point — that person is not failing the coaching. They have found the ceiling of the execution layer. What is below that ceiling is the architecture.
GROW Model Limitations — What Coaching Frameworks Miss
The limitation is not in the questions. It is in what the questions assume.
“What do you want?” — assumes the person can access what they want without the architecture filtering it.
“What is in the way?” — assumes the obstacle is external, or at most a belief that can be reframed.
“What are your options?” — assumes the options are available to the person’s operating system.
“What will you do?” — assumes the commitment made in the session will hold against whatever runs when the session ends.
For the person whose architecture has a specific instruction running — when things build, interrupt; when belonging deepens, create distance; when the goal is within reach, manufacture the reason it cannot hold — the commitment made in the session is genuine. And the instruction is more persistent than the commitment.
Not because the person is weak. Because the instruction was written at a level that predates the coaching conversation. It does not respond to goal-setting. It responds to what the operating system considers safe.
I’ve Had Executive Coaching but My Patterns Keep Returning — Why?
Because the pattern is not in the execution. It is upstream of it.
Executive coaching works on highly capable people who have demonstrable ability to perform. They can execute. They have executed. They know how to set goals, build plans, manage time, lead teams. The stall is not a capability problem. It is a structural one — a specific point in the process where something interrupts, reliably, that has nothing to do with skill or intention.
The executive who has had multiple coaches and keeps finding the same ceiling — the project that stalls at the same stage, the promotion that arrives and doesn’t hold, the team dynamic that replicates itself across different teams — is not encountering a coaching problem. They are encountering an architecture problem. The coaching was building on ground that has a specific instruction running beneath it.
The coaching reached the execution layer. The instruction lives below it.
What Is Missing from Personal Development Coaching that Nobody Talks About?
The question of whether the ground can hold the plan.
Every coaching framework starts with the goal and works forward. None of them start with the architecture and ask: what can this person actually hold at the operating system level? What will the architecture allow, and what will it prevent regardless of intention?
This is the layer that is almost entirely absent from the coaching industry. Not because coaches don’t want to reach it — but because coaching frameworks were not built to reach it. They were built to support execution. They are very good at that. The architecture layer requires a different set of questions entirely.
“What is the specific instruction your operating system is running that interrupts execution at this point?” is not a coaching question. It is a structural one.
Why Do Action Plans Stall Even with a Good Coach?
Because the plan is built at the execution layer and the interruption is happening at the architecture layer.
The plan is sound. The accountability is present. The commitment is genuine. And at a specific point in the execution — reliably, predictably, often at the same stage — something interrupts. Not randomly. Faithfully. Because the same instruction is running every time.
The instruction was not addressed by the coaching. The coaching didn’t go to the level where the instruction lives. This is not a criticism of the coaching. It is a description of where the coaching was designed to operate — and where it wasn’t.
When the tools work but the pattern returns, the problem isn’t the tool. It’s the architecture underneath.
Alternatives to Life Coaching When Coaching Isn’t Reaching the Root
The question worth asking is not “which coach should I hire next” but “which layer hasn’t been addressed yet.”
Coaching addressed the execution layer. The interruption is happening below it. The architecture layer is not reached by a more detailed plan, a stricter accountability structure, or a different coaching methodology. It is reached by identifying the specific instruction running the interruption — the governing conclusion the operating system formed before language existed for it — and naming it precisely enough to work with.
That is not an execution-layer question. It is a structural one.
If you’ve worked with a coach — if the plan was sound, the accountability was real, the commitment was genuine — and execution kept stalling at the same internal friction point: the coaching was not wrong. The ground the coaching was building on had an instruction running that the coaching couldn’t reach.
That instruction has a name.
When the plan is solid and the execution still stalls, the problem is not the plan. It’s the architecture the plan was built on.
Scan My Code
The breath shortening before you open the document you committed to opening. The shoulders already carrying weight before the week has started. The specific moment in execution where the familiar resistance arrives — not dramatically, just quietly, exactly where it always arrives.
These are not signs that you lack discipline or commitment. They are signs that something below the execution layer has not been named yet.
The single code generating the friction has a name. Not as a general resistance — yours specifically, in your language, mapped to your data across every plan that has stalled at the same point. That’s what the X-Ray returns.