The CEO Who Stopped Fighting Change — and Started Leading It

He sat down across from me at a coffee shop in Thousand Oaks and said, "I don't know if I'm the problem or if everyone around me is." That's actually a good place to start. Most executives I work with in Ventura County arrive either convinced they're completely right or completely broken. This man was neither. He was a seasoned CEO, brought in to stabilize a professional services organization that had been bleeding talent, losing clients, and drifting without direction for three years. The board had recruited him specifically because of his track record. Six months in, he was ready to quit. His board was whispering to staff behind his back. His staff was stonewalling every initiative. And he was spending more mental energy managing his anger at the people above him than actually leading the people below him. That's where we started.

The Situation

The organization had been around for over two decades. It had a good reputation in the community, solid name recognition across the Conejo Valley, and a long history of doing decent work. It also had a culture that had calcified around a former executive director who had run things informally, by relationship, and with very little accountability structure. When that person left, they left a vacuum and a staff that had learned to operate without clear direction, without performance standards, and without anyone holding the line on anything.

The board hired this CEO to change that. He came in with a clear mandate: modernize operations, rebuild client trust, and create a sustainable organizational structure. He had done this before at a similar organization in the Central Valley. He knew the work. What he didn't know was what he was walking into politically.

Within his first ninety days, three things were already wrong:

• Two board members were openly socializing with longtime staff and sharing concerns about the CEO's "abrasive" style, which mostly meant he expected accountability
• A senior manager who had been passed over for the CEO role was actively running a counter-narrative among employees, framing every new policy as a threat to the organization's culture
• The CEO himself had started reacting to these problems defensively, which gave his critics more ammunition
• The board had never documented what success looked like, what authority the CEO actually had, or how disagreements between board and leadership would be resolved

By the time we met, none of his major initiatives had gotten traction. Not one. Six months of work and the organization was essentially where it had been when he arrived, except now there was open tension where before there had just been drift.

The Board Problem

Boards are complicated in Ventura County. This isn't a criticism. It's just a fact of how these organizations are built. Many board members in local nonprofits and professional services groups are deeply embedded in the community. They know the staff personally. They've been around for years, sometimes decades. They care genuinely. And sometimes that care becomes interference.

In this case, two particular board members had been with the organization since its early years. They knew the old executive director well. They liked him. They were uncomfortable with the pace and tone of change, and instead of bringing those concerns to the CEO directly, they were voicing them sideways, to staff, in hallways, over coffee. Not with malicious intent necessarily, but the effect was corrosive.

What this looked like on the ground:

• Staff would hear board members express doubt about a new policy, then push back on the CEO with board sentiment as cover: "Even the board is questioning this"
• The CEO would bring a proposal to the board, receive lukewarm approval in the meeting, and then discover that the same board members had already undermined it informally before implementation began
• Because nothing was in writing, nothing was actually agreed to. Every conversation could be revisited, revised, or quietly ignored
• The CEO had no documented authority to act, which meant every decision felt like it required political negotiation rather than execution

This is not unusual. In my forty years of executive coaching in Ventura County and beyond, I've seen this pattern repeat itself across organizations from Camarillo to Ojai. A new leader is brought in to change things, and the existing power structure, even when it nominally wants change, resists it because change means loss of the familiar. The board wasn't trying to sabotage their CEO. They were trying to protect something they loved. But protection and sabotage can look identical from where the CEO sits.

What He Was Thinking vs What Was Happening

Here's where the coaching work got interesting.

In our second session, I asked him to walk me through a typical Monday. Not his schedule. His thoughts. What was running through his mind from the time he got in his car to the time he sat down at his desk. He paused for a long time. Then he started talking, and what came out was a near-constant internal monologue about the board. How they had set him up. How they hired him to fail. How they wanted the appearance of change without the reality of it. How the two board members who were most vocal were threatened by competence. How nobody in this organization actually wanted to be held accountable.

That internal narrative was running all day, every day. It wasn't fully wrong. Some of it was accurate. But it was consuming somewhere between thirty and fifty percent of his available mental and emotional bandwidth before he even had his first meeting of the day.

This is the thought coaching insight that matters: your thoughts about a problem are not the same as the problem itself, and sometimes your thoughts about a problem create a second problem that's worse than the first one.

He was reacting to the board from a place of grievance. That grievance, while understandable, was showing up in how he communicated, how he held meetings, how he responded when questioned. It was making him look reactive rather than strategic. And that, ironically, was confirming the very doubts his board members had about him.

The board problem was real. His thoughts about the board problem were making it significantly worse. We needed to work on both.

The Strategy: Board Alignment First

We made a decision early in our coaching work: nothing else changes until the board relationship is on solid ground. Not in theory. In writing.

This is the move most CEOs avoid because it feels confrontational or because they're afraid of what the documentation might reveal about the limits of their actual authority. But ambiguity is almost always worse than a difficult truth. When nothing is written down, every disagreement becomes a referendum on who is right. When expectations are documented, disagreements become conversations about what was agreed to.

We built a simple framework. It wasn't a legal document. It was a working agreement between the CEO and the board that covered four things: what decisions the CEO could make without board approval, what decisions required board input before action, how board members would communicate concerns about operations (to the CEO, not to staff), and what success would look like at twelve months and twenty-four months.

Getting this documented required two board sessions that were uncomfortable. The CEO had to present the need for clarity without making it feel like an accusation. We worked on the language together. He went in not as a man defending himself but as a leader proposing a structure that would make everyone's role cleaner. That framing made a difference.

The two board members who had been most problematic actually responded well once things were in writing. They weren't bad people. They had just been operating in an ambiguous space and filling it the way people do, with informal relationships and private conversations. Structure gave them somewhere better to put their energy.

Once that agreement existed, every conversation about operations had a foundation. When a staff member tried to use board sentiment as leverage, the CEO could say clearly, "Here is how the board and I have agreed to operate." That sentence, backed by something real and documented, ended a lot of conversations that previously would have dragged on for weeks.

Handling Resistant Employees

Once the board alignment was in place, we turned to the staff. This is where a lot of CEOs make a second mistake. They either assume everyone can change if given enough time and support, or they assume the resistant ones need to go immediately. Both of those assumptions cost organizations a lot of unnecessary pain.

The truth I've seen play out repeatedly, from large corporations like Amgen to small service organizations in Ventura County, is that employees in a resistant culture generally fall into three groups. The first group wants to change but needs leadership to be consistent before they'll commit. They've seen too many initiatives start and stall. They're waiting to see if this one is real. The second group is neutral and will follow whoever seems to be winning. The third group has a genuine stake in the old way of doing things, whether that's power, comfort, or identity, and will not change unless the cost of not changing becomes concrete and personal.

Here is what actually tells you which group you're dealing with:

• Watch behavior over ninety days of consistent, documented expectations. Words mean almost nothing in a culture of drift. Behavior patterns tell you everything.
• Note who raises concerns directly with you versus who complains laterally to colleagues. Direct concern is a sign of engagement. Lateral complaining is a sign of resistance.
• Give people one genuine conversation where you name what you're seeing and ask them directly what they need to get on board. Some people just need to be seen and heard. Others will use that conversation to continue negotiating the terms of their non-compliance.
• Be willing to make a decision. Prolonged ambiguity about whether someone stays or goes is more damaging to a culture than the departure itself.

In this case, the senior manager who had been running the counter-narrative was in the third group. Three months of documented expectations, one direct conversation, and a clear thirty-day performance plan later, she chose to resign. That resignation, handled with dignity and without drama, was the moment the broader staff understood that the change was real. Two people who had been fence-sitters became active supporters within weeks of her departure.

You cannot coach someone into wanting to follow your leadership. You can create the conditions where good people rise and people who won't follow become visible. Then you make decisions.

What Held After Coaching Ended

We worked together for about eight months. By the end of that period, several things had changed that I believe will last because they changed at the structural and cognitive level, not just the behavioral one.

The board relationship had a documented operating agreement that survived our coaching engagement. The CEO told me recently that it has now become part of how they onboard new board members. That's the kind of institutional change that outlasts any individual coach or consultant.

The CEO had also developed a different relationship with his own thinking. He still had frustrating days. He still dealt with difficult people. But he had learned to notice when his internal narrative was becoming the primary obstacle, and he had a practice for stepping back from it. Forty years of daily meditation has taught me that this skill, the ability to observe your own thinking without being controlled by it, is worth more than any strategic framework I could hand someone.

The organization stabilized. Turnover slowed. Client relationships improved. They brought in two new programs that had been on hold during the chaos. None of that happened because of a brilliant strategy. It happened because the CEO stopped fighting his environment with one hand while fighting his own thoughts with the other.