Picture this scenario: It’s Monday morning, and you are fired up. You have just finished a massive continuous improvement project. You and your team have been in the trenches for months, and the results are spectacular—you’ve cut defects by 30%. You are over the moon, your team is high-fiving, and you walk into the boardroom ready to share this incredible news with the leadership team.
You pull up your slide deck. You launch into the methodology. You bring up the Fishbone diagram, the 5-Whys analysis, and the Pareto chart.
But the moment you look around the room, the energy shifts. The CEO is checking their watch, looking like they have mentally checked out five minutes ago. The CFO is squinting at your charts like they are written in ancient Greek.
Does this sound familiar?
If you are like many Continuous Improvement (CI) practitioners, this is a painful reality. You have done the work. You have achieved the results. Yet, the people who need to know about it the most seem the least interested.
The hard truth is this: Being a master in continuous improvement doesn’t mean a thing if you can’t speak the language of leadership.
In this post, we are going to move past the tools and step into the boardroom. We need to discuss how to stop being viewed as “just a process person” and start presenting yourself as a strategic partner that executives cannot live without.
The Expert Paradox
Why do great results, great processes, and great stories go unheard?
It is often because we, as Impruvers, fall into a trap known as the Expert Paradox. The irony of this paradox is that the better you get at Continuous Improvement, the more you tend to speak a “foreign language”.
When we immerse ourselves in Lean Six Sigma, we learn a specific vocabulary. We talk about Gemba, Muda, Kaizen, DMAIC, and SIPOC. For us, this language is precise and efficient. But for executives who didn’t grow up in a Lean culture, it’s just noise.
It gets even worse for Lean practitioners because a good chunk of our jargon literally comes from another language—Japanese. You might think that dropping terms like Hoshin Kanri or Heijunka makes you sound more capable and sophisticated. You might think it shows off your expertise.
But the actual effect? It makes you sound out of touch. To a busy executive, you might come across as a “know-it-all” or even a bit arrogant. They aren’t trying to hear that. They don’t want a lecture on methodology; they want to know you understand their world.
If you want to influence leadership, you have to stop trying to pull them into your world of technical tools and start meeting them in theirs.
The Mechanic Analogy
Think about the last time you took your car to the mechanic.
When you walk into the shop, do you want the mechanic to sit you down and give you a 30-minute presentation on the specific brand of wrench they used? Do you want to hear about the diagnostic software’s version number or the molecular structure of the oil they are using?
No. You just want the dang thing fixed.
You want to be able to jump in your car, turn the ignition, hit the gas pedal, and go. The mechanic who can make that happen every time is the mechanic you are going to do business with.
Now, imagine if that mechanic stood there going on and on about their tools and procedures, but the car still didn’t run right. You would leave.
Executive leaders are the customers. You are the mechanic. The business is the car.
If you go into a meeting and talk endlessly about diagnostic tools (your charts and graphs) but fail to clearly articulate how you “fixed the engine” (the business problem), leaders will treat you exactly how you would treat that rambling mechanic: they will keep it moving.
Aligning with the P&L: The Language of ROI
So, if leaders don’t care about Hansei or Value Stream Maps, what do they care about?
They care about the health of the business. They care about:
- Risk mitigation
- EBITDA (Earnings Before Interest, Taxes, Depreciation, and Amortization)
- Capacity
- Growth
As you work your way up the corporate ladder to the C-Suite, these are the metrics that matter.
I am a huge fan of Lean tools. I love a good PDCA cycle or a standard work document. But when I enter a boardroom, I approach the conversation as if the people in that room have zero interest in any of that.
If you cannot tie your super-successful project back to the Profit and Loss (P&L) statement, then in their eyes, it didn’t happen. Or even worse—it did happen, but they view it as a waste of time because they can’t see the value.
If you are a CI leader and you cannot read a P&L, you are missing a critical skillset. You need to be able to identify the major cost drivers in your organization and develop plans to bring them down without compromising quality or capacity.
Executives speak the language of ROI (Return on Investment). Your salary, your team, and your time are investments they are making. They want to see what they are getting in return.
From “Manufacturing Guy” to Strategic Navigator
I used to work with a partner at a consulting firm who viewed us lower level associates strictly as “manufacturing guys.” It used to drive me crazy. It felt diminutive—as if there was a whole world of business we weren’t savvy enough to understand.
But how do we break out of that box? How do we move from being the “shop floor guy” to a Strategic Navigator?
The secret is to stop solving random problems and start solving the problems that leaders are losing sleep over.
It is absolutely possible that your boss expects you to be knee-deep in the weeds of daily operations. But if you stay there, you will get swallowed up chasing a million rabbits and catching none. You need to familiarize yourself with the leader’s strategic goals.
Don’t just guess. Get them to open up to you. Ask them: “What are you afraid of right now? What keeps you up at night? If we could solve one big issue this quarter, what would it be?”.
When you align your CI efforts with their fears and strategic goals, the conversation changes. Now you aren’t asking for permission to do a “Lean project.” You are offering a solution to their biggest headache. You are asking what it’s worth to them and what they are willing to spend to make that problem go away. Now, you are in business.
The Cost of Manual Reporting Calculator
Are you spending valuable time formatting slides instead of fixing problems? Estimate the annual cost of manual “Deductive” reporting.
The Inductive Communication Shift
Once you have the right focus, you need the right delivery. This brings us to a concept called Inductive vs. Deductive Reasoning.
Most engineers and CI professionals are trained to think and speak using Deductive Reasoning. This is the “storytelling” approach. We explain the journey from A to Z. We want to weave in every detail, every tool we used, every obstacle we overcame, eventually arriving at the conclusion.
We do this because we think it builds trust. We think we are taking them on an exciting journey. But to an executive, we are just distracting them from the work they need to get done.
Leaders communicate using Inductive Reasoning. This is the opposite approach. You start with the headline. You give the answer first.
The Deductive Approach (What to Avoid): “Well, we started by looking at the line, and we noticed some variance, so we did a 5-Whys analysis. Then we convened a Kaizen burst event, and the team came up with several ideas. We tested three of them…”
The Inductive Approach (What Leaders Want): “We reduced the defect rate by 30%.”
See the difference?
If you start with the outcome, the leader can immediately process the value. They might just say, “Great job, go do it again.”
If they do have questions, they will ask. And that is when you break it down—but you still stay organized.
- Leader: “How did you do that?”
- You: “We focused on three areas: We implemented quality at the source, we added a specific inspection point, and we switched to a more reliable supplier.”
This method—being concise, mutually exclusive, and completely exhaustive—is a show of respect for their time. It proves you understand the pace at which they operate.
Creating a Cadence of Impact
Finally, you need to change how frequently you communicate.
I know CI leaders who only report their progress to executive leadership once a year. These sessions are often miserable. The leader sits there for a day listening to people drone on about activities rather than impact.
You need to create a Cadence of Impact. Do not make leaders wait years, quarters, or even months to hear about the good news. They need a constant feed of success.
You have to be part Lean expert and part Marketer.
Here are three ways to do this effectively:
- The One-Pager: Learn how to write a one-page executive summary. Focus 90% on impact and 10% on activity. Show the ROI right at the top. Link it to the P&L immediately after.
- Visual Evidence: Use before-and-after pictures. Pictures tell a story that data cannot. Without a picture, there is always room for doubt. With a picture (or video), the impact becomes real.
- Scream from the Rooftops: Every success story, every goal achieved, and every problem solved should be broadcast. Err on the side of being a little obnoxious about it. People might complain about your volume, but they will never complain about your results—especially if those results help them sleep at night.
Your Immediate Call to Action
If you want to start bridging this gap today, here is a simple homework assignment.
Pull up your current project list. Look at every single project you are working on. Now, try to tag each one to a specific corporate strategic goal.
Take it a step further: Pull up the P&L (or ask a finance partner for help). Rank the top cost drivers of the business. Can you draw a direct line between your projects and those costs?
If you cannot tie your project to a strategic goal or a P&L line item, you need to be honest with yourself: That project is not going to be prioritized by leadership. It might be time to pivot.
A New Tool for Impruvers
We know this reporting process can be tedious. That is actually why we launched a new feature at Impruver.
We now allow you to create “Success Stories” directly out of your projects, goals, and action items. These stories get distributed automatically to key leaders throughout your organization. It creates that endless drip of good news—that Cadence of Impact—without you having to build a new slide deck every week (or ever).
It helps leadership see the value you bring to the table, in a format they actually want to read.
If you want to see how this works and how we can help you speak the language of leadership, hit me up at impruver.com and book a demo.
Until then, stop speaking code, start speaking impact, and let’s get better every day.
Frequently Asked Questions:
To prove ROI, you must connect your improvements directly to the Profit and Loss (P&L) statement. Executives are often less interested in the specific Lean tools used (like 5-Whys or Fishbone diagrams) and more interested in financial metrics such as EBITDA, risk mitigation, capacity growth, or cost reduction. Effective reporting involves showing the financial impact first, followed by the operational changes that achieved it. These tools are centralized in Impruver so that you have everything in one place when you need it.
The most effective communication method is “Inductive Reasoning.” Instead of telling a chronological story of how you solved a problem (Deductive), start with the headline or key outcome first (e.g., “We reduced defects by 30%”). If leadership asks for details, break them down into supporting points. Additionally, maintaining a “Cadence of Impact” through one-page executive summaries and before-and-after photos ensures leaders receive a constant stream of positive news rather than waiting for annual reports. Impruver automatically creates and distributes one-page summaries of projects, stories, tools, and key improvements.
Projects are often ignored because of the “Expert Paradox,” where practitioners use complex jargon (like Gemba, Kaizen, or specific statistical tools) that alienates leaders who don’t speak that language. If a project isn’t tied to a specific corporate strategic goal or a major cost driver on the P&L, it is unlikely to be perceived as a priority by leadership.
Lean Management Software, such as Impruver, can automate the distribution of “Success Stories” derived from your projects, goals, tools, and action items. This technology ensures that key leaders receive an automatic, steady stream of updates regarding the value your team is delivering, eliminating the need to manually build new slide decks for every update. It also helps you tag and track projects against specific corporate strategic goals to ensure alignment.
When presenting to the CEO or C-Suite, focus on high-level business health metrics rather than process metrics. Key areas of interest include Risk Mitigation, EBITDA (Earnings Before Interest, Taxes, Depreciation, and Amortization), Capacity, and Growth. Visual evidence, such as before-and-after photos or videos, is also highly effective in making the impact “real” to an executive audience. Impruver can help you organize your improvements, including before and after photos, so that communication with leadership can be automated.
• Creation from Existing Data: The software allows you to generate success stories directly from the work you are already tracking, such as “projects, goals, tools, [and] action items”.
• Automatic Distribution: Once created, these stories are “distributed automatically to key leaders throughout your organization”.
• Constant Visibility: This automation creates an “endless drip of good continuous improvement news,” ensuring that leadership is constantly reminded of the value and impact your team is delivering, rather than waiting for infrequent report-outs.
