The strategy presentation was impressive. New markets, digital business models, AI-supported processes. On the board slide, “Operational Excellence” appears as one of six strategic fields of action. That sounds ambitious.
In day-to-day operations, it looks different. Delivery dates are missed regularly, but no one analyzes the causes. Quality fluctuates, but complaints are handled individually instead of being understood systematically. Processes are fragile: they work as long as everything goes to plan, and collapse as soon as something unexpected happens. Meetings go in circles because last week’s problems were not solved.
Operational excellence is not sexy. It is not applauded at any conference and appears in no trend report. But it is the difference between organizations that function and those that merely formulate strategies.
A CEO I advised invested considerable energy in a transformation initiative while his operational foundation was crumbling. Client complaints increased, internal escalations piled up, and middle management spent its time firefighting instead of leading. When I asked him when he had last devoted an entire day to day-to-day operations—not strategy, not transformation, but operational processes—he had to think for a long time. The answer: months.
This is not an isolated case. In many organizations, day-to-day operations are seen as something that “runs” or “should run.” Leadership attention flows into projects, initiatives, and change. Operations are delegated and then forgotten—until they stop working. Three levers help strengthen the foundation.
W. Edwards Deming, the father of modern quality management, coined a sentence that should make every manager uncomfortable: “Every system is perfectly designed to get the results it gets.” In other words: every system delivers exactly the results it was built to deliver. If your delivery dates are regularly not met, that is not bad luck. It is the result of your system. If your quality fluctuates, it is not down to individual employees. It is down to processes that allow variation.
Most organizations treat operational problems as isolated incidents. A delivery date was missed, so the responsible employee is reprimanded. A complaint comes in, so the individual issue is resolved. What is missing is the systematic question: Why does this keep happening? The answer is almost never individual people. It lies in processes that are not robust enough, in interfaces that are not defined, in responsibilities that are unclear, and in KPIs that measure the wrong things.
| Treating symptoms | Root-cause work |
|---|---|
| Reprimand an individual employee | Analyze the process that makes the error possible |
| Resolve the complaint | Identify patterns in complaints |
| Decide on an escalation | Ask why the escalation was necessary |
| Introduce more controls | Design the process so controls become unnecessary |
A division head I supported in stabilizing her division started with a simple measure: for four weeks, she had every escalation documented—not who escalated, but why. The pattern was clear: 70% of escalations had the same cause—an unclear interface between two teams. She did not solve the escalations. She solved the interface. After that, escalations fell by half.
Operational excellence does not come from peak performance in isolated cases. It comes from reliable quality in normal operations. The difference between an excellent and a mediocre organization is not what it delivers on its best days, but what it can still deliver reliably on its worst days.
That requires standards—and the word sounds boring because it is. Clear process descriptions for critical workflows, not for everything, but for the things that must not go wrong. Defined quality criteria that are non-negotiable. Regular checks to ensure standards are being followed. And the willingness to act immediately when deviations occur, not only when the client complains.
The most common mistake: setting standards and then not enforcing them. The first deviation is tolerated because there was a good reason. The second is overlooked. The third becomes normal. Six months later, the standard exists only on paper. This is not an employee problem. It is a leadership problem. Standards that are not enforced are more harmful than no standards, because they send the message: rules apply only in theory.
This pattern is reinforced by a reward system that celebrates the wrong people. Whoever puts out a fire is seen as a hero and promoted. Whoever prevents the fire from breaking out in the first place through excellent processes remains invisible. As long as you reward the firefighters and ignore the fire-prevention architects, your day-to-day operations will always be on fire. And once you have sent that signal, it will be difficult to rein in the lived culture again.
The third lever is the most uncomfortable, because it affects your calendar. Operational excellence requires leadership attention—not as a one-off initiative, but permanently.
Take a look at your calendar from the last two weeks. How much time did you spend on operational topics—not strategy meetings, not projects, not stakeholder management, but understanding and improving the processes that keep your business running? If the answer is “little to none,” you are sending a signal: day-to-day operations are not important enough for my attention.
Operational leadership means conducting regular operational reviews—not to control, but to understand. Discuss problems in depth, not just tick off status dashboards. And above all: talk to the people who do the work, not only to those who report on it. In Lean management, this principle is called a “Gemba Walk”—going to where the work happens. Do not conduct operational reviews in the conference room. Go to where value creation happens: on the shop floor, at the phone in customer service, in the development environment. Reports can be polished. Reality cannot. Set priorities honestly, because sometimes a manager’s most important contribution is not the next initiative, but the decision to fix a fragile interface before it puts the business at risk.
This does not mean you stop thinking strategically. It means finding the balance between change and stability, between transformation and day-to-day operations. Organizations that are successful in the long term can do both: innovate and deliver at the same time. One without the other is either stagnation or chaos.
First: Name the three operational problems that occur most frequently in your division. Are they solved as isolated incidents each time, or have you systematically analyzed the root cause? If it is the former, start a pattern analysis this week.
Second: Are there defined standards for the critical workflows in your division? And are they actually being followed? Do not ask your team leads—ask the employees who do the work.
Third: What percentage of your time last week did you devote to operational day-to-day business—not projects, not strategy, but processes? If it is under 20%, block two hours this week for an operational review.
No one is recognized for operational reliability. No conference invites you because your processes work. No headhunter calls because your on-time delivery rate is 99%. Operational excellence is invisible when it works—and painfully visible when it is missing.
Larry Bossidy, former CEO of Honeywell, put it in a formula: execution is the strategy. An average strategy with excellent execution will always beat a brilliant strategy with mediocre execution. Operational discipline is not a side issue. It is the main issue.
Measure what matters – Why the wrong KPIs conceal operational problems instead of revealing them.
Twenty priorities are none – When day-to-day operations are buried under twenty parallel initiatives, operational quality is the first to suffer.
All Insights can be found in the overview.
Proven tools and models for self-application are available under Solutions.
If you want to take these thoughts further for your company, a no-obligation initial conversation is worthwhile.
