Operational Excellence Doesn't Have a Finish Line — Here's What That Means for Your Plant
Most operational excellence initiatives fail. Not because of the wrong methodology, wrong tools, or wrong team. They fail because of the wrong framing.
I recently spoke with Rajeev Seth, Director of Operational Excellence & Asset Reliability at Mondelez International, on the Shop Floor, Top Floor Talk Show. What he said has stuck with me: “Operational excellence is the way you are going to work daily, weekly, and monthly.”
That’s a deceptively simple idea, but the gap between knowing it and actually living it is where most manufacturers get stuck. Here’s what goes wrong, and what it takes to get it right.
The Project Trap
When you frame operational excellence as a project, you unintentionally signal to your entire organization that it’s temporary. Projects have start dates and end dates. They have budgets, deliverables, and a finish line.
Here’s what each level of your org hears when you treat OE like a project:
- Frontline operators: “This too shall pass. Keep your head down.”
- Middle managers: “This is extra work on top of my real job.”
- Senior leaders: “We’ll get a report at the end and move on.”
None of those interpretations create lasting change. All of them guarantee reversion.
Three Consequences of Getting This Wrong
1. The Reactive Loop Never Breaks
The most visible symptom of a failed OE initiative is persistent firefighting. You fix an issue, it holds for three weeks, then it’s back. Teams stay stuck addressing symptoms instead of root causes, because the “project” never built the daily habits required for prevention.
Rajeev put it plainly: manufacturers spend their most valuable time reacting to problems instead of preventing them. The technology to break that cycle exists: AI, machine learning, predictive maintenance. But technology deployed inside a project mindset just becomes another tool that gets abandoned when the project closes.
2. Silos Survive and Quietly Sabotage Progress
Projects are typically owned by a single function, a dedicated OE team or an outside consulting group. This creates an immediate structural problem: the people doing the “excellence work” are separated from the people doing the actual work.
“Don’t act like an external consultant. Act like a partner with them and solve their problems.”
When improvement lives in a silo, the people closest to the problems don’t own the solutions. Quality blames production. Production blames maintenance. Everyone blames the OE team for “not fixing things.”
3. Trust Erodes and Momentum Dies
This one is the hardest to measure, and the most damaging. Every failed initiative teaches your workforce a lesson, just not the one you intended. They learn that leadership’s commitment is temporary and learn to wait it out.
“You cannot generate momentum by pushing. You can generate momentum by pulling – when people are pulling operational excellence.”
That pull only happens when people trust that the changes will stick and their effort will be honored. Every project that fades into irrelevance makes the next one harder to sell. You’re not starting from zero, you’re starting from a deficit.
The Shift: From Project to Operating System
If operational excellence isn’t a project, what is it? It’s your operating system, the daily, weekly, and monthly rhythms that define how work gets done, how problems get solved, and how people engage with their roles.
Three practical shifts to get there:
Start with Purpose, Not Dashboards
Rajeev doesn’t start his day by checking metrics. He starts with purpose, asking how his team can work smarter, simplify their ways of working, and build the right culture. Metrics matter, but they serve the purpose rather than define it.
Try replacing “How did we perform yesterday?” with “What did we learn yesterday, and what are we doing differently today?” One is backward-looking. The other drives action.
Move Authority to Where the Information Lives
The project model positions improvement experts as coaches who parachute in and leave. Rajeev argues for something different, Leadership Gemba: leaders physically present on the shop floor, coaching in real time, removing barriers, building capability through doing.
As he puts it: “You need to move authority to the information, which is at the bottom of the pyramid.” Frontline operators need both the capability and the empowerment to make decisions – and that requires leaders who are present, not distant.
Build Pull, Not Push
The project model is inherently push-based. Corporate decides on an initiative and pushes it down. This creates compliance, not commitment.
The alternative: start small, work alongside a team as a partner, solve a real problem that matters to them. When neighboring teams see the results and ask, “How did you do that?” – that’s pull. That’s sustainable momentum.
Are You in Project Mode? A Quick Diagnostic
Be honest with yourself:
| Signal | Project Mode | Operating System Mode |
| Who owns improvement? | A dedicated team or external consultants | Every function, every level |
| When does improvement happen? | During designated project phases | Daily, as part of standard work |
| What happens when it “ends”? | Teams revert to old habits | There is no end – it’s how you work |
| How are KPIs used? | Lagging indicators in monthly reports | Leading & lagging indicators drive daily action |
| Where do leaders spend time? | In conference rooms reviewing dashboards | On the floor, coaching and removing barriers |
The Bottom Line
The gap between a failed OE initiative and a lasting culture of excellence isn’t knowledge, budget, or technology.
You can launch another project, hire another consultant, and print another set of banners. Or you can make a different choice: stop treating operational excellence as something you do in addition to your work, and start treating it as the way you do your work.
Show up on the floor. Build trust. Develop capability. Let your teams pull improvement toward themselves.
As Rajeev put it best: “My day starts with a purpose every morning.”
What purpose will yours start with tomorrow?
Hear the full conversation with Rajeev Seth – including his take on AI-powered predictive maintenance, Leadership Gemba, and how to build a Daily Management System that actually sticks.
