Watch the recording of the webinar:
Listen to the recording via our podcast (the webinar and then the Q&A):
Most CEOs say continuous improvement matters. Far fewer can describe how it actually shows up in their decisions about strategy, capital, talent, and where the business is headed. In this Ask the CEO session, Bill Canady walks through how he runs companies -- and the answer is more direct than most CI leaders are used to hearing from the executive level.
Bill has led companies to profitable growth for more than 30 years. He scaled OTC Industrial Technologies past $1B in revenue with a 78% increase in earnings. He's the author of The 80/20 CEO and From Panic to Profit, and the creator of the Profitable Growth Operating System. The session is unscripted and the Q&A pulls from a global audience.
What follows is a synthesis of the substance, organized for someone who wants to understand how the executive level actually thinks about improvement work.
Bill's framing is consistent across the conversation. 80/20 isn't a tactic -- it's how he organizes a business. Look at the data, find where the company is making money and where it isn't, then do more of what makes money and less of what doesn't.
That sounds obvious. The reason it isn't is that most companies have so many priorities, products, customers, and initiatives that nobody can tell you which 20% are actually generating the returns. The data exists. It just isn't being asked the right questions.
For Bill, 80/20 isn't strongest in any single function -- it's strongest as a common language across the company. Speaking the same language with the same goal, scaled down to fewer priorities, is what lets a team actually move things instead of moving everything an inch.
This is the part most CI professionals need to internalize. 80/20 thinking and the disciplines underneath it are the framing leaders use to decide whether your improvement project is worth resourcing.
A theme Bill returns to throughout the session: the math of cascaded priorities is brutal.
If a CEO has 10 strategic goals, each goal action-plans into roughly 100 targets, and each target translates into about 10 action plans. That's 10,000 action items. The same names show up across all 10,000 because no organization actually has 10,000 people who can independently own work. The result is everyone overcommitted, nothing fully resourced, and execution that feels exhausting without producing wins.
Bill's approach is the opposite of cascading. Pick the few things that actually matter, fully staff the first one, see what's left over, then go to the second. He acknowledges this offends people. Cancelling someone's pet project feels personal -- they equate the project with their job and their worth. The way through is making the decision collectively, around a shared definition of what good looks like, with the strategy owned by the team rather than dictated from above.
This connects directly to what most healthcare and manufacturing CI leaders see: somebody at every level has called something a top priority, and now there are 300 top priorities competing for the same attention.
Bill is direct about why lean matters in his world: it's the best tool he knows for taking underutilized resources -- people, capital, factories -- and shifting them to where the highest-return opportunities live.
His mental model goes like this. The data tells you where you're making money. Force-rank customers and resources into quads. The top quad gets the people, the capital, and the floor space. Pulling resources from underperforming areas to feed the top quad creates chaos because factories have to be relaid out, work has to flow differently, and the system has to be rebuilt around the new priority. Lean is what lets you do that without breaking the operation.
He frames it specifically as a waste-reduction tool, not a variability-reduction tool. If variability is the problem, that's Six Sigma. For redeployment and layout work, lean is the game.
The order-to-cash framing matters here too. Bill watches the cash conversion cycle -- how long it takes to turn a dollar of investment into a dollar of returned cash. The instinct is to attack production time on the shop floor (concrete land), but the real opportunity is often in the office (carpet land). A drawing might take a day to produce, but spend four or five weeks waiting in queue. Engineering, sourcing, and approval cycles are usually a target-rich environment for improvement, and most companies underinvest there because production is more visible.
Bill describes the CEO role with three priorities that sit on top of everything else.
First, decide where the company is going. In private equity, that's typically a 3x return on invested capital over a defined window. The number is the goal that gives everyone clarity about how big the prize is.
Second, measure and monitor. Watch the metrics, hear the team report out, run the discipline of asking what went wrong and what's being done about it.
Third -- and Bill calls this the hardest -- make the operating system a condition of employment. Lean, the talent process, M&A, 80/20 -- these are how the company runs. They're not optional, and people who won't use them eventually don't stay. He's emphatic that this isn't about being a robot. It's about not letting the operating system be undermined by individual reluctance, especially in a private-equity context where the timeline is roughly a thousand days.
He also describes a "rule of three" for execution. You need a strong visionary who sets direction. You need operators -- presidents, directors, managers, VPs -- who actually do the work. And you need what he jokingly calls "prophets" (with a ph): outside experts who've been there before and can help the organization adopt proven processes faster than reinventing them. Skip any of the three and execution slows.
A long thread in the session is about what happens when an acquired company has culture and leadership problems, and how Bill decides whether to coach a leader up or move them out.
His four-step approach in a new company:
Step one is setting the goal with the CFO and the board -- the financial definition of what good looks like. Step two is building the strategy with the team, with the team owning it (not him). Ownership matters because if it's his strategy, the team treats it as something to be tolerated rather than executed. Step three is organizing the company around the strategy. This is where leaders show themselves as either bought-in or blocking. Up until step three it's all conversation. In step three, projects get cancelled, resources get moved, and people start to either lean in or resist.
He's explicit about what happens next. Somewhere around 90-120 days in, leaders who can't or won't move start leaving the role -- often leaving the company. He's not casual about this, but he's not soft about it either. If he doesn't act, the company never aligns.
The signal CI professionals should hear: the people running the businesses you support face this calculus constantly. When they're cool to your improvement program, they're often making a parallel judgment about whether the program will help them execute the strategy they've committed to with the board.
This is the section worth bookmarking. Bill answered the question "what do you wish more CI professionals understood about the CEO's perspective" directly.
The CEO is already on your side. They want the company to run efficiently and productively. They want their people to have meaningful opportunities. They want strong returns for investors. Continuous improvement is a huge part of how that happens, and they know it.
What they're looking for from you, Bill says, is succinct: here's the opportunity, here's what I'd do about it, here's the impact. They're also dealing with a wider portfolio of problems than you can see from your seat -- another business unit might be on fire, capital might already be committed elsewhere, or your project might be #4 on a priority list that has hard limits. Understanding the hand they're playing is part of your job. Helping them know which card to play next is how a CI leader becomes invaluable.
If you can walk in and say "this saves $100M on a $200M budget," you become the most interesting person in the room. The number doesn't have to be that big. The framing does.
A related question came in about how CI professionals can move into broader operations or P&L roles. Bill's response was practical.
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. That knowledge is the perfect foundation for an operations role. The question is whether the individual wants to be a subject matter expert or move into a broader leadership role -- and CI is one of the few functions where you regularly stand in front of CEOs, segment leaders, and business unit heads. Use the visibility.
Moving into sales is harder because the organization tends to see CI people as operational. If sales is the goal, his suggestion is unconventional but consistent: get into a function outside of operations and start applying CI thinking there. Sales could use more CI than almost any other function -- the sales cycle, CRM data flow, opportunity intake from customers back into engineering. Become the expert in that space, and the next role finds you.
Bill names four principles he uses to keep teams aligned and energized.
Be data-driven. Less than 20% of the data and you're guessing. More than 80% and you took too long. The middle is where decisions get made.
No surprises. Fish, relatives, and bad news all stink after three days. Keep leadership in the loop early, especially when things are going sideways.
Results matter. He's specific that this isn't a "best efforts" company. Hall of Fame batting in baseball is .300. In business, .700-.800 is the bar. You have to win more than you lose because the company is being measured on outcomes.
Progress, not perfection. Don't make the same mistake twice, but don't paralyze the team waiting for a perfect plan. The Honda Civic story is the metaphor: the early model wasn't impressive, but the discipline of incremental improvement over decades produced the Toyota Tacoma.
A practical question came in about whether organizations should run big kaizen events or focus on daily continuous improvement. Bill's answer: both, but the daily side is where the culture lives.
Daily management is the lever. A team standing up in front of a board every day, talking through safety, quality, delivery, cost, and whatever else surfaced -- that's the cue for surfacing problems early and solving them with permanent solutions rather than workarounds. Mature teams progress from "we don't crush people" to "let's track near misses." Same trajectory in CI: from big visible events to a steady stream of small improvements suggested by the people on the line.
The shift happens when leaders make it safe for people to raise their hands. That requires the right culture, and it requires leaders who actually listen and move on what they hear. Without that, daily management becomes a status meeting and improvements stop coming.
A question came in about AI's role in lean. Bill's framing: AI is the next computer. In and of itself it's meaningless. Embedded into how the work gets done, it changes what's possible.
He gives examples from different functions. AI defeats the white page when writing marketing copy or first drafts. It bridges the engineer-to-marketer translation problem by giving both sides a tool that can be trained on the product and queried from either direction. A massive Excel sheet that used to take hours to analyze can be uploaded to a chatbot and queried in seconds. On the production side, vision systems trained on specifications can inspect parts faster and more reliably than human inspection.
His honest answer on jobs: AI will force upskilling the same way computers did. Some jobs change, some expand, some disappear, new ones emerge. The people who adapt come out further ahead. The companies that don't adapt fall behind.
A question came in about whether lean principles could drive transformation across healthcare, particularly around inefficiencies, costs, and disparities. Bill has board experience in healthcare (he was on the AHA board and involved with University Hospitals in Cleveland) and his answer was specific.
The healthcare ratio he cites: a clinician spends 5-10 minutes with a patient and then up to 80-90% of the day documenting that visit. Imagine the lean opportunity in a system that skewed toward measuring and monitoring. AI plus CI thinking has enormous potential, but healthcare moves cautiously because the cost of getting something wrong is a patient's life. Hospitals are begging for help. The challenge is finding people who understand HIPAA, human emotion, exhausted physicians, and the specific operational realities of clinical work -- not just lean theory.
The connection to a recent personal experience Mark mentioned: an AI tool drafting visit notes from a recorded patient visit, freeing the clinician to see additional patients per day. That's not technology replacing clinicians. It's technology removing the documentation burden from work that clinicians went to school to do.
Bill didn't pitch the platform during the session, but the connection is direct enough to name.
A 1,000-day private equity timeline puts brutal pressure on visibility. A multi-site company with multiple business units cannot run on spreadsheets and email threads. KaiNexus exists because tracking improvement work, measuring impact, and spreading successful improvements across an enterprise is operational infrastructure, not a nice-to-have.
The platform handles the things Bill's operating model assumes are happening: improvements being captured at scale, status visible to leadership at every level, impact tracked in financial and non-financial terms, daily management routines supported with real data. If your CEO is operating with the kind of focus and pace Bill describes, the question is whether your CI infrastructure can keep up.
Bill Canady is the CEO of Arrowhead Engineered Products and the Chairman of OTC Industrial Technologies. He has led companies to profitable growth for more than 30 years. Under his leadership, OTC scaled past $1B in annual revenue with a 78% increase in earnings. He is the author of The 80/20 CEO and From Panic to Profit, and the creator of the Profitable Growth Operating System. Bill is a Navy veteran, a summa cum laude graduate of Elmhurst University, and earned his MBA from the University of Chicago Booth School of Business.
What is 80/20 leadership?
80/20 leadership applies the Pareto principle to how a CEO organizes a business. Look at the data to find where the company is actually making money and where it isn't. Force-rank customers, products, and opportunities. Concentrate people, capital, and attention on the top quad and pull resources out of the underperforming bottom quad. The goal isn't a tactical efficiency improvement -- it's a common language across the company that lets everyone make decisions against the same set of priorities.
How does 80/20 leadership relate to continuous improvement?
80/20 thinking is the brain that decides what's worth improving. Once you know where the highest-return opportunities are, lean and CI are the tools that let you actually redeploy resources, redesign work, and execute. Trying to apply lean across an entire company without first deciding which 20% deserves the focus tends to produce activity without results.
Why do most strategies fail at execution?
Cascaded priorities multiply faster than people realize. A CEO with 10 strategic goals typically generates roughly 10,000 action items by the time the strategy reaches the front line. The same names show up across all 10,000, which means no priority is fully resourced. The discipline is fully staffing the most important priority first, then moving to the second only when the first is covered.
What's the difference between CI work in concrete land and carpet land?
Concrete land is the production floor -- machines, lines, fittings, physical product. Carpet land is the office side -- engineering, sourcing, approvals, design, sales support. Most CI work historically focused on concrete land because waste is more visible there. The bigger opportunity in many companies is in carpet land, where wait times in queues, approval cycles, and information handoffs often dwarf the actual production time.
What do CEOs actually want from CI professionals?
Three things, succinctly: here's the opportunity, here's what I'd do about it, here's the impact. CEOs are already on your side -- they want the company to run efficiently. What they need from you is help understanding the trade-offs they're making across the business so they know which improvement to prioritize when capital, attention, and people are all constrained.
How does Bill Canady approach leadership change in an acquired company?
Four steps. Set the financial goal with the CFO and board. Build the strategy with the team and let the team own it. Organize the company around the strategy -- this is where bought-in leaders and blockers separate. Around 90-120 days in, leaders who can't or won't execute the strategy typically leave the role. The discipline isn't about being harsh; it's about not letting the operating system be undermined by individual reluctance.
Should organizations run big kaizen events or focus on daily improvement?
Both, but daily improvement is where the culture lives. Big rapid improvement events have their place, but the engine of sustained improvement is daily management routines -- short standups in front of a board where teams discuss safety, quality, delivery, cost, and surface problems early enough to solve them with permanent solutions rather than workarounds.
How is AI changing continuous improvement work?
AI is the next computer. It removes friction from drafting, analyzing data, bridging communication between technical and non-technical functions, and inspecting work in production. It will force upskilling the way computers did. The people and companies that adapt come out further ahead; the ones that don't fall behind. The technology by itself doesn't matter -- embedding it into how the work gets done is what changes outcomes.
.svg)
Copyright © 2026
Privacy Policy