If you've ever walked out of a meeting with your CEO wondering whether they actually care about your improvement program, the answer is almost certainly yes. The harder question is whether they care about it the way you think they do.

I've been thinking about this since a recent KaiNexus webinar with Bill Canady, CEO of Arrowhead Engineered Products and Chairman of OTC Industrial Technologies. Bill has spent more than 30 years leading companies through profitable growth, including scaling OTC past $1B in annual revenue. He's the author of The 80/20 CEO and From Panic to Profit. The session was unscripted and the Q&A came from a global audience, which made for an unusually direct view of what's actually going on in the executive's head when a CI leader walks in the room.

The short version: most CEOs want continuous improvement to succeed. What they need from CI leaders is more specific than most CI leaders deliver.

The CEO is already on your side

Bill's framing on this is worth quoting directly because it runs counter to a story many CI professionals tell themselves. Executives are not your skeptical audience. They want the company to run efficiently. They want their people to have meaningful opportunities. They want strong returns for investors. Continuous improvement is a substantial part of how that happens, and they know it.

What they're not always sure of is whether your specific program will help them get there.

This is the gap. Most CI leaders walk into executive conversations carrying a methodology to defend. The executive isn't questioning the methodology. They're trying to figure out whether the work you're proposing maps to the priorities they're already accountable for. That's a different conversation, and it's one most CI presentations don't have.

The framing that works

When Bill was asked what he wished more CI professionals understood about the CEO's perspective, his answer landed in three short pieces.

Here's the opportunity. Here's what I would do about it. Here's the impact.

Read that again. Notice what isn't in it. There's no methodology preamble. No "we're going to use the DMAIC framework." No history of lean. No taxonomy of waste types. The executive doesn't need to be educated on the toolset. They need to make a decision, and they need the information that lets them make it quickly.

Bill's example was deliberately stark. If you can walk in and tell a CEO that one specific change saves $100M against a $200M budget, you've just become the most interesting person in their week. The number doesn't have to be that big. The framing does. Specificity beats abstraction every time, and concrete numbers tied to real impact create the moment where the executive leans forward instead of nodding politely.

This is harder than it sounds. Pulling a single defensible number out of a complex system requires you to do the work the executive can't do for themselves. Most CI leaders avoid that work because it's exposing — putting a stake in the ground means you can be wrong. The executive is already wrong about plenty of things. They're not going to punish you for being roughly right with conviction. They will, eventually, lose patience with hedged generalities.

Understand the hand they're playing

Here's the part that surprises a lot of CI leaders. Your project is not the only thing on the executive's mind. Not even close.

Bill described the texture this way. Another business unit might be on fire. Capital might already be committed elsewhere. The board might be pushing for a different priority that will consume executive bandwidth over the next quarter. Your improvement project might be number four on a priority list that has hard limits on what gets attention.

When the CEO seems lukewarm about your work, it usually isn't a vote against improvement. It's the executive trying to figure out where your project fits in a portfolio of competing demands you can only see from your seat.

The CI leaders who become genuinely valuable at the executive level are the ones who help the CEO understand the hand they're playing. Not just "here's my project," but "here's how my project relates to the strategic objective you committed to with the board last quarter." That's a different conversation, and it's the one that gets resourced.

A practical move: before your next executive conversation, write down the three biggest priorities your CEO is publicly accountable for this year. Then write down how your improvement work connects to each one. If you can't draw a clear line for at least one, you're not ready for the conversation yet. Go do the connection work first.

What the CEO is actually deciding

Bill talked about his own job in three pieces, and understanding this helps decode what executives are doing when you're presenting to them.

First, decide where the company is going. In private equity, that's typically a 3x return on invested capital over a defined window. In public companies, healthcare systems, or family-owned businesses, the metric varies but the function is the same — the CEO is accountable for a definition of success that came from outside the company and isn't negotiable.

Second, measure and monitor. Watch the metrics, hear teams report out, ask what went wrong and what's being done about it.

Third, make the operating system a condition of employment. Lean, the talent process, capital allocation, strategic priorities — these aren't optional. People who won't use them eventually don't stay.

When you walk into a CEO's office, you are entering the second job — measure and monitor — with input that might affect the first job and that depends on the third job for follow-through. Most CI leaders only think about the second piece. The strongest CI leaders think about all three. They show up with information that helps the CEO refine where the company is going, framed in a way the operating system can actually execute.

The succinct ask

Bill's "succinct" framing applies to more than the opening sentence. The whole conversation should be tighter than most CI leaders make it.

A presentation that's three slides instead of thirty. A monthly update that fits on one page instead of in a deck. A request for resources that's stated in dollars and timeline, not in tools and methodology. A status report that leads with results and impact, not with activity and effort.

This is harder when you're proud of the work, and CI leaders are usually proud of the work for good reasons. The trap is confusing executive interest in the topic with executive interest in the details. They're interested in the topic. They're rarely interested in the details. The details belong in the documentation that supports your work, not in the conversation that gets the work resourced.

There's a related point Bill made about board meetings that translates to executive interactions generally. Board members think about your company maybe four times a year, totaling perhaps twenty hours. By Tuesday, you've already spent more time on the company than they will all quarter. The same dynamic exists between you and your CEO at the level of any specific improvement project. They've been thinking about it for the ten minutes before your meeting. You've been thinking about it for six months. Calibrate accordingly.

Visibility is your career path

A question came in during the session about how CI professionals can move into broader operations or P&L roles. Bill's answer was practical, and worth surfacing because it changes how to think about the executive conversations you're already having.

CI professionals know the business better than almost anyone else in the company. They know the factories, how they're laid out, what's working, what isn't. They sit at the intersection of strategy and execution in a way few other functions do. That knowledge is the foundation for an operations role, and CI is one of the few functions where you regularly stand in front of CEOs, segment leaders, and business unit heads.

The visibility is the asset. Every executive conversation is an audition for the next role, whether you're thinking about it that way or not. CI leaders who frame their work in executive language — focus, priorities, results, returns — get noticed. CI leaders who frame their work in methodology language — kaizen, A3, value stream — stay where they are.

That isn't a knock on the methodology. Bill is unambiguous that lean is the best tool he's seen for redeploying resources and laying out work, and he expects his teams to use it. The point is that when you're in front of executives, the methodology is the means, not the message. The message is what changed and what it produced.

The blunt version

If this whole post had to fit on a sticky note, here's what it would say.

Your CEO wants you to succeed. They need three things from you to make that easier. A clear opportunity, your specific recommendation, and the concrete impact. Connect your work to the priorities they're publicly accountable for. Keep it short. Lead with results.

The CI leaders who do this consistently aren't doing different work than their peers. They're framing the same work in language that lets the executive say yes faster.

Want to hear the full Ask the CEO conversation with Bill Canady, including the global audience Q&A on healthcare, AI, leadership change, and 80/20 thinking in practice? Watch the recording here →

See KaiNexus in action →