When to tell the CEO they are wrong — and how.
The most valuable thing a fractional operator can do — the thing no sycophantic internal hire will do — is tell the CEO something they do not want to hear. Done at the wrong moment or in the wrong way, it ends the engagement. Done right, it changes the trajectory of the company.
The role no one wants but every company needs.
There is a particular kind of loneliness that CEOs of early-stage companies describe when you ask them honestly about their operating experience. They have advisors who are careful. They have board members who are interested but not embedded. They have employees who are loyal and, by virtue of that loyalty, reluctant to say the thing that might be received badly. They have investors who see the board deck version of the company, not the operating reality. And they have a founding team who, if they are good, will tell the CEO hard things — but only within the political constraints of a team that has to work together after the conversation.
Into this environment walks the fractional operator. And one of the things that makes a fractional genuinely valuable — not just operationally useful but strategically important — is precisely the independence that comes from not being a permanent part of the system. The fractional does not have a promotion to lose. Their equity is limited or nonexistent. Their long-term employment does not depend on the CEO's approval of every position they take. This creates a structural condition for honest conversation that is genuinely rare at the leadership level.
The problem is that most fractionals do not use this structural advantage effectively. They get embedded in the organization, they start caring about the relationships, and they start calibrating their feedback the same way everyone else does — managing the political cost of the hard conversation rather than just having it. The instinct is understandable. It is also a fundamental abdication of the fractional role.
The discipline is not whether to have the conversation. It is timing and framing. Said too early, before credibility is established, the hard truth reads as arrogance from someone who does not yet understand the business. Said in the wrong frame — as a verdict rather than a concern — it creates defensiveness rather than reflection. Said too late, after the decision has been made and the organization has committed, it is not useful at all.
The timing problem: when you have earned the right.
There is no universal rule for when a fractional operator has established enough credibility to deliver a genuinely hard message. But there are signals. The CEO asks for your opinion on something outside your direct mandate. They reference something you said in a previous conversation as having been useful. They tell you something about the business they have not shared in a group setting. These are indicators that the trust account has been built to a level where a difficult conversation is possible without the message being filtered through defensiveness.
Before those signals are present, the fractional has to decide: is this hard thing urgent enough to say before the trust is fully established? The answer is sometimes yes. If the CEO is about to make a decision that will materially damage the business — a hire, a market bet, a funding structure — and the consequences are irreversible or near-irreversible, waiting for the trust account to build is the wrong call. You say it, you lose some relational capital, and you do it anyway because the alternative is worse.
But most of the hard conversations that fractionals face are not in this category. Most of them are about patterns rather than single decisions — a CEO who is micromanaging the team, a founder who is in denial about a market signal, a leadership team that is avoiding a necessary personnel decision. These pattern-level conversations can and should wait until the trust is there. Trying to have them before that trust exists almost always fails, not because the observation is wrong but because the CEO does not yet have enough experience of your judgment to give the feedback the weight it deserves.
The framing that makes it land.
The specific words matter more than most operators think. When a fractional says "I think you are making a mistake," the CEO hears a verdict. When a fractional says "I have a concern I want to share before we move forward," the CEO hears the beginning of a conversation. These produce different emotional responses and different conversational dynamics.
The frame that works most reliably has four components. First: signal that you are on the same side. "I want this to work as much as you do" is not a platitude when it is true — and in a well-scoped fractional engagement, it should be true. Second: name the specific risk, not the general concern. Not "I think the timing is off" but "I think we will launch before the support infrastructure can handle the volume, and the first cohort will churn before we can recover the CAC." Third: acknowledge the possibility that you are wrong and say what would change your view. "If the support team can get to two-hour response times by launch, I withdraw the concern entirely." Fourth: ask for a pause, not a reversal. "Can we have this conversation before we sign?" is a much easier ask than "I think we should not do this."
The reason the fourth component matters is that CEOs who feel they are being asked to reverse a decision will often defend it even when they are privately uncertain. Asking for a pause — for 24 hours, for a piece of additional information, for one more conversation with the relevant person — lowers the defensive response and creates the space for the CEO to update their view without it feeling like capitulation.
There are situations where this measured framing is insufficient — where the CEO needs to hear a clear, unambiguous statement that a decision is seriously problematic. In those situations, the language shifts: "I need to be direct with you about something. I think this is a significant mistake and I want to explain why." This is a different kind of conversation, and it requires a different kind of trust to work. But when it is the right call, it is right precisely because it does not hedge — and the CEO, whatever their initial reaction, usually knows they are being told something that matters.
The situations that always require the conversation.
There are categories of decision where a fractional operator who stays silent is not being diplomatically wise — they are failing at their job. The first is personnel. When a CEO is holding on to someone who is doing clear damage to the team — creating attrition, blocking the work, or poisoning the culture — and is not addressing it, the fractional's role is to surface it directly. "The person in this role is the reason three of your best people are looking for new jobs. I know this is a hard conversation but I do not think you can wait another quarter."
The second is capital. When a CEO is spending into a belief that the numbers no longer support — extending a runway assumption that has been invalidated, holding on to a cost structure that requires a growth rate the company is no longer achieving — the fractional operator who manages the P&L or the operations has to say it plainly. Not in a memo. In a conversation. "I want to walk through what the numbers are telling us, because I think there is a gap between where we think we are and where we actually are."
The third is the CEO's own behavior. This is the hardest category and the one most fractionals avoid. When the CEO is the problem — when their communication style is creating fear, when their involvement is removing the team's ability to act, when their public narrative diverges from the private operating reality — the fractional is often the only person in the room with the combination of access and independence to say it. "The way you handled that meeting has created a problem I want to talk about. The team is not sharing information with you because they are managing your reaction rather than the work."
These conversations are difficult. They are also the reason a good fractional operator is worth substantially more than a capable project manager. The project manager delivers the work. The fractional delivers the work and tells the CEO what the organization cannot tell itself.
- 01Establish credibility before delivering hard truths on major decisions. The trust account has to exist before you can make a significant withdrawal. For pattern-level concerns — not imminent costly decisions — wait until you have demonstrated enough judgment that the message lands with the weight it deserves.
- 02Name the specific risk, not the general concern. "I have a concern about timing" invites dismissal. "The support team cannot handle launch volume by Q2 and the first cohort will churn before we recover CAC" is a statement the CEO has to engage with. The more specific the risk, the harder it is to wave away.
- 03Ask for a pause, not a reversal. A CEO who feels they are being asked to reverse a decision will defend it even when privately uncertain. A request to pause — to verify one assumption, to have one additional conversation — is easier to grant and often achieves the same outcome.
- 04Never use a bad outcome to score points. When the thing you warned about happens, your job is to be the person in the room focused on what to do next. The CEO already knows you were right. Saying it out loud turns you from a partner into a critic, and critics do not get the access they need to be effective.
- 05The CEO's behavior is always on the table. The fractional operator who will address every operational problem but will not tell the CEO that their own behavior is the constraint is providing a fraction of the value they could. The conversation is hard. It is also the most important one you will have.
- 06Always private, always direct, never through the team. Hard truths go to the CEO first, in private, with full directness. Never surfaced through the team. Never implied in a group meeting. Never escalated to the board as a substitute for having the direct conversation. These are the rules of the relationship.
Frequently asked questions.
Is it ever appropriate to tell a CEO they are wrong in front of the team?
Almost never. The rare exception is when you are in a leadership team meeting and the CEO is about to commit the company to something factually incorrect — a number, a legal fact, a customer commitment that does not exist. In those cases, a gentle correction in the room is appropriate because the alternative is worse. But disagreements about direction, strategy, or priorities should always happen privately first. Publicly contradicting a CEO without prior private conversation is a trust-destroying move regardless of whether you are right.
How do you tell a CEO they are wrong when they are emotionally invested in the decision?
You start by acknowledging the investment, not dismissing it. "I understand why this matters to you, and I want to make sure we get the outcome you're aiming for" is not a manipulation technique — it is an accurate statement of your role. Then you shift to the specific risk: not the general case against the decision, but the one thing that, if it materializes, will cost the most. You are not trying to win the argument. You are trying to change the outcome.
What should a fractional operator do when the CEO ignores their concern and the bad outcome happens anyway?
Not say "I told you so" in any form. The moment a fractional operator uses a bad outcome to score points, the relationship dynamic shifts from partner to critic — and critics do not get the access they need to be effective. The right move is to be the person in the room who focuses on what to do next. The CEO already knows you were right. You do not need to say it. Demonstrating judgment in the aftermath is worth more than having been right before the fact.
When should a fractional operator escalate to the board?
Only in situations involving material misrepresentation, legal exposure, or a decision that the board has explicitly reserved for itself. Escalating to the board as a way of overriding a CEO decision you disagree with is almost always the wrong move — it ends the engagement, damages the CEO's relationship with the board unnecessarily, and signals that you operate outside the authority structure you were hired into. If the situation is genuinely severe enough to warrant board involvement, the right first step is to tell the CEO you believe it needs to go to the board, and why.
Working on this?
If this is the problem on your desk, a 30-minute intro is the fastest way to find out whether I can help.
Request an intro →