Customer Value: The Complete Practitioner's Guide to Operational Excellence That Customers Can Feel
By Allan Ung | Founder & Principal Consultant, Operational Excellence Consulting (OEC)
Published: 27 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 linking Lean, Quality, and Design Thinking disciplines to customer outcomes, including senior roles at IBM, Microsoft, and Underwriters Laboratories (UL), Allan has facilitated customer value and process improvement programmes for organisations including Micron, Tokyo Electron, Panasonic, PSA, Prudential Singapore, NileDutch, and Singapore's Ministry of Social and Family Development (MSF).
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.
Operational excellence and customer value are usually run as two separate programmes with two separate owners. They are not separate. This guide sets out, framework by framework, how Lean's definition of value, the Voice of the Customer, the Value Proposition Canvas, Customer Journey Mapping, and the daily management disciplines that sustain them fit together into a single system for improving what the customer actually experiences.
If you have run a Kaizen event and watched the cycle time fall while the complaint log stayed exactly where it was, you already know the uncomfortable truth this article is built around: operational improvement and customer value improvement are not the same project, and treating them as the same project is why so many transformation efforts produce internal applause and external indifference. I have sat in enough steering committee reviews to have seen the pattern repeat itself across semiconductor fabs, logistics operators, and public-sector service counters alike. A process gets faster, cheaper, or more compliant with SOP, and the metrics on the wall move in the right direction. Then the customer satisfaction score, or the citizen feedback score, or the net promoter score, does not move at all — or moves the wrong way, because the "efficiency" came from cutting something the customer was quietly relying on.
This is not an argument against Lean, Six Sigma, or TPM. It is an argument for sequencing them correctly. Every methodology I have deployed over three decades — value stream mapping, TPM's eight pillars, Hoshin Kanri, root cause analysis — is, at its foundation, a tool for removing waste from a system. But waste is not a fact of nature; it is a judgement, and the judgement has to be made from the customer's seat, not the process owner's. Get that sequencing wrong — optimise the process first and ask about the customer later, if at all — and you get local efficiency with no connection to what the person on the receiving end actually values. Get it right, and every Lean, Quality, and Design Thinking tool in the OEC toolkit becomes a mechanism for delivering more of what the customer is actually paying for, in less time, with fewer defects.
This guide draws on the frameworks I use with clients across manufacturing, logistics, and public service delivery to answer one practitioner question: how do you systematically improve customer value using the discipline of operational excellence, rather than treating "customer-centricity" as a slogan bolted onto a cost-reduction programme? It follows on from two clusters of work I have published separately — the Lean Thinking series, anchored by our Value Stream Mapping guide, and the Design Thinking and Strategy Execution series covering the Value Proposition Canvas, Business Model Canvas, and Customer Journey Mapping. This article is the bridge between them.
Why Efficiency Without Customer Value Is a Trap
Every operational excellence programme I have led begins with a question that sounds almost too simple to ask out loud: value to whom? In the National Productivity Board days, when I co-led our national Cost of Quality and Total Quality Process programmes, the answer seemed obvious — value meant conformance to specification, and cost of quality meant the price of failing to conform. Those programmes worked; participating companies cut their quality costs by an average of 42.3 percent, a combined S$3 million in savings across the cohort. But conformance to specification is an internal definition of value. It tells you whether you built the thing right. It tells you nothing about whether you built the right thing, or whether the customer noticed the improvement at all.
That distinction is where most operational excellence programmes quietly go wrong. A process team eliminates a non-value-adding step, measures the reduction in cycle time, reports it up the chain as a win, and moves to the next target on the improvement roadmap. Nobody asked the customer whether that step was actually invisible to them or whether it was, unbeknownst to the process team, the one point in the transaction where a human being reassured them the order was correct. I have seen this exact failure mode in service redesigns at public agencies, where removing a manual verification step cut processing time by days but also removed the one touchpoint where an anxious applicant could ask a question. The metric improved. The experience did not.
The waste elimination that Lean is famous for — the seven or eight classic wastes of overproduction, waiting, transport, over-processing, inventory, motion, defects, and unused talent — only functions as a customer value tool if the definition of "value-added" used to classify each process step comes from an external, verified customer definition rather than an internal, assumed one. This is the single most common gap I find when auditing a client's value stream map: the value-added/non-value-added classification was done in a conference room by process owners, using their best guess about what the customer wants, and never verified against an actual customer statement. A guess dressed up as data is still a guess.
Defining Value the Lean Way: The First Question Before Any Improvement
Lean thinking opens with a single sentence that is easy to recite and hard to operationalise: value is defined by the customer, not the producer. Before you draw a single box on a value stream map, before you launch a single Kaizen event, you need an answer — grounded in the customer's own words, not your organisation's internal shorthand — to what specifically they are willing to pay for, wait for, or tolerate inconvenience for.
In practice, this means every value stream mapping exercise I facilitate begins with a Voice of the Customer pass before the current-state map is drawn. Skip that step and the VA/NVA classification exercise becomes an exercise in confirming what the team already believed. I have watched teams label an inspection step "value-added" because it feels productive, when the customer in question told us directly, when asked, that they would happily accept a slightly higher defect rate in exchange for a shorter lead time. That single piece of Voice of the Customer data reclassified an entire sub-process from value-added to non-value-added, and the redesign that followed delivered results the earlier, un-validated map never would have found. It is the same discipline that underpinned the Micron value stream mapping engagement I have documented separately — a USD 1 million improvement that came not from working the existing process harder, but from re-drawing the value definition before touching the process at all.
The eight wastes are, functionally, a checklist of everything that is not customer value. Overproduction produces things the customer has not asked for yet. Waiting delays the delivery of value the customer is already owed. Over-processing — my personal candidate for the most under-diagnosed of the eight — does more to the product or service than the customer's own stated requirement calls for: polishing a report to a level of formatting the recipient never notices, running a quality check the customer's own specification does not require, adding an approval layer the customer never asked to be protected by. None of this is waste in the abstract. It is waste only in relation to a specific, verified customer value definition. Change the customer, or change what that customer values, and the classification changes with it. This is precisely why value definition has to be the first step of any operational excellence programme and not an afterthought layered on at the end.
Hearing the Customer Correctly: VOC, Kano, and the House of Quality
If Lean tells you that value must be defined by the customer, the next practitioner question is mechanical: how do you actually capture that definition with enough precision to act on it? This is where Voice of the Customer methodology, the Kano Model, and Quality Function Deployment's House of Quality come in, and where I see the second most common gap in client programmes — organisations that collect customer feedback constantly but never structure it into something a process redesign team can use.
Voice of the Customer is not a survey. It is a structured capture discipline — interviews, direct observation, complaint pattern analysis, and Gemba-based listening at the point where the customer actually experiences the service — that translates a customer's own words into a specific, verifiable requirement statement. The discipline matters because customers rarely state requirements in a form an engineer or process designer can act on directly. A customer says "I want this fast." A well-run VOC process translates that into a specific, measurable requirement: turnaround time under a stated number of hours, confirmed against what the customer actually does with that time once it is theirs. Confuse the raw statement with the requirement, and you risk designing a solution to the wrong specification entirely.
The Kano Model then sorts those captured requirements into categories that most improvement teams treat as interchangeable and should not: basic (must-be) requirements, whose absence causes dissatisfaction but whose presence generates no delight because the customer assumed you would deliver them anyway; performance requirements, where more is proportionally better and the customer will notice and reward incremental gains; and delighter requirements, unexpected attributes the customer did not think to ask for but that generate disproportionate loyalty when present. The practical value of this sorting is that it stops organisations from over-investing in basic requirements that have already reached the point of diminishing returns — chasing an already-adequate turnaround time down by another few hours — while under-investing in the one delighter that would actually move the customer's perception. I have used this categorisation repeatedly in service-sector engagements to redirect improvement budgets away from polishing what the customer already takes for granted and toward the handful of attributes that genuinely differentiate the experience.
Quality Function Deployment's House of Quality is the more rigorous cousin of this exercise, most useful where the customer requirement has to be translated all the way down into engineering or process specifications with competing trade-offs — the classic environment across the semiconductor and precision manufacturing clients I have worked with, including Lam Research, Micron, and Analog Devices. The House of Quality forces an explicit correlation matrix between what the customer said they wanted and what the technical or process team controls, surfacing conflicts — where satisfying one customer requirement degrades another — before they show up as a defect on the production floor or a complaint in the field. Deployed properly, it prevents the single most expensive category of quality cost: the requirement that was correctly captured from the customer, then quietly lost or distorted somewhere between the voice of the customer and the specification sheet.
Seeing the Value Proposition Whole: The Value Proposition Canvas and Business Model Canvas
Capturing individual requirements is necessary but not sufficient. At some point the practitioner has to step back and ask whether the collection of requirements, taken together, adds up to a coherent value proposition — something the customer would recognise as a reason to choose you over the alternative. This is the gap the Value Proposition Canvas closes, and it is a tool I have written about separately in full because it deserves the depth. In brief, for the purposes of this article: the canvas splits into a Customer Profile — the jobs the customer is trying to get done, the pains they experience along the way, and the gains they are hoping for — and a Value Map, which states plainly how your products, services, and processes relieve those specific pains and create those specific gains. The discipline in the canvas is not the boxes; it is the requirement that every entry on the Value Map trace back to a named entry on the Customer Profile. A pain reliever with no corresponding customer pain is a feature nobody asked for, and in operational excellence terms, it is a form of over-processing before a single process step has even been designed.
The Business Model Canvas sits one level further out, asking whether the value proposition you have designed is viable across the whole operating model — cost structure, channels, key resources, key activities — not just desirable to the customer. I incorporated a client testimonial from Nelson Quek at PSA Corporation into that article precisely because PSA's own experience illustrates the point: a value proposition that looks compelling on paper still has to survive contact with the operational and channel realities of delivering it at the scale a port operator, or any large-scale service organisation, actually requires. Customer value work that never makes this connection to the business model risks producing an elegant customer profile that the organisation has no realistic operational pathway to deliver against.
The link back to operational excellence is direct and, in my experience, frequently missed: the Value Map's pain relievers and gain creators are not marketing promises. They are operational commitments. Every entry on that map has to be traceable to a process, a standard, or a control that the organisation actually runs — and traceable in the other direction too, so that when a process improvement team proposes cutting a step, someone checks the Value Map before approving the cut. This is the connective tissue I most often find missing between the strategy team that owns the Value Proposition Canvas and the operations team running the Kaizen calendar. They should be reading from the same document. In most organisations I have audited, they have never seen each other's document at all.
Walking the Customer's Path: Customer Journey Mapping and Gemba
Where the Value Proposition Canvas gives you the customer's world at a single point in time, Customer Journey Mapping gives you the customer's experience across time — every touchpoint, from first awareness through to post-delivery support, laid out sequentially with the customer's actions, emotions, and pain points attached to each stage. I have built this out as its own practitioner guide within the Design Thinking cluster, and the reason it belongs in an operational excellence conversation, rather than staying siloed as a marketing or UX tool, is that most of the touchpoints on a customer journey map are, in fact, process steps your organisation already runs and already has the tools to improve.
The practitioner value of overlaying a customer journey map against an internal value stream map is that it exposes a category of waste that pure process mapping cannot see on its own: the handoff. Handoffs between departments are frequently invisible to the internal process owner, who sees their own segment of the process as complete and compliant, while the customer experiences the same handoff as a gap — a repeated request for information already given, a silence while ownership transfers internally, a loss of continuity in who is accountable for their case. I have not yet run a journey-mapping exercise with an operations team that did not surface at least one handoff nobody inside the organisation had previously flagged as a problem, precisely because no single internal process owner experiences the full handoff the way the customer does.
This is also where the Gemba Walk earns its place in a customer value programme rather than remaining a shop-floor observation ritual. A Gemba Walk conducted from the customer's physical or digital vantage point — sitting where the customer sits, using the channel the customer uses, waiting the length of time the customer waits — routinely surfaces friction that no internal metric captures, because internal metrics are built around the boundaries of internal process ownership, not around the customer's continuous experience. Structured correctly, Gemba observation and Customer Journey Mapping are the same discipline applied at different resolutions: go and see, from the customer's position, what is actually happening, rather than trusting the dashboard built from the organisation's own instrumentation.
From Diagnosis to Delivery: TPM, Standard Work, and Hoshin Kanri as the Engine
Diagnosing what the customer values and where the experience currently breaks is the analytical half of the work. The harder half, and the one that separates a workshop output from a sustained result, is building the operational discipline that reliably delivers against that diagnosis every day, not just in the weeks immediately following the improvement event. This is where TPM, Standard Work, and Hoshin Kanri stop being separate methodologies and become the delivery engine for everything the earlier frameworks identified.
Total Productive Maintenance is, on the surface, an equipment reliability discipline, and in the semiconductor and precision manufacturing engagements I have run — with clients including Tokyo Electron, Panasonic, STATS ChipPAC, and Amkor Technology — its connection to customer value is direct and unambiguous: unplanned equipment failure is one of the most common root causes of the defects and late deliveries that erode customer trust fastest. But TPM's contribution to customer value goes further than uptime. The Education & Training pillar, and the broader autonomous maintenance discipline it supports, builds the frontline capability to notice small deviations before they compound into the kind of variation a customer actually experiences as inconsistency. A customer rarely complains about a single late shipment. They complain about unpredictability — a service that is sometimes fast and sometimes slow, sometimes right and sometimes wrong. TPM's discipline of standard conditions and early abnormality detection is, at root, a variation reduction programme, and variation reduction is very often what a customer means when they describe an organisation as reliable.
Standard Work performs the equivalent function at the level of individual task execution. A customer value requirement that has been correctly captured through VOC, correctly categorised through Kano, and correctly designed into the Value Proposition Canvas will still fail to reach the customer consistently if the frontline process that delivers it is left to individual judgement and informal habit. Standard Work is not bureaucracy for its own sake; it is the mechanism that makes a customer promise repeatable across every shift, every location, and every member of staff delivering it, which is precisely why it belongs in the same conversation as customer value rather than being treated as a purely internal efficiency tool.
Hoshin Kanri closes the loop at the strategic level, and this is the step I find missing most often even in organisations that have done excellent work on VOC, Kano, and journey mapping in isolation. Customer value insights captured at the frontline have to travel upward into the annual strategy deployment process, and strategic customer value priorities have to travel back downward into the daily targets that shop-floor and service-counter teams actually manage against — the same catchball discipline that underpinned the Hoshin Kanri engagements I ran with DSTA and Prudential Singapore. Without that two-way translation, customer value work stays trapped as a series of disconnected projects: a journey mapping workshop here, a VOC survey there, none of them connected to what the organisation's leader daily management system — the LDMS discipline documented in David Mann's work and the one I have implemented across multiple clients — actually tracks and escalates on a daily basis. A customer value insight that never makes it onto a tier board is an insight that will be re-discovered, at cost, the next time a customer complains.
Where This Breaks: Common Mistakes I See in the Field
The first and most common mistake is sequencing: running the process improvement before the customer value definition, then retrofitting a customer justification onto a solution the team had already decided to build. It is not. Teams that do this can usually recite a customer benefit for their chosen improvement, but the benefit was generated after the decision, not before it, and it rarely survives contact with an actual customer interview.
The second is treating Voice of the Customer as a one-time data collection exercise rather than a standing input to the operational excellence programme. Customer requirements shift — sometimes gradually, sometimes because a competitor resets the baseline of what counts as acceptable — and a VOC exercise conducted two years ago is quietly decaying in relevance even if nobody has told the improvement team.
The third mistake is organisational: the team that owns the Value Proposition Canvas and Customer Journey Map sits in strategy or marketing, while the team running Kaizen events and Standard Work sits in operations, and the two groups rarely share a workshop, let alone a document. I have walked into more than one organisation where the operations team could describe their process metrics in detail but had never seen the customer journey map their own strategy function had commissioned the year before.
The fourth is measurement mismatch. Organisations frequently measure operational improvement in internal units — cycle time, first-pass yield, cost per transaction — while measuring customer value in an entirely separate survey instrument that runs on a different cadence and reports to a different committee. Structure and logic first. Documentation second. Until those two measurement systems are reconciled against the same value definition, leadership will keep approving process changes with no visibility into whether they helped or hurt the customer experience the survey is meant to be tracking.
What the Best Practitioners Do Differently
The practitioners who get this right treat the Voice of the Customer as a recurring input into the Hoshin Kanri annual planning cycle, not a separate project with its own budget line and its own end date. Customer insight is scheduled to arrive before strategy deployment begins, not after the annual targets have already been set.
They also insist on co-locating, at least for the duration of a redesign, the people who own the customer-facing map and the people who own the internal process map. The handoff waste that Customer Journey Mapping exposes is almost always cross-functional by nature, and cross-functional waste cannot be solved by a single department working alone, however good their individual Kaizen discipline is.
They build the Kano categorisation into their improvement prioritisation criteria explicitly, rather than defaulting to whichever process has the loudest internal advocate or the easiest data to collect. A performance requirement with a clear, measurable gap to the competitor's benchmark gets prioritised ahead of a basic requirement the organisation has already satisfied, even when the basic requirement's data set is easier to pull.
And they close the loop back to the shop floor or service counter through a daily management system that makes customer value visible at the same cadence as production output or service volume — not as an annual survey score reviewed once a year, but as a tier-board metric a frontline supervisor sees and discusses every day, the same discipline I have implemented through LDMS deployments built on the eight-dimension assessment model I use with clients across manufacturing and service environments alike.
The Discipline of Asking "Whose Eyes?"
Every framework in this guide — Voice of the Customer, Kano, the House of Quality, the Value Proposition Canvas, Customer Journey Mapping, TPM, Standard Work, Hoshin Kanri — is answering some version of the same question in a different form: through whose eyes are we defining value, and how do we know? Lean's founding instruction to eliminate everything that does not add value in the customer's eyes is deceptively simple to state and genuinely difficult to operationalise, because the eyes in question belong to someone who is not in the room when most process decisions get made.
The organisations that improve customer value sustainably are not the ones with the most sophisticated individual tool. They are the ones that have built the habit of asking, before every improvement decision, whose eyes this judgement is actually being made through — the customer's, or the process owner's convenient assumption about the customer. Build that single discipline into your Kaizen calendar, your Hoshin Kanri catchball, and your daily tier boards, and every methodology in this guide starts pulling in the same direction. Skip it, and you can run the most technically proficient operational excellence programme in your industry and still watch your customer satisfaction score refuse to move.
Build the Capability: Unifying Operational Excellence and Customer Value
Improving customer value through operational excellence is not a single workshop; it is a set of connected disciplines that have to be deployed together and sustained daily. OEC's training and consulting programmes are built around exactly this connective structure rather than teaching each methodology in isolation:
Lean Thinking and Value Stream Mapping — establishing the customer-verified value definition that every subsequent improvement decision should be tested against.
Design Thinking, Customer Journey Mapping, and the Value Proposition Canvas — translating captured customer insight into a coherent, deliverable value proposition.
TPM (Total Productive Maintenance) — building the equipment reliability and frontline ownership discipline that removes the variation customers experience as inconsistency.
TWI and Standard Work — making customer commitments repeatable across every shift and every member of staff delivering them.
Hoshin Kanri / Strategy Deployment and Leader Daily Management Systems (LDMS) — connecting frontline customer insight to strategic priority-setting, and sustaining the gain through daily tiered management.
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 customer value transformation across manufacturing-intensive and service-intensive environments alike, Allan's expertise spans Lean Thinking, Total Quality Management (TQM), TPM, TWI, Design Thinking, 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, Design Thinking Coach, 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, quality system strengthening, and customer experience redesign across cross-border operations.
Allan has facilitated Voice of the Customer, Value Stream Mapping, and customer journey redesign programmes for organisations including Micron, Lam Research, Tokyo Electron, Panasonic, PSA Corporation, Prudential Singapore, NileDutch, Singapore's Ministry of Social and Family Development (MSF), 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 Design Thinking and Lean capability and to drive customer-centred operational improvement.
👉 Learn more at: www.oeconsulting.com.sg
Further Learning Resources
Value Stream Mapping: The Complete Practitioner Guide — the foundational Lean Thinking article this guide builds on, including the Micron value stream mapping case referenced above.
Value Proposition Canvas: A Practitioner's Guide — the full breakdown of the Customer Profile and Value Map framework introduced in this article's fourth section.
Business Model Canvas: A Practitioner's Guide — including the PSA Corporation client perspective on translating value proposition into an operationally viable model.
Customer Journey Mapping: A Practitioner's Guide — the complete methodology for the touchpoint-by-touchpoint mapping discussed in this article's fifth section.
The Gemba Walk: A Practitioner's Guide — the observation discipline underpinning both process diagnosis and customer-vantage-point verification.
Leader Daily Management System (LDMS): A Practitioner's Guide — the eight-dimension daily management model referenced in the delivery-engine section above.
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