When a CEO Pattern Becomes Your Responsibility
How senior executives recognize CEO patterns, assess business impact, and decide when it’s time to have a courageous conversation.
If my writing has value to you, your ‘like’ has value to me. Click the heart—it helps by raising this article’s profile on Substack. Thank you for the gift!
The hardest conversations with a CEO aren’t the ones where trust is broken. They’re the ones where you respect the CEO, believe in the mission, and still find yourself quietly managing the fallout of how they operate under pressure.
A comment undercuts your team. A priority shift pulls you off strategic work. Expectations aren’t clear, followed by frustration when they aren’t met.
Each instance, on its own, feels manageable. You adjust and move on.
Because you’re capable, you make it work.
Until you realize you’re dealing with the same dynamic again.
That’s the moment to ask:
Am I managing incidents, or tolerating a pattern?
And if it’s a pattern, especially one involving the CEO, when does it become your responsibility to name it?
Recently, I worked with a senior leader who faced this exact dynamic.
Over nine months, he experienced multiple “small” situations that, taken individually, didn’t justify confrontation.
When we laid three of them side by side, the sequence was nearly identical each time: shifting expectations, frustration under pressure, work pulled back upward.
The breakthrough came from seeing the repetition.
Once the sequence was visible, the focus shifted from fairness to impact.
We stopped debating what had just happened and mapped what kept happening. We compared moments. We identified what repeated.
Then the questions changed.
What is this dynamic doing to execution?
What is it teaching my team?
How is it shaping how we operate under pressure?
What behaviors are being rewarded or punished?
The answers were uncomfortable but clear.
Strategic work was stalling because he kept getting pulled back into execution. High performers were becoming cautious. Autonomy was shrinking. Work was flowing upward instead of scaling outward.
And eventually, we named the final layer: the cost to his role. His scope was narrowing. His leadership was being redirected from building to buffering.
When you stay inside a single incident, you debate details. When you zoom out, you see consequences.
Patterns reveal impact. Incidents invite debate.
The shift happens when you move from incident thinking to pattern thinking. You trace the sequence. You compare across moments. You articulate the impact. You name the cost.
That’s how friction turns into data.
Now that you see the pattern, here’s the hard part.
Name it to the person who holds power over you.
Clarity doesn’t automatically create courage. You may question whether the CEO will change. You may calculate the risk to your reputation or your trajectory. In a power-imbalanced relationship, even clear feedback can feel like exposure.
If you’re capable of absorbing the impact, staying quiet can seem efficient. You stabilize volatility. You protect your team. You keep things moving.
When your role narrows instead of expands, when your energy shifts from building to buffering, when you hear yourself say, “I can’t believe I’m dealing with this again,” those are signals.
Silence isn’t neutral. It builds pressure.
I’ve seen the alternative. Another client never named the pattern. Week after week, she absorbed it. Told herself it wasn’t big enough to confront. Until one day, she was done. No dramatic blowup. Just accumulated frustration. And then she quit.
At senior levels, there’s a point where avoiding the conversation stops being prudence and starts being participation.
Instead of asking, “Is this worth bringing up?” ask, “Is it responsible not to?”
Managing up is difficult because the person you need to speak to holds authority over you. Yes, the risk is real.
But so is the responsibility that comes with your role.
Even once you decide to act, another fear remains.
What if it goes badly?
We often define success as agreement or change. But you don’t control the outcome.
What you control is whether you speak clearly, grounded in business impact rather than frustration.
From there, the response tells you something.
If the response is reflective, growth is possible.
If the response is defensive, you’ve learned something about the limits of the environment.
Your job isn’t to engineer a “good” conversation. It’s to surface reality.
Clarity first. Outcome second.
From that place, you can decide what comes next.
So how do you know it’s no longer a small thing?
Repetition.
You’re having the same debate again. The same frustration. Your energy contracts. Your team adjusts to avoid volatility.
No single moment demands confrontation.
But together, they begin shaping how you lead and how the company operates.
That’s the threshold.
At that point, you’re not managing an incident. You’re responsible for the conditions under which your team and the company performs.
That responsibility requires clarity. It requires the willingness to name what you see, and the discipline to let the response inform you.
That is senior leadership.
– Amanda
I work with Founders & C-Suite Executives on three key levels:
Strategic: Strengthen clarity and decisiveness in complex, high-stakes environments.
Leadership: Evolve and scale your leadership capabilities in line with what the business needs.
Inner Work: Address internal patterns that shape how you operate under pressure so you can lead with intention and sustainability.
I offer a complimentary discovery session to assess fit. I’d love to hear from you.
A good reminder that senior leadership isn’t about absorbing friction
Really liking the content and format, Amanda!