Writings · I
Why the Right Coaching Can’t Solve the Wrong Problem
Maurice Nicoleau
Reading Time - 9 Min Read
The pattern that survives three organizations, two coaching relationships, and a decade of genuine development work is not a skill deficit. It is diagnostic information.
This is for the executive who has logged the coaching hours, absorbed the feedback, and can describe the pattern that needs to change with more precision than most coaches would — and is still producing it. Not for lack of effort. Not for lack of intelligence.
There is a way to know what it is instead. A skill responds to context. New organization, new team, new coaching relationship — capability improves, the feedback lands differently, the behavior changes. The skill was the variable.
A pattern that follows a leader across all of it is something else. It reasserts itself with new people, new stakes, new frameworks layered on top of it. Whatever is generating the behavior was never what the development work was aimed at.
The strategic discussion. Formidable here — reading the room, sensing where power is settling, understanding the forces in play before stepping in. These are real capabilities. They hold until the moment arrives that requires setting direction rather than reading it. Entering the water before the current has declared itself.
Something shifts. A sudden need for more information. Another consideration worth examining. A reframing of the question that buys another beat, then another. By the time the decision is made, they are alongside whoever won. The team reads it as measured judgment. It is not.
It is a pattern so refined it has become invisible — including to the person running it. Two decades of this. Three organizations. Years of coaching addressing the visible — communication, influence, presence. None of it touches the question underneath. Not why the decision could not be made. Why being wrong had always carried a weight that had nothing to do with the decision itself.
A different room. The leader people want to work for. Retention numbers prove it. What the numbers do not capture is what the organization has learned over time — that this leader can be moved. Standards become opening positions. Accountability becomes a conversation. The team does not lose respect all at once. They simply stop bringing the problems that require a hard answer, because experience has taught them one will not come.
The burnout, when it arrives, gets called a workload problem. It is not. It is the accumulated cost of never having been able to let someone leave the room disappointed. Because disappointed, somewhere unexamined, has always felt one step away from gone.
Both have a reason for the pattern. Reasons they could articulate if asked. The first would say thoroughness. Gathering all available information before committing. The second would say care. Protecting relationships that make real work possible.
Both reasons are coherent. That is what allows the pattern to survive.
A coherent reason is not external to the pattern. It is part of the mechanism that keeps it invisible. Thoroughness is a defensible executive virtue. Care is a defensible executive virtue. The pattern attaches itself to virtues that can be defended, and the defense is sincere. What is being reported is what is available to consciousness.
What is not available is what the pattern is actually responding to.
Underneath the first leader’s thoroughness is the older experience of being wrong in a room full of people when the sense of self was still contingent on being right. When worth was not yet separate from performance. Losing the room did not just mean losing the argument. It meant losing something about the essence of who one was.
That structure does not dissolve when seniority arrives and strategic miscalculation is no longer a personal verdict. It persists, intact, into rooms where the conditions that produced it have been gone for thirty years.
Underneath the second leader’s care is not generosity. When a staff member withdraws, when a peer goes cold, when holding the line produces silence on the other side — that is not an interpersonal event. It activates a fear of being fundamentally alone. Not professionally sidelined. Alone. A terror that predates every role ever held. One that was never resolved, only outpaced by achievement.
Achievement is unusually effective at outpacing structures it does not resolve. A career powered partly by the energy of outrunning a fear is, by definition, a career in which the fear has been functional. The pattern does not get examined because it has been working.
That is exactly why it survives the development work that comes after.
What the two share is structure. Every senior leader has a version of it. The specific content differs — the pattern that runs, the fear underneath it, the conditions that produced it. What does not differ is the structure itself. A response formed under conditions that no longer exist, operating in rooms where it no longer belongs, surviving every development effort because no development effort was ever aimed at it directly.
There is a reason no development effort has been aimed at it. By the time seniority arrives, the pattern has been load-bearing for decades. It is woven into what worked. Examining it directly is not what the system rewards. Coaching does not reach it. Performance reviews do not surface it. Most leadership development is constructed to operate at the level above it.
What breaks a pattern of this kind is not a new framework. It is not a better coach. It is not more self-awareness layered on top of the awareness already present.
What changes the pattern is the part of the structure generating the response no longer treating the threat as present. Not the part that knows the conditions are gone. That part has known for years. The part still answering to the threat as if it were live.
The two are not the same part. They never have been. That is why the years of knowing have changed nothing.
The part that knows operates above. It can describe the pattern, locate where it came from, articulate what triggers it. It can do all of this with precision and produce no change in the response, because the response is not being generated at the level where the description is happening. The description is accurate. It is also operating in a register the response does not answer to.
That part is operating on older information. It was set up under conditions that, at the time, were real. A threat to worth. A threat to belonging.
Whatever the original was. The setup made sense. The response was correct for the conditions that produced it. What it has not done — what it has never done — is update.
Anything that reaches it has to operate at the same level. Not above it. Not adjacent to it. At the register where the response is still being generated. That is the structural requirement, and it is why the years of work have not produced the change. None of the work has been wrong. It has been operating one level up from where the answering is happening.
When the part still answering stops answering, the response stops. Not because it is being managed. Because there is no longer a threat being met.
The pattern is not being managed better. It is no longer there to manage.
The energy that went into holding it at bay, into managing what it produced, into compensating across decades of high-stakes rooms — that energy is no longer being spent there. The capacity that was load-bearing for the defense becomes load-bearing for the work. The ceiling did not get higher. It stopped being a ceiling.