Business Performance: The Complete Practitioner's Guide to Operational Excellence That Reaches the P&L
By Allan Ung | Founder & Principal Consultant, Operational Excellence Consulting (OEC)
Published: 28 September 2026
Allan Ung is the Founder and Principal Consultant of Operational Excellence Consulting (OEC), a Singapore-based management training and consulting firm established in 2009. With over 30 years of experience connecting Lean, TPM, and Quality disciplines to measurable business results, including senior roles at IBM, Microsoft, and Underwriters Laboratories (UL), Allan has led performance improvement programmes for organisations including Micron, Lam Research, Tokyo Electron, Panasonic, STATS ChipPAC, Sika, and Toyota Tsusho.
He holds a Bachelor of Engineering (Mechanical) from the National University of Singapore and completed advanced consultancy training in Japan as a Colombo Plan Scholar. Allan is a Certified Management Consultant (Japan), a Certified Lean Six Sigma Black Belt, and an accredited TPM Instructor.
Most operational excellence programmes generate activity — Kaizen events, audit scores, training completions — without ever proving they moved a business result. This guide sets out, framework by framework, how to define business performance correctly, diagnose the real gap, close it, align the organisation behind it, and sustain the gain so it survives past the consultant's exit date.
If you have sat through a steering committee review where the Kaizen calendar showed twenty-two completed events, the training dashboard showed ninety percent completion, and the finance director quietly asked why none of it appeared in this quarter's cost line, you already understand the problem this guide exists to solve. I have sat on both sides of that table — as the practitioner presenting the activity metrics, and, earlier in my career at the National Productivity Board, as the one asking companies to show me the business result rather than the workshop attendance sheet. The uncomfortable answer, most of the time, is that the activity was real and the connection to business performance was never actually built. It was assumed.
This is not a failure of Lean, Six Sigma, or TPM as methodologies. Every one of these disciplines is, at its core, a system for improving performance — output, cost, quality, delivery, safety, and the morale that sustains all four. The failure sits earlier, in the step most improvement programmes skip: defining, in the language finance and operations both recognise, exactly which business performance metric a given improvement activity is supposed to move, by how much, and over what timeframe, before the first Kaizen event is scheduled. Skip that step and you get a programme full of technically correct improvement work that management can neither defend in a budget review nor connect to the numbers the board actually asks about.
This guide draws on the diagnostic, improvement, alignment, and sustainment frameworks I use across manufacturing, logistics, and public-sector engagements to answer a deliberately broad practitioner question: how do you use operational excellence to move business performance, not just process metrics? It builds on work I have published separately across the TPM cluster — OEE Benchmarking, Focused Improvement, Autonomous and Planned Maintenance — and the Lean Thinking and Strategy Execution clusters covering Value Stream Mapping, Hoshin Kanri, and Leader Daily Management Systems. This article is the connective layer that ties them to the result a business actually has to report.
Why Improvement Activity Stalls Before It Reaches the P&L
The pattern I encounter most often, across industries as different as semiconductor fabrication and public-sector service delivery, is what I call activity-result disconnection: an operational excellence programme generates a steady stream of completed improvement projects, each individually defensible, none of them tied to a pre-agreed business metric with a target and an owner. The programme looks busy. Whether it is working is a separate, unanswered question.
The disconnection usually traces back to how targets get set. A Kaizen event gets scoped around a process the team already knows how to improve — cycle time on a familiar line, defect rate on a familiar station — rather than around the business metric leadership actually needs to move this quarter. The team delivers a genuine, measurable process improvement. It is not. The specific process chosen was rarely the constraint holding back the business result leadership cared about, so the improvement, however real, does not show up where anyone is looking for it.
The second and closely related failure is measurement lag. Process metrics — cycle time, first-pass yield, OEE — update daily or weekly. Business performance metrics — cost per unit, gross margin, on-time delivery percentage reported to the customer, revenue per employee — often update monthly or quarterly, and travel through finance systems the operations team does not directly control. By the time the business metric reports, the improvement team has moved on to the next Kaizen event, and nobody circles back to confirm the two numbers actually connect. I have walked into organisations running an active, well-resourced continuous improvement programme that could not, when asked directly, name which specific business KPI their current quarter of Kaizen activity was targeting.
The third failure, and the one that costs the most once it compounds, is that operational excellence gets organisationally separated from strategy deployment. The people running Hoshin Kanri and setting the annual business targets sit in one planning cycle; the people running the Kaizen calendar and the daily improvement work sit in another, operating cadence. Without an explicit catchball mechanism connecting the two, the improvement team optimises whatever is locally visible and technically tractable, while the strategy team sets targets with no visibility into which levers the shop floor or service line can actually pull. Both groups are working hard. Neither is necessarily working on the same problem.
Defining Business Performance the Operational Excellence Way: PQCDSM
Before diagnosing anything, the practitioner needs a shared, cross-functional definition of what "business performance" actually means for the organisation in front of them — precise enough that a Kaizen team, a finance controller, and a business unit head would all recognise the same result if they saw it. The framework I use to build that shared definition is PQCDSM: Productivity, Quality, Cost, Delivery, Safety, and Morale. It is deliberately broader than a single financial metric because business performance rarely improves through one lever pulled in isolation; a cost reduction achieved by degrading delivery reliability or burning out the workforce is not a business performance improvement, it is a metric substitution that will surface as a different problem within two quarters.
Productivity asks what output the organisation generates per unit of input — labour hour, machine hour, square metre of floor space — and is usually the metric closest to what a business unit head means when they say "performance" in a review. Quality, measured through first-pass yield, defect rate, and the cost of quality methodology I worked with extensively during my National Productivity Board tenure, captures how much of that output is actually usable without rework, a distinction that matters enormously because rework hides inside productivity numbers unless it is separately tracked. Cost aggregates the financial consequence of the other dimensions and is where most business performance conversations start and, unhelpfully, often stop. Delivery captures whether the customer receives what was promised, when it was promised — the metric most directly connected to the customer value work I have covered separately, and the one most likely to be quietly sacrificed when a cost target is pursued in isolation. Safety and Morale are frequently treated as compliance obligations rather than performance levers, which is a genuine strategic error: an organisation with high injury rates or high voluntary turnover is paying a business performance cost that rarely appears on the same dashboard as the productivity numbers it is simultaneously reporting.
The discipline PQCDSM enforces is a forced trade-off conversation before any improvement work begins. Every proposed Kaizen event, TPM initiative, or process redesign should be able to state which PQCDSM dimension it primarily targets, and — this is the step most programmes skip — which of the other five dimensions it might inadvertently degrade. An improvement that boosts productivity by increasing machine speed without checking the corresponding quality and safety impact is not a validated improvement; it is an untested hypothesis wearing a completed-project label.
Diagnosing the Gap: OEE, Cost of Quality, and Root Cause Analysis
Once the organisation agrees on what business performance means across PQCDSM, the next practitioner task is diagnosing where the actual gap sits, as opposed to where it is assumed to sit. This is where Overall Equipment Effectiveness, Cost of Quality analysis, and structured Root Cause Analysis do their real work, and where I find the second most common diagnostic mistake: teams diagnose the symptom that is easiest to measure rather than the one that is actually constraining the business result.
OEE decomposes equipment performance into three multiplicative factors — availability, performance, and quality — and the diagnostic value of the framework is precisely in that decomposition, because the three factors respond to entirely different improvement levers and are routinely confused with each other. In an anonymised OEE benchmarking exercise I ran across three Asia-Pacific semiconductor manufacturers, the consistent finding was that availability losses — unplanned downtime, changeover time — were the dominant constraint at all three sites, while the improvement effort each site had already invested was disproportionately weighted toward performance optimisation, running the equipment faster rather than running it more consistently. The business performance consequence of that mismatch is direct: money and engineering time were being spent against the smaller of the three OEE factors while the larger one went largely unaddressed, because performance losses are more visible on a shift-by-shift basis than the accumulated cost of frequent short stoppages.
Cost of Quality analysis performs the equivalent diagnostic function on the quality dimension, and it was central to the national programmes I co-led at the National Productivity Board, where participating companies achieved an average 42.3 percent reduction in quality costs, a combined S$3 million in savings across the cohort. The diagnostic power of Cost of Quality lies in separating prevention costs, appraisal costs, and failure costs — internal and external — because most organisations, left to their own instincts, over-invest in appraisal (inspection, testing) relative to prevention, and chronically under-track external failure cost, which is frequently the largest and least visible of the four categories because it surfaces as customer returns, warranty claims, and lost repeat business rather than as a line item anyone in operations directly owns.
Root Cause Analysis is the tool that converts a diagnosed gap into an actionable improvement target, and its business performance value depends entirely on discipline most teams abandon under time pressure: continuing past the first plausible cause to the systemic cause that, if left unaddressed, will regenerate the same performance gap under a different symptom next quarter. A recurring on-time delivery miss traced only as far as "the supplier was late" produces a corrective action against that supplier. The same miss, traced through a proper five-why or fishbone analysis to an underlying root cause — no supplier performance scorecard exists, so lateness is only ever discovered after the fact — produces a corrective action that prevents the entire category of failure, not just the specific instance. Structure and logic first. Documentation second.
Closing the Gap: Focused Improvement and the Eight Wastes
With the diagnosis complete, Focused Improvement — Kobetsu Kaizen, TPM's dedicated pillar for eliminating the specific losses identified through OEE and Cost of Quality analysis — is the mechanism that converts the diagnosis into a closed performance gap. The discipline that separates Focused Improvement from generic Kaizen activity is targeting: rather than running improvement events against whatever process a team happens to know well, Focused Improvement events are explicitly scoped against the highest-loss category identified in the OEE or Cost of Quality breakdown, with the business performance target — a specific PQCDSM metric, a specific magnitude, a specific date — set before the improvement team is even assembled.
The eight wastes function here as the practitioner's search checklist for where the loss is actually hiding, and business performance improvement work benefits from treating them as a diagnostic lens rather than a Lean vocabulary exercise. Overproduction ties up working capital in inventory the business does not yet need to sell, a direct cost-of-capital drag that rarely appears on a production efficiency dashboard but appears immediately on a cash flow statement. Waiting — of people, of equipment, of work-in-progress — is lost throughput capacity that a business performance conversation should translate directly into forgone revenue potential, not just idle time. Defects are the most obviously connected to Cost of Quality, but the connection is frequently under-quantified because internal failure cost calculations stop at scrap and rework labour without including the opportunity cost of the capacity consumed producing the defective unit in the first place. Unused talent — the eighth waste, and in my experience across the semiconductor and logistics clients I have worked with, the most consistently under-diagnosed — represents a business performance cost that shows up nowhere on a standard operations dashboard at all: the frontline improvement ideas never surfaced, the process knowledge that leaves with a departing employee, the capability the organisation paid to train and then never deployed against its highest-value problem.
The business performance discipline that Focused Improvement adds on top of standard Kaizen practice is closure verification: a Focused Improvement project is not complete when the process change is implemented, it is complete when the pre-agreed business metric has actually moved and been independently confirmed, typically thirty to ninety days after implementation, against a baseline captured before the project started. Skip that verification step and you are back to activity-result disconnection — a completed project with an assumed, unconfirmed business impact.
Aligning the Organisation: Hoshin Kanri and the Catchball Discipline
Diagnosis and Focused Improvement close individual performance gaps. Business performance at the organisational level requires those individual gaps to be prioritised against each other and connected to a single set of enterprise targets, which is the function Hoshin Kanri performs and the reason it belongs at the centre of this guide rather than as a peripheral strategy tool. I have deployed Hoshin Kanri with clients including DSTA and Prudential Singapore specifically to solve the organisational misalignment described earlier — strategy planning and improvement execution running on separate cadences with no shared vocabulary.
The catchball process, Hoshin Kanri's signature mechanism, forces an iterative negotiation between the annual business targets senior leadership sets and the operational capability the frontline teams who have to deliver those targets can actually confirm. A target that arrives at the shop floor or service line without catchball is, functionally, a wish rather than a plan; it has not been tested against what the people closest to the process actually believe is achievable, and it frequently sets a business performance target the organisation has no realistic operational pathway to hit, which produces the same activity-result disconnection this guide opened with, just generated top-down instead of bottom-up.
The X-matrix, or equivalent strategy deployment tool, is where PQCDSM, OEE, and Cost of Quality metrics get explicitly linked to the annual business targets, so that a specific Focused Improvement project can be traced upward to the specific enterprise-level performance target it supports, and a specific enterprise target can be traced downward to the specific improvement projects funded to deliver it. This traceability is the single structural fix for the disconnection problem I described at the start of this guide: it makes it organisationally impossible to run a Kaizen calendar that cannot answer which business result it is working toward, because the answer is written into the deployment matrix before the project is approved.
Sustaining the Gain: Standard Work, Autonomous Maintenance, and LDMS
Closing a performance gap once is a project outcome. Keeping it closed is an operational discipline, and it is the step where I see more hard-won business performance gains quietly erode than at any other point in the improvement lifecycle. A Focused Improvement project that reduces changeover time or defect rate will regress toward the original baseline within a few months unless the new way of working is locked in through Standard Work, sustained through frontline ownership, and monitored through a daily management system that would actually notice the regression before it becomes a quarter-end surprise.
Standard Work converts the specific process change validated during the improvement project into the only way the task is performed, regardless of which shift or which operator is running it. Without this codification step, the improvement survives only as long as the specific individuals who implemented it remain in the role, which is precisely why performance gains achieved through informal tribal knowledge decay so predictably once staff turnover, shift rotation, or organisational change intervenes.
Autonomous Maintenance, the TPM pillar I have built curriculum and audit toolkits around extensively, performs the equivalent sustainment function for equipment-driven performance gains specifically. An OEE improvement achieved through a Focused Improvement project on a specific machine will regress as equipment condition drifts back toward its previous state, unless operators are trained and equipped to detect and correct the early signs of that drift themselves, at the point of occurrence, rather than waiting for a scheduled maintenance cycle or a full breakdown to surface the problem. This is the direct business performance argument for Autonomous Maintenance that is frequently lost when the pillar gets treated purely as a housekeeping or safety initiative: it is, at its core, a sustainment mechanism for whatever availability and performance gains Focused Improvement has already achieved.
Leader Daily Management Systems close the loop at the management cadence level, and this is the mechanism I have found makes the single largest difference to whether a business performance gain survives past the first six months. The LDMS discipline I have implemented across multiple clients, built on an eight-dimension assessment model and grounded in the daily management principles documented in David Mann's Creating a Lean Culture, puts the specific PQCDSM metrics targeted by the Hoshin Kanri deployment onto a tier board that a frontline supervisor reviews every single day, with a defined escalation path the moment the metric drifts outside its expected range. A business performance target reviewed once a quarter in a steering committee will always regress faster than the daily improvement cadence can catch it. A target visible on a tier board every morning gets corrected the same week the drift begins.
Where This Breaks: Common Mistakes I See in the Field
The most common mistake is scoping improvement work around process familiarity rather than diagnosed business impact — running Kaizen events against the process the team already knows how to improve, rather than against the highest-loss category surfaced by OEE or Cost of Quality analysis. The event succeeds by its own internal metrics and contributes little to the business performance number leadership is actually watching.
The second is skipping closure verification. A Focused Improvement project gets marked complete when the process change goes live, with nobody scheduled to confirm, thirty or sixty days later, that the targeted business metric actually moved and held. Without that verification step, the improvement portfolio accumulates a growing gap between reported project completions and confirmed business impact, and eventually someone in finance notices the gap before the operations team does.
The third is treating PQCDSM dimensions independently rather than as a connected trade-off system. A productivity initiative gets approved and executed without an explicit check against quality, delivery, safety, and morale impact, and the organisation discovers the trade-off only after the fact, when a different metric — often external failure cost or voluntary turnover — starts moving in the wrong direction for reasons nobody connects back to the earlier initiative.
The fourth, and the one that compounds every other mistake on this list, is running Hoshin Kanri and the Kaizen calendar as parallel, unconnected processes rather than a single catchball-linked system. Strategic targets get set without operational validation; operational improvement gets executed without strategic prioritisation. Both processes look functional in isolation. Neither is actually driving the business result the other believes it is responsible for.
What the Best Practitioners Do Differently
The organisations that consistently convert operational excellence activity into business performance results build the target and the verification date into the project charter before the improvement team is assembled, not after the fact. Every Focused Improvement project I see succeed on the business performance metric, not just the process metric, was scoped with the answer to "which PQCDSM dimension, by how much, verified when" already written down on day one.
They run their OEE, Cost of Quality, and Root Cause Analysis diagnostics on a fixed cadence — not as a one-time assessment that ages out of relevance, but as a standing input to the Hoshin Kanri annual planning cycle, so that the following year's improvement priorities are set against current loss data rather than last year's assumptions.
They co-locate the finance function inside the improvement governance structure, not as an auditor brought in after the fact to validate savings claims, but as a participant from project scoping onward who confirms the business metric definition and baseline before the improvement work starts. This single structural choice eliminates most of the activity-result disconnection I described at the outset, because the business metric and the process metric are defined together, by people with legitimate authority over both, from the beginning.
And they treat sustainment — Standard Work, Autonomous Maintenance, and the daily tier board — as a funded, staffed part of the improvement project itself, not an unfunded hope that the gain will somehow hold once the project team disbands and moves to the next priority on the roadmap.
The Discipline of Naming the Number First
Every framework in this guide — PQCDSM, OEE, Cost of Quality, Root Cause Analysis, Focused Improvement, Hoshin Kanri, Standard Work, Autonomous Maintenance, and LDMS — is answering some version of the same underlying question: which specific business number are we trying to move, and how will we know, with evidence rather than assumption, that we actually moved it? It is not a difficult question to ask. It is a difficult discipline to maintain, because naming the number first, before the improvement work begins, requires the operations team and the finance function to agree on a shared definition of success before either side knows whether the project will succeed — an uncomfortable commitment that "we improved the process, and we believe it helped" quietly avoids.
The organisations that build sustained business performance out of operational excellence are not the ones running the most sophisticated individual methodology. They are the ones that have made it structurally impossible to complete an improvement project without naming, verifying, and sustaining the specific business number it was meant to move. Build that discipline into your project charters, your Hoshin Kanri deployment matrix, and your daily tier boards, and every framework in this guide starts pulling toward the same result. Skip it, and you can run the busiest continuous improvement calendar in your industry and still be unable to answer, when the finance director asks, what any of it actually did for the business.
Build Business Performance Capability Through Operational Excellence
Improving business performance through operational excellence is not a single toolkit; it is a connected diagnostic, improvement, alignment, and sustainment system that has to be deployed together and verified against real business metrics. OEC's training and consulting programmes are structured around exactly this connective system:
TPM and OEE Benchmarking — diagnosing where availability, performance, and quality losses are actually concentrated before committing improvement resources.
Total Quality Management and Cost of Quality Analysis — separating prevention, appraisal, and failure costs to target the highest-impact quality investment.
Root Cause Analysis — converting a diagnosed performance gap into a corrective action that closes the systemic cause, not just the immediate symptom.
Focused Improvement and Lean Kaizen — closing targeted performance gaps against a pre-agreed business metric, with built-in closure verification.
Hoshin Kanri / Strategy Deployment — connecting enterprise business targets to frontline improvement priorities through structured catchball.
TWI, Standard Work, Autonomous Maintenance, and Leader Daily Management Systems (LDMS) — sustaining the gain through daily frontline ownership and tiered management review.
About the Author
Allan Ung is the Founder and Principal Consultant of Operational Excellence Consulting, a Singapore-based management training and consulting firm established in 2009. With over 30 years of experience leading operational excellence and business performance transformation across manufacturing-intensive and service-intensive environments alike, Allan's expertise spans Lean Thinking, Total Quality Management (TQM), TPM, TWI, Hoshin Kanri strategy deployment, and structured problem solving.
He is a Certified Management Consultant (CMC, Japan), Lean Six Sigma Black Belt, TPM Instructor (Japan Institute of Plant Maintenance), TWI Master Trainer, ISO 9001 Lead Auditor, and former Singapore Quality Award National Assessor.
During his tenure with Singapore's National Productivity Board (now Enterprise Singapore), Allan pioneered Cost of Quality and Total Quality Process initiatives that enabled companies to reduce quality costs by an average of 42.3 percent, a combined S$3 million in savings across the cohort. In senior regional and global roles at IBM, Microsoft, and Underwriters Laboratories, he led Lean deployment, OEE improvement, and quality system strengthening across cross-border manufacturing operations.
Allan has facilitated OEE, Focused Improvement, and Hoshin Kanri deployment programmes for organisations including Micron, Lam Research, Tokyo Electron, Panasonic, STATS ChipPAC, Amkor Technology, Sika, Toyota Tsusho, and DSTA. He holds a Bachelor of Engineering (Mechanical Engineering) from the National University of Singapore and completed advanced consultancy training in Japan as a Colombo Plan Scholar.
His philosophy: "Eliminate everything that does not add value in the customer's eyes."
His practitioner-led toolkits have been used by managers and organisations across Asia, Europe, and North America to build Lean and TPM capability and to drive measurable business performance improvement.
👉 Learn more at: www.oeconsulting.com.sg
Further Learning Resources
Value Stream Mapping: The Complete Practitioner Guide — the foundational Lean Thinking article behind the loss-diagnosis discipline referenced in this guide, including the Micron value stream mapping case.
OEE: A Practitioner's Guide — the full availability, performance, and quality decomposition introduced in this article's diagnostic section.
Focused Improvement: A Practitioner's Guide — the complete Kobetsu Kaizen methodology for closing the highest-loss categories surfaced through OEE and Cost of Quality analysis.
Hoshin Kanri: The Complete Practitioner Guide — the catchball discipline and X-matrix deployment tool referenced in this article's alignment section.
Leader Daily Management System (LDMS): A Practitioner's Guide — the eight-dimension daily management model behind this article's sustainment argument.
From Resistance to Resilience: The Change Management Practitioner Guide — the discipline for making a sustained performance gain survive the organisational change that so often unravels it.
Operational Excellence Consulting offers a full catalog of facilitation‑ready training presentations and practitioner toolkits covering Lean, Design Thinking, and Operational Excellence. These resources are developed from real workshops and transformation projects, helping leaders and teams embed proven frameworks, strengthen capability, and achieve sustainable improvement.
👉 Explore the full library at: www.oeconsulting.com.sg