Speaking AI at the Executive Level, Not Just IT

Speaking AI at the Executive Level, Not Just IT

When every executive needs to speak AI, not just the CIO, hiring decisions change in ways that are easy to underestimate. This article is for boards, CEOs, and search committees who want their next leadership hire to hold their own in conversations where artificial intelligence shapes budgets, clinical workflows, and risk. It covers what to look for and how to evaluate it.

The shift is already here. In most healthcare organizations, AI now touches revenue cycle, care management, network strategy, and quality reporting at the same time. That means the executives sitting around your leadership table need enough fluency to ask sharp questions, not defer every one of them to the technology function.

Why Every Executive Needs to Speak AI Now

The short answer: AI decisions no longer live in a single department, so the leaders who evaluate them cannot either. A finance leader who cannot pressure-test a vendor’s automation claim, or an operations leader who cannot tell a real efficiency gain from a repackaged one, slows the whole organization down.

This is not about turning every executive into an engineer. It is about judgment. The best leaders we place can read a proposal, spot the assumptions that will not hold, and know which questions belong to the technology team and which belong to them. That instinct is now part of the job description for roles that never used to touch it.

It also changes how executives collaborate. When the finance chief, the operations leader, and the quality officer all speak enough AI to challenge each other’s thinking, decisions get better and faster. When only one person in the room can engage the subject, everyone else is guessing.

What This Means for Your Next Leadership Hire

The bottom line: evaluate AI fluency the way you evaluate financial acumen or clinical credibility, as a real dimension of the role, not a nice-to-have. That starts with knowing what you are actually looking for.

We tend to separate fluency into three levels when we help clients think through a search:

• Conversational fluency. The executive can follow an AI discussion, understand the tradeoffs, and ask questions that move it forward.
• Evaluative fluency. The executive can judge whether a proposed tool fits the organization’s economics, workflows, and risk tolerance.
• Strategic fluency. The executive can see where AI reshapes the business model itself and can lead the organization toward or away from it.

Not every role needs all three. A hospital or health system leader running service-line growth needs evaluative fluency. A leader steering long-range strategy needs the strategic kind. The mistake we see is treating AI fluency as a single trait and either over-weighting it or ignoring it entirely.

This is also where the [same title can fail in two different organizations](https://carsonkolb.com/same-title-fails-in-two-organizations/). The level of AI fluency a role demands depends on the business model, the payor mix, and the maturity of the technology already in place. A generic scorecard misses that entirely.

How to Evaluate AI Fluency Without Faking It

The direct answer: test judgment, not vocabulary. A candidate who name-drops the latest tools may know less than one who calmly explains why a promising pilot never scaled. Buzzwords are easy to rehearse. Judgment shows up in how someone reasons through a real problem.

In interviews, we encourage clients to put a real decision in front of the candidate. Describe an actual proposal the organization is weighing and ask how they would evaluate it. Listen for whether they separate the technical questions from the business ones, whether they ask about data quality and change management, and whether they can name what would make them walk away.

Watch for two failure modes. The first is the executive who defers everything to the technology function and adds no independent judgment. The second is the executive who is overconfident, treats AI as a cure-all, and skips the hard operational questions. Neither one belongs in a senior seat where AI decisions carry real dollars and real clinical consequences.

This is one reason [a leadership hire is so hard to undo](https://carsonkolb.com/leadership-hire-you-cannot-undo-preparing-for-the-decision/). Fluency gaps rarely show up in month one. They surface later, in the meetings where a poorly evaluated investment was already approved and the money is already spent.

Where a Search Partner Earns Its Keep

The reality: assessing AI fluency in a healthcare executive is difficult to do from a resume, and most internal hiring processes are not built for it. Titles tell you almost nothing here. Two candidates with identical credentials can differ enormously in how they reason about technology decisions.

This is the work healthcare executive search is built for. We spend our time understanding not just what a candidate has done but how they think, including how they engage with the fast-moving parts of the business. When AI fluency is a real requirement for the role, we build it into the assessment from the start rather than hoping it surfaces on its own.

The takeaway for anyone weighing a search: decide, before you begin, how much AI fluency the role genuinely requires, and at what level. Write it into the profile. Then hold candidates to it the same way you would hold them to every other core competency. That single step keeps the requirement honest and keeps the eventual hire ready for the room they are about to join.