Your continuous improvement department is killing your continuous improvement. This sounds counterintuitive until you understand the mathematics of organizational capability—then it becomes obvious.
Dedicated improvement teams reduce overall organizational improvement capacity by systematically excluding 95% of employees from improvement work, concentrating knowledge in specialized silos, creating “us vs. them” dynamics, and removing ownership from the people who actually do the work. Distributed improvement capability consistently outperforms specialized departments.
I call this The 95% Rule: when you create a continuous improvement department, you’ve told 95% of your organization that improvement isn’t their job. Congratulations—you’ve just eliminated 95% of your improvement potential with an org chart change that felt like progress.
Why Do Dedicated Improvement Teams Reduce Results?
Dedicated improvement teams reduce results because they remove improvement responsibility from people closest to the work, who have the best insights into waste, inefficiency, and customer impact. Specialization creates artificial separation between improvers and operators, generating resistance to “imposed” changes rather than ownership of solutions.
Here’s what your CI director won’t tell you: their department’s existence depends on improvement remaining specialized. If everyone improved their own work, the department would be unnecessary. The incentives are structurally misaligned with your actual improvement goals.
According to McKinsey research on operational excellence, those doing the day-to-day work know the most about how to improve that work. Your improvement specialists observe from conference rooms. Your frontline employees experience problems daily. Which group do you think has better improvement ideas?
What Is the Engagement Paradox in Improvement?
The Engagement Paradox reveals that specializing improvement reduces engagement, yet engagement is the primary driver of improvement results. Organizations with dedicated CI teams show lower employee engagement in improvement activities than organizations where improvement is everyone’s responsibility.
This isn’t complicated psychology. When improvement is “their job”—the specialized team’s job—everyone else feels permission to ignore it. Why would a frontline worker suggest improvements when a dedicated department exists to handle that? They’ve been told, structurally, that their role is execution, not thinking.
The companies that win at improvement have no improvement department. They have an improvement culture where every employee owns the responsibility to make their work better. No specialists required. No artificial separation between thinkers and doers.
How Should Organizations Structure Improvement Capability?
Organizations should structure improvement capability through distributed ownership with rotating participation, cross-functional project teams, embedded improvement responsibilities in every role, and minimal coordination infrastructure. The goal is making improvement a natural part of work, not a specialized function performed by designated experts.
The optimal structure maintains 25% of employees participating in improvement projects at any time through 5-6 person cross-functional teams. Each person works on one project at a time, rotating through 2-3 projects annually. No permanent improvement department. No career CI specialists. Just organized capability development across the workforce.
According to Harvard Business Review analysis, improvement initiatives work well initially but gains fade quickly without proper sustainability mechanisms. Distributed capability creates sustainability because improvement becomes cultural DNA rather than departmental activity.
What Should You Do With Your Current CI Team?
Transform your current CI team from project executors to capability builders who train others, facilitate initial projects, develop methodology, and measure results—then systematically reduce their direct project involvement as organizational capability grows. The goal is self-obsolescence, not permanent employment.
This transition takes 12-18 months. Phase one: CI specialists facilitate projects while training team leaders. Phase two: trained leaders run projects independently with CI specialist coaching. Phase three: CI specialists focus on methodology refinement and new capability development. Phase four: remaining CI resources address only the most complex, cross-functional challenges while routine improvement happens everywhere, automatically.
If your CI director resists this transition, they’re protecting their empire rather than serving your improvement goals. Act accordingly.
How Do You Build Distributed Improvement Capability?
Build distributed improvement capability by embedding improvement expectations in every job description, tying improvement participation to performance evaluations, providing brief methodology training to all employees, rotating improvement project participation broadly, and celebrating improvement contributions publicly across all organizational levels.
Start with a pilot: select one department, train everyone in basic improvement methodology (4-6 hours), launch cross-functional projects with rotating participation, measure results against departments using traditional CI structures. The performance gap will be obvious within two quarters. Use that data to expand the model.
Stop treating improvement as a specialized function. Start treating it as a universal capability. Your competitors who understand this will bury you. The math is unforgiving.
Frequently Asked Questions
Won’t eliminating specialists reduce improvement quality?
Quality improves with distributed capability because frontline employees understand operational details specialists miss. Specialists bring methodology knowledge; frontline workers bring problem knowledge. Distributed models combine both while specialized departments access only methodology expertise disconnected from operational reality.
How do you maintain consistency without a central team?
Maintain consistency through standardized methodology, clear templates and tools, brief training for all participants, and light coordination infrastructure. Consistency comes from shared frameworks, not centralized control. The methodology itself creates consistency; specialists are unnecessary for enforcement.
What size organization can eliminate dedicated improvement teams?
Organizations of any size can adopt distributed improvement capability. Smaller organizations (under 100 employees) never needed dedicated teams. Larger organizations transition gradually, building distributed capability while reducing specialist headcount over 12-18 months as internal competence grows.
About the Author
Todd Hagopian is the author of The Unfair Advantage: Weaponizing the Hypomanic Toolbox and founder of the Stagnation Intelligence Agency. He has transformed businesses at Berkshire Hathaway, Illinois Tool Works, and Whirlpool Corporation, generating over $2 billion in shareholder value. His methodologies have been published on SSRN and featured in Forbes, Fox Business, The Washington Post, and NPR. Connect with Todd on LinkedIn or Twitter.