Operational Excellence Framework: Building Blocks and Maturity Levels

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

An operational excellence framework links culture, principles, systems, tools and results. See the building blocks, the Shingo model and four maturity levels.

An operational excellence framework is a structure that ties culture, principles, systems, tools and results together, so that improvement becomes part of daily management. This article is for plant managers and operational excellence leads who must build or choose such a framework. It explains the building blocks, the ten principles of the Shingo Model, a four-level maturity scale, a worked example with numbers and the mistakes that turn a framework into a poster on the wall.

Key points

• The Shingo Model builds on five layers: culture at the base, then guiding principles, systems, tools and results.
• Its ten guiding principles fall into three dimensions: cultural enablers, continuous improvement and enterprise alignment.
• Tools answer how, not why. A framework keeps tools tied to principles, so that they do not become the whole programme.
• A four-level maturity scale helps to plan: reactive, defined, managed and integrated. It is a planning aid, not a standard.
• Sustained change takes years. The Shingo Challenge asks for evidence of at least three years of sustained improvement.

What is an operational excellence framework?

IBM describes operational excellence as an approach to business management that emphasizes continuous improvement across all aspects of the business. Lean is one proven methodology for it, and best practices from other plants can feed it. The approach traces back to the Shingo Model, and other methodologies were later built on its principles.

Operational excellence needs structure to last. Without it, improvement stays a set of separate initiatives that fight for the same organizational attention, such as a 5S campaign here and a Six Sigma project there, and long-term success is unlikely. Good operational excellence work answers four questions. Think of them as performance management for the whole system, not for single people. What do we believe? Which systems do we use to work? Which tools support them? How do we know the result is good?

An overview of the Shingo Model makes the point clearly. It is not a standalone programme. It gives an organization a structure to anchor its initiatives and to close gaps on the way to excellence. So operational excellence does not replace lean, Six Sigma or kaizen. It holds them together.

What are the building blocks?

The Shingo Institute presents its approach as layers. The Shingo page names five.

1. Culture. The foundation of an enterprise, where principles are embedded to guide behaviour.
2. Guiding principles. The basis for building a sustainable culture of excellence.
3. Systems. Complex systems divided into layers of subsystems, with outcomes defined in performance and behavioural terms.
4. Tools. Tools address the question "how". Analytics and simple charts are tools too. The "why" comes from the guiding principles.
5. Results. Performance results, usually measured with lagging key performance indicators (KPIs).

Read the list from the bottom up. Culture and principles come first because they decide how people use the systems and tools. Results come last because they are the outcome, not the cause. The aim is to reduce waste, remove inefficiency and optimize the workflow, so that customers are served better. IBM links this approach to a competitive advantage. KPIs show whether customer satisfaction and operational efficiency really improve. The overview warns that focusing too much on one tool is a common mistake. A plant with a perfect kanban board and no principle behind it has a tool, not operational excellence.

For a plant manager, each block turns into a plain question:

• Culture: how do people react when a problem appears?
• Principles: which few rules do leaders use when they decide?
• Systems: how do planning, production and quality work together on a normal day, and where can we streamline the hand-offs?
• Tools: which simple methods does the team use to see and solve problems?
• Results: which measures show whether customers get what they need?

How do the ten principles group into dimensions?

The Shingo page sorts the ten guiding principles into three dimensions.

• Cultural enablers: respect every individual and lead with humility.
• Continuous improvement: assure quality at the source, improve flow and pull, seek perfection, embrace scientific thinking and focus on process.
• Enterprise alignment: create value for the customer, create constancy of purpose and think systemically.

The grouping is useful for design of any operational excellence system. Cultural enablers deal with people. The continuous improvement group deals with how work is done and improved at the line. Enterprise alignment deals with direction: whether the plant, the planners and the sales team pull the same way. A culture of continuous improvement needs all three. A plant with strong line methods but weak alignment improves the wrong things.

Mike Orzen, a lean coach and Shingo Institute faculty member, notes in his essay that flow is the least practiced principle. If you build the structure, check early whether your plant still runs in large batches. That answer tells you where the most work lies.

What do maturity levels look like?

The sources above do not define maturity levels, and there is no standard scale for operational excellence. The following four levels are my own planning aid. Use them to describe where you stand and to choose the next step, not to give a plant a grade.

1. Reactive. Teams fix problems after they happen. Methods differ from shift to shift. Results depend on individuals, and a defect is fixed by whoever finds it.
2. Defined. Standards, basic KPIs and a first set of tools exist. The routine is not yet stable.
3. Managed. A daily routine reviews the measures at the line, and problems are tracked until they are closed. Leaders go to the gemba, the real place of work, and ask questions.
4. Integrated. Teams eliminate waste across areas, and improvement links to the business strategy and to planning. Several areas share the same rhythm, and the structure is used even when leaders change.

Two facts keep expectations realistic. The Shingo Institute offers an anonymous web-based culture survey, called Shingo Insight, which shows how people see the culture. And its Shingo Challenge asks for evidence of at least three years of sustained transformational improvement. Real change takes years, not quarters.

How do you assess where you stand?

Keep the first assessment short and honest. Good change management means that the people who are scored also help to score.

1. Pick five areas. For example: leadership routine, standard work, KPIs, problem solving and the link between planning and the shop floor.
2. Score each area from 1 to 4, using the scale above.
3. Ask the people on the line. A score from the office is often more optimistic than the view from the line. Compare both views.
4. Look at the lowest score. A weak area often holds back the others.
5. Write the next step. One step per area, with an owner and a date.

How do you choose and tailor a framework?

Do not start with a name. Operational excellence is a way of working, not a label. Start with the problem you need to solve, then test the options with these questions.

• Does it fit our culture? An approach that asks for open feedback will not work if people fear to speak.
• Will leaders use it every day? An approach used only in workshops fades.
• Does it help the line? Operators must see how it makes their work easier.
• Does it link to our results? It should connect to delivery, quality and cost.
• Can we sustain it? Keep only the parts you can maintain. A small system that lives beats a large one that does not.

Adapt the approach to your plant, and keep the principles. The tools may change, the principles should not.

Example: scoring a plant

This is an illustration with made-up numbers.

A plant scores its five areas on the four-level scale:

• Leadership routine: 2
• Standard work: 3
• KPIs: 2
• Problem solving: 2
• Link between planning and shop floor: 1

The average is (2 + 3 + 2 + 2 + 1) ÷ 5 = 10 ÷ 5 = 2.0. The plant is between "defined" and "managed".

The lowest score is the link between planning and the shop floor, because plans change during the day and the floor does not see it. The team starts there. It sets one daily planning check at the line and agrees who tells whom when the plan changes. It also adds a weekly review of open problems in the routine.

After a year, the planning link rises to 2 and problem solving to 3.

• New total: 2 + 3 + 2 + 3 + 2 = 12.
• New average: 12 ÷ 5 = 2.4.

The average rose by 0.4 points. That is small, and it is realistic. The numbers are assumptions. What counts is the conversation they trigger about the next step.

Common mistakes

• Choosing a tool first. Tools answer how, not why. Without a principle, the tool is the whole programme.
• Copying a method unchanged. The method must fit the plant, its people and its products, or no one will achieve operational excellence with it.
• A poster instead of a practice. If leaders do not use it daily, it exists only on paper.
• Scoring for show. A maturity score that nobody trusts hides real problems. Use it to plan, not to compare plants.
• Ignoring culture. The Shingo page puts culture at the base for a reason, and operational excellence stands on it. Systems and tools built on a weak base fall over.
• Expecting a quick result. Sustained change takes years. Plan the first twelve months with small, visible steps.

How software can help

Operational excellence needs a clear picture of processes and who is responsible for each step. iFAKT's Polaris BSM provides business swimlane modelling that documents business processes together with the responsibilities of the roles involved. It can make the systems layer visible: who does what, in which order. That supports operational excellence, because roles stay clear. Data-driven decisions need data that people trust. Use such a map to start the conversation with the teams, and check it against what happens at the line.

Next step

Score five areas of your plant on the four-level scale, with the people from the line in the room. Then pick the lowest area and write the first step of your operational excellence framework for it, with an owner and a date.