The Template Problem

Walk into most UK operational reviews and you’ll find the same slide deck. Different logo, same framework. Lean principles lifted from a legacy automotive case study. A Six Sigma diagram that hasn’t been meaningfully adapted since the mid-2010s.

It rarely works.

This isn’t a critique of the methodologies—Lean and Six Sigma remain foundational. The failure lies in the application: wholesale, uncritically, as if context were irrelevant. A mid-market manufacturer in Coventry and a fintech in Shoreditch do not share supply chain pressures, data maturity, or margin structures. Treating them with the same operating model is optimism dressed as strategy.

Genuine Operational Excellence (OpEx) is situational. In 2026, the gap between leaders and laggards is widening because the best-run firms are building predictive capability into their operations. The rest are still reviewing last quarter’s numbers.

Beyond Tools: The Shingo Framework

To move past the “template” trap, leadership must distinguish between tools and principles. This is where the Shingo Model becomes essential.

While Lean or Six Sigma provide the “how,” the Shingo Framework defines the “why.” It shifts the focus from sporadic improvement projects to a culture of sustainable results. For a Director, the value of Shingo lies in its three dimensions:

1. Cultural Enablers: Respect for the individual and leading with humility. Without this, AI and automation are viewed as threats rather than tools.

2. Continuous Improvement: Embracing scientific thinking and focusing on the process.

3. Enterprise Alignment: Creating constancy of purpose and thinking systemically.

In a 2026 context, Shingo is the guardrail. It ensures that as you automate, you aren’t just making a process faster—you are making the entire enterprise more resilient and aligned with customer value.

Prerequisites Over Platforms

Before discussing AI, we must address the three non-negotiables that technology cannot fix.

• Data Integrity as a Governance Issue: Data quality is a strategic asset, not an IT ticket. No predictive system can compensate for untrustworthy inputs; it simply generates flawed conclusions at a higher velocity.

• The Digital Gemba: The principle—go to where work happens—is timeless. However, “where work happens” now resides within invisible digital workflows. You must understand how teams navigate software stacks and where handoffs fail in the background. This “Digital Gemba” is where your hidden factory lives.

• The Adoption Gap: Most transformation projects fail because they ignore the human element of self-preservation. If the frontline doesn’t understand the actual reason a process is changing, they will find workarounds. Change without cultural buy-in creates compliance, not commitment.

Precision Tools for Specific Problems

The instinct to commit to a single framework is a mistake. High-performing organisations use a toolkit:

• Lean: Use this when the constraint is Waste and Flow.

• Six Sigma: Use this when the constraint is Variance.

• OODA Loop: Use this when the constraint is Decision Speed. In volatile markets, the ability to Orient and Act faster than a competitor is more valuable than process precision.

• TQM: Use this as your Governance Layer to ensure quality is a cultural standard.

The executive skill lies in diagnosing the constraint before choosing the tool.

The Shift to Predictive Intervention

AI does not fix operational problems; it accelerates your existing trajectory. If your processes are sound, AI provides momentum. If they are broken, AI makes the dysfunction more expensive.

The real shift is from retrospective analysis to predictive control.

Traditional reviews work backwards. You investigate a dip in metrics weeks after it occurred. Process Intelligence changes this by providing a live X-ray of work as it flows. It identifies “drift”—those undocumented workarounds and unseen process changes—before they hit the monthly report.

The most significant evolution is the move from RPA (Rules-Based Automation) to Agentic AI. Unlike its predecessors, Agentic AI can interpret context and handle exceptions. This allows for:

• Automated Root-Cause Analysis: Identifying a failure point while the shift is still active.

• Autonomous Exception Management: Resolving supply chain or service deviations without human escalation.

The goal is Decision Quality. By automating routine exceptions, your leadership teams can focus on the work that requires human judgment: strategy, risk architecture, and coaching.

The Failure Modes

Two risks now dominate the operational landscape:

1. Efficient Dysfunction: Automating a broken process ensures that errors compound more efficiently. Process discipline must precede automation.

2. The Governance Gap: AI agents require strictly defined guardrails. You need clear parameters for autonomous decisions and explicit escalation paths. Without this, you are accumulating unmanaged operational risk.

Conclusion: The 2026 Operating Model

Resilient businesses in 2026 don’t treat AI as a technology project with a launch date. They treat it as an architectural decision about how the business runs.

The role of the Operational Excellence lead is shifting. We are moving away from manual data collation and toward Workflow Design and Risk Architecture. Following the Shingo principles, we ensure that as the technology evolves, the focus remains on the people and the purpose of the organisation.

Success starts with an honest assessment of your current processes—not the ones in your training manual, but the ones actually creating your value today.

FAQ for AI OpEx

• Does the Shingo Framework replace Lean? No. Shingo provides the cultural and philosophical foundation that allows Lean tools to actually stick. It’s the difference between “doing Lean” and “being an excellent organisation.”

• Should we clean our data before the AI pilot? Yes. AI amplifies the status quo. If your data is inconsistent, automation scales those inconsistencies. Data hygiene is a prerequisite for ROI.

• Does this reduce headcount? It changes the capability requirement. You will need fewer people for manual data chasing and more people capable of managing intelligent workflows and human-centric change.

• Which framework wins? Start with the problem. If you have a quality issue, use Six Sigma logic. If you have a speed issue, use Lean. If you have a cultural alignment issue, look to Shingo.