Key takeaways
Most mature programs can name all six operational excellence pillars. Far fewer can say who owns each one, and that gap is where programs stall.
- The six pillars: leadership and vision, customer focus, process optimization, performance measurement, employee engagement and empowerment, and innovation and continuous improvement.
- Principles shape how people think. Pillars are the machinery that lets the thinking show up in the work. Both are core.
- Baldrige and Shingo both name the categories. Neither tells you how much is enough, so self-assessments come back middling and nothing moves.
- Measurement usually gets built last. That one sequencing choice is why most mature programs plateau.
Before you fund another rollout, write down who owns each pillar and the number that proves it is working.
A program that has run for years and stopped producing new impact rarely has a methodology problem. What it has is a set of pillars that got adopted as vocabulary and never built into anything load-bearing. Ask five people in that organization what customer focus means and you will get five reasonable answers. Ask who owns it, and the room goes quiet.
Operational excellence pillars are the capabilities that have to be in place before Lean, Six Sigma, or Kaizen can produce anything that holds. Right now the most exposed part of that structure is the manager layer. Gallup's latest global workforce study found manager engagement fell to 22% in 2025 from 27%, a steeper slide than individual contributors saw. Managers are what keeps improvement moving in the weeks between executive reviews. Lose them and sustaining improvement at scale comes down to whoever happens to care.
What are the operational excellence pillars?
The operational excellence pillars are the six capabilities that keep improvement running when nobody senior is pushing: leadership and vision, customer focus, process optimization, performance measurement, employee engagement and empowerment, and innovation and continuous improvement. None of them is an activity you schedule. They are structure, which is why picking a methodology does nothing to put them in place.
Principles and pillars are both core to operational excellence, and they do different jobs. The 10 Principles of Operational Excellence, drawn from the Shingo Model, describe how people think and behave: respect every individual, lead with humility, focus on process. Pillars are where those principles get traction. Take focus on process. As a principle, it is an instruction to a leader. As a pillar, it is a written process with somebody's name on it, a number attached, and a standing meeting where that number gets looked at.
If you need the broader definition first, the guide to what operational excellence means in practice covers it. This article starts one level down.
| Pillar | What it holds up | What breaks without it |
|---|---|---|
| Leadership and vision | Prioritization and resourcing | Every initiative competes for the same attention |
| Customer focus | The definition of value | Teams optimize metrics customers never feel |
| Process optimization | Repeatability | Gains reverse when the improver moves on |
| Performance measurement | Evidence and accountability | Nobody can tell whether anything changed |
| Employee engagement and empowerment | Problem detection at the source | Leaders learn about issues from the quarterly report |
| Innovation and continuous improvement | Adaptation over time | Standards accumulate and the system goes stale |
How do you know a pillar is actually built?
You need two things: a name and a number. Almost no published framework hands you either. The Baldrige Criteria for Performance Excellence sort an enterprise into categories covering leadership, strategy, customers, measurement and analysis, workforce, operations, and results. The Shingo Model arranges ten guiding principles across culture, improvement, and alignment. Both are good descriptions of what a strong organization looks like. Neither tells you how much is enough, so the self-assessment comes back with respectable scores in every box and nothing changes on Monday.
Ownership tends to land where the decision rights already sit. Direction belongs to the executive sponsor, customers to the value stream owner, standards to the function lead, measurement to the program office. Anything that happens daily belongs to the frontline manager. Put a threshold next to each name and the operational excellence pillars become auditable.
| Pillar | Who owns it | Threshold that means it is built |
|---|---|---|
| Leadership and vision | Executive sponsor, usually COO or SVP Ops | A frontline supervisor can recite the priorities without looking |
| Customer focus | Owner of the customer-facing value stream | Complaint codes route to the process owner who can act on them |
| Process optimization | Function or department lead | Every closed improvement leaves an updated standard behind |
| Performance measurement | The OpEx or program office | Implementation rate is reported monthly and holds above 75% |
| Employee engagement and empowerment | Frontline manager | Submitters see the status of their last idea without asking |
| Innovation and continuous improvement | Frontline manager, coached by the OpEx office | Standards are retired on a regular cycle |
The 75% figure is not invented for this article. KaiNexus reports that teams using KaiNexus follow through on over 75% of their improvements. If your program opens far more than it closes, measurement is the pillar you are missing, and every quarter spent treating that as a reporting chore is a quarter it stays missing.
What are the six core operational excellence pillars?
They run in this order: leadership and vision, then customer focus, then process optimization, performance measurement, employee engagement and empowerment, and finally innovation and continuous improvement. Each carries its own load and breaks in its own way.
Pillar 1: Leadership and vision
Leadership and vision is the pillar that decides what gets funded, and the test of it is refusal. Every program has an executive sponsor on paper, and sponsorship costs nothing. The programs that have actually built this pillar can point at work they turned down last quarter and tell you why.
Day to day that looks like a priority list short enough to bite. Three to five items, with a visible line from every funded improvement back to one of them. MIT Sloan Management Review notes that better-aligned businesses tend to outperform poorly aligned peers, all else equal, which is the case for spending scarce executive attention on the list itself instead of on individual projects.
Make it real with a hard cap on active priorities per business unit. Adding a sixth means retiring one of the five. You will know the pillar is built when a frontline supervisor can recite the list without looking it up.
Pillar 2: Customer focus
Customer focus is a routing problem. Enterprises running a mature program are not short of voice-of-customer data. Most of them are drowning in it. What is missing is the path from a complaint code to a process owner who has capacity to do something about it.
Treat customer signal the way you treat an internal audit finding. Same queue, same standing, same expectation that somebody answers for it.
Tagging is the mechanism that makes this work. Every complaint gets attached to the process that produced it, and the three processes generating the most complaints get reviewed monthly with their owner in the room. Do that for two quarters and complaints stop being a service problem. They become an operations backlog.
Pillar 3: Process optimization
Process optimization is what turns an improvement from an anecdote into an asset. Until the better method is written down, taught, and expected of the next person, it lives in one person's head and walks out when they change roles. In most enterprises standard work belongs to quality and gets treated as a compliance artifact, which is exactly why improvements slide off it.
The shift is to treat standard work as the starting line for the next improvement instead of the record of the last audit.
One rule does most of the work here. An improvement cannot be marked complete, or counted in the monthly numbers, until the standard it touched has been updated.
Pillar 4: Performance measurement
Performance measurement has to watch the improvement system itself, not only what the system produced. A program can post respectable numbers for a full year on momentum from work that finished two years ago, while current participation quietly falls apart.
Across the KaiNexus customer base, 28% of improvements carry direct financial impact, the average improvement is worth roughly $15,000, and about 1 in 100 exceeds $100,000, as set out in How to Measure the Impact of Your Continuous Improvement Program. Read that spread carefully. The large wins are never commissioned. They surface out of volume, which means a program counting only the big projects quietly starves the pipeline that produces them, then describes the starvation as focus.
So put participation rate and time-to-close on the same page as savings, and treat a slide in either one as a miss worth saying out loud.
Pillar 5: Employee engagement and empowerment
Employee engagement and empowerment comes down to what visibly happens after somebody speaks up. Frontline teams see failures before any report does. Whether they bother telling you a second time depends almost entirely on what happened to the first thing they raised. Recognition programs lift submission volume for a while. Visible closure keeps it up.
A structured channel is what makes this work, and an open door is not a channel. Neither is a suggestion box, and neither is an email to a supervisor. A channel means every idea is visible, has somebody assigned, gets tracked, and closes with a stated reason.
Post the disposition of every idea where the people who submitted them actually work. Include the declines, with the reason attached. A decline with a reason costs you far less submission volume than silence does.
Pillar 6: Innovation and continuous improvement
Innovation and continuous improvement is the one pillar whose job includes taking things away. Most programs are additive by reflex: new standards, new metrics, new items on the huddle agenda, none of it ever retired. That is how a system which worked beautifully at launch turns into something people route around.
Keep the cycle low-ceremony. Obstacles escalate, anything that recurs three times gets structured problem-solving, and nothing stays on the board purely because it has always been there.
In practice that is a 10-minute huddle at shift change covering yesterday's exceptions, plus one quarterly sitting where the only question on the table is what to retire.
Which operational excellence pillars are usually weakest?
Measurement and engagement, almost always, and usually together, since the second depends on the first. The signatures below show up well before the results do.
- Improvement activity you cannot count. If nobody can tell you how many improvements are in flight this month, the measurement pillar is absent, no matter how healthy the outcome metrics look. Outcome metrics lag by quarters, and by the time they move you have lost two of them.
- Gains that reverse within two quarters. When a result erodes and nobody notices, look at process optimization before you blame the project that produced the gain. The improvement was genuine. Nothing was holding it in place.
- Ideas that arrive only from managers. If every submission comes from supervisor level and up, the engagement pillar is broken, and you are missing exactly the observations that cost the least to act on.
- Six competing priorities at the same level. Past about five, leadership and vision has failed. Somebody published a wish list and put the word strategy on the cover.
- Efficiency gains no customer can feel. Real internal savings alongside flat satisfaction and flat retention usually means customer focus is missing and teams have spent a year optimizing work nobody valued in the first place.
How do you build the pillars into daily operations?
Build measurement second, not last. The usual order runs leadership, engagement, process, and then measurement, and leaving it until the end is the surest way to plateau. Without it there is no evidence the other operational excellence pillars are doing anything, so they become the first thing cut when budget gets tight.
The rest is short. Publish three to five priorities and cap them hard. Set up counting before you set up campaigns, so every improvement has an owner, a date, and a status anyone can look up. Add the closure rule. Engagement starts moving on its own once people can see things closing. For the fuller sequence, see Top Strategies to Achieve Operational Excellence.
You do not need software to start any of this. A whiteboard and genuine discipline will hold all six pillars up inside a single department, and plenty of strong programs began exactly there, which is why the build-versus-buy argument usually arrives too early. The problem shows up at scale. Once the work spans several sites, wiring daily huddles and tiered management to strategy deployment across the enterprise by hand eats more management time than the improvements give back, and the manual reporting layer turns into the thing everyone quietly stops doing.
Frequently asked questions
The confusion that costs the most is between pillars and principles, and getting it wrong is the difference between building structure and writing a values statement. The second most common one is assuming the pillars compete with Lean, Six Sigma, and Kaizen, when they are what those methods stand on.
What are the pillars of operational excellence?
Leadership and vision, customer focus, process optimization, performance measurement, employee engagement and empowerment, and innovation and continuous improvement. Each one is a capability somebody owns and a threshold somebody checks, which is a different thing from a workstream with a budget attached. You know a pillar is built when there is a name on it and an observable test that says whether it is holding.
What is the difference between operational excellence pillars and principles?
Principles cover how people think and behave, things like respecting every individual or focusing on process, and they matter to operational excellence every bit as much as the pillars do. Pillars are where a principle gets somewhere to live: a written process, an owner, a metric, a standing review. A principle with no pillar underneath it stays a poster on the wall. A pillar with no principle behind it turns into bureaucracy fairly quickly.
How many pillars of operational excellence are there?
There is no authoritative count, and the number matters less than the coverage. Published frameworks carve the same ground up differently depending on how finely they want to split leadership, strategy, and culture. Six works here because each one carries a load the others do not, and each breaks in a way you can spot.
Do the operational excellence pillars replace Lean or Six Sigma?
No, and the question has it backwards. Lean, Six Sigma, Kaizen, and the Shingo Model are core to operational excellence, and the pillars are the ground those methods stand on. Every one of them assumes documented process, working measurement, and an engaged frontline are already there, and none of them will build those for you. With all six pillars in place you can run any of these methods well. With two of them missing, whichever one you pick will disappoint you.
How long does it take to build a missing pillar?
The mechanical pillars move faster than the behavioral ones. Measurement and process optimization come down to deciding what to count and writing one closure rule, so progress shows up early. Leadership and vision and employee engagement and empowerment take longer, because people have to watch the new rules survive a few cycles first. That usually includes at least one moment where something popular got declined, or a declined idea came back with an honest reason attached.
Build the pillars before you fund another rollout
An organization that wants all six operational excellence pillars to hold needs three fairly unglamorous things it probably does not have: every improvement in one place, a status anyone can check without having to ask, and measurement that covers participation and implementation rate instead of savings alone. Those are infrastructure problems rather than culture problems, which is good news. Infrastructure survives a change of leadership. Enthusiasm does not.
KaiNexus was built to be that infrastructure, giving an organization one system where improvement work gets captured, tracked, measured, and tied back to strategy across every site. If the strategy and the commitment are already there and the structure underneath them is not, see how it works in a short demo.
.svg)
Add a Comment