The job description usually says something like "strategic partner to the CEO."

It's one of those phrases that sounds meaningful and says almost nothing. Every COO candidate uses it. Every job posting includes it. And almost no one stops to ask what it actually means to do it well.

I've had the privilege of working alongside some extraordinary leaders over my career. What I've learned, slowly and sometimes the hard way, is that being a genuine thought partner to a CEO is one of the most nuanced, most demanding, and most rewarding things the COO role requires.

It is also almost nothing like what people imagine when they hear the phrase.

It starts with understanding what the CEO actually needs, which is rarely what they're asking for.

CEOs are, by nature and necessity, forward-facing. They live in the space of what's possible: the next opportunity, the next phase, the next version of the organization. That orientation is exactly what organizations need from their chief executive. It's also what makes them hard to be a genuine thought partner to.

Because what a visionary leader often needs most isn't someone to affirm the vision or execute the plan. It's someone who can slow the conversation down long enough to ask: have we thought this all the way through? What are we assuming? What does the organization need to be true for this to work, and is it true yet?

That's not a comfortable role to play. It requires a combination of intellectual confidence and relational security that takes time to develop. You have to be secure enough in the relationship to push back without making it feel like opposition. And you have to be genuinely invested in the CEO's success, not in being right.

The temptation in this role pulls in two directions. One is to defer too readily, becoming a sounding board that only reflects the CEO's own thinking back at them. The other is to push back too reflexively, turning every strategic conversation into a debate. Neither is thought partnership. Both are failures of presence.

I've caught myself leaning toward both at different moments. The work is staying in the harder, more honest middle.

Real thought partnership requires you to hold two things simultaneously.

The first is the vision: the CEO's ambition for the organization, their instinct about where things are going, their read on what the moment requires. You have to understand it deeply enough to advocate for it, translate it for the team, and defend it when it's under pressure.

The second is the reality: what the organization can actually hold right now, what the team has capacity for, what the finances will support, what the governance structure will allow. You have to understand that deeply enough to be honest about it, even when honesty is inconvenient.

The thought partner's job is to hold both of those things at the same time. Not to choose between them, but to help the CEO navigate the distance between them.

That navigation is where the real strategic work happens. Not in the vision, and not in the reality, but in the honest conversation about what it will actually take to close the gap.

You have to be willing to be the one who says the hard thing.

Every organization has a version of the conversation no one wants to have. The budget that doesn't actually work. The hire that isn't performing. The strategy that made sense six months ago and doesn't anymore. The board relationship that has quietly become a liability.

The thought partner's job — maybe the most important one — is to be the person who brings that conversation to the surface. Not to create conflict, and not to be the voice of doom, but because the CEO needs at least one person in the room who will tell them what's actually true rather than what's comfortable.

That requires a specific kind of courage. Not the loud kind — not the dramatic confrontation or the principled resignation. The quiet kind. The willingness to say, in a calm and direct voice, in a private moment: I think we need to talk about this. Here's what I'm seeing. Here's what I'm worried about. What are you thinking?

I've had versions of that conversation at meaningful moments in my career. They are almost always uncomfortable. They are almost always necessary. And they are, in my experience, the moments that define whether a CEO-COO partnership is genuinely functional or merely cordial.

The best thought partnerships are built on explicit trust and lane clarity.

One of the most useful conversations I've had in any senior role is the one where the CEO and I get explicit about how we work together. Not just what we're each responsible for, but how we communicate, how we disagree, how we make decisions when we see things differently, and what each of us needs from the other to do our best work.

That conversation sounds obvious. It almost never happens organically. And the organizations where it doesn't happen — where the CEO-COO relationship runs on assumption and inference rather than explicit understanding — are the ones where the partnership eventually creates friction rather than relieving it.

The COO who invests in that conversation early, who creates the conditions for genuine partnership rather than waiting for it to emerge, is the one who becomes genuinely indispensable. Not because they're irreplaceable, but because the trust they've built makes the whole organization function better.

That, in the end, is what thought partnership actually means. Not a seat at the strategy table. Not a title that implies proximity to power.

A relationship solid enough that the organization can move through hard things and come out the other side better for having navigated them together.