Part of a series of articles on |
Machine industry |
---|
Manufacturing methods |
Industrial technologies |
Information and communication |
Process control |
Zero Defects (or ZD) was a management-led program to eliminate defects in industrial production that enjoyed brief popularity in American industry from 1964 [1] to the early 1970s. Quality expert Philip Crosby later incorporated it into his "Absolutes of Quality Management" and it enjoyed a renaissance in the American automobile industry—as a performance goal more than as a program—in the 1990s. Although applicable to any type of enterprise, it has been primarily adopted within supply chains wherever large volumes of components are being purchased (common items such as nuts and bolts are good examples).
"[...] Zero Defects is a management tool aimed at the reduction of defects through prevention. It is directed at motivating people to prevent mistakes by developing a constant, conscious desire to do their job right the first time." [2] : vii — Zero Defects: A New Dimension in Quality Assurance
Zero Defects seeks to directly reverse the attitude that the number of mistakes a worker makes doesn't matter since inspectors will catch them before they reach the customer. [2] : 4 This stands in contrast to activities that affect the worker directly, such as receiving a paycheck in the correct amount. Zero Defects involves reconditioning the worker "to take a personal interest in everything he does[,] by convincing him that his job is just as important as the task of the doctor or the dentist." [2] : 4
The development of Zero Defects is credited to Philip B. Crosby, a quality control department manager on the Pershing missile program at the Martin Company, [3] though at least one contemporary reference credits a small, unnamed group of Martin employees. [4]
Zero Defects was not the first application of motivational techniques to production: during World War II, the War Department's "E for Excellence" program sought to boost production and minimize waste. [5] [6] [7]
The Cold War resulted in increased spending on the development of defense technology in the 1950s and 1960s. Because of the safety-critical nature of such technology, particularly weapons systems, the government and defense firms came to employ hundreds of thousands of people in inspection and monitoring of highly-complex products assembled from hundreds of thousands of individual parts. [2] : 10 This activity routinely uncovered defects in design, manufacture, and assembly and resulted in an expensive, drawn out cycle of inspection, rework, reinspection, and retest. [2] : 12 Additionally, reports of spectacular missile failures appearing in the press [note 1] heightened the pressure to eliminate defects.
In 1961, the Martin Company's Orlando Florida facility embarked on an effort to increase quality awareness and specifically launched a program to drive down the number of defects in the Pershing missile to one half of the acceptable quality level in half a year's time. [2] : 12 Subsequently, the Army asked that the missile be delivered a month earlier than the contract date in 1962. Martin marshaled all of its resources to meet this challenge and delivered the system with no discrepancies in hardware and documentation and were able to demonstrate operation within a day of the start of setup. [2] : 14¡V15 After reviewing how Martin was able to overachieve, its management came to the conclusion that while it had not insisted on perfection in the past, it had in this instance, and that was all that was needed to attain outstanding product quality. [2] : 15
Management commissioned a team to examine the phenomenon and come up with an action plan, which became the organizing, motivating, and initiating elements of Zero Defects. [2] : 15 The Department of Defense also took notice and in 1964, began to actively encourage its vendors to adopt Zero Defects programs. [8] [9] Interest in the program from outside firms, including Litton Industries, Thiokol, Westinghouse, and Bendix Corporation, [2] : 16 was keen and many made visits to Martin to learn about it. [2] : 16 Their feedback was incorporated and rounded out the program. In particular, General Electric suggested that error cause removal be included in the program. [2] : 16
Martin claimed a 54% defect reduction in defects in hardware under government audit during the first two years of the program. General Electric reported a $2 million reduction in rework and scrap costs, RCA reported 75% of its departments in one division were achieving Zero Defects, and Sperry Corporation reported a 54% defect reduction over a single year. [2] : 17
During its heyday, it was adopted by General Electric, ITT Corporation, Montgomery Ward, the United States Army among other organizations. [10]
While Zero Defects began in the aerospace and defense industry, thirty years later it was regenerated in the automotive world. During the 1990s, large companies in the automotive industry cut costs by reducing their quality inspection processes and demanding that their suppliers dramatically improve the quality of their supplies.
In 1979, Crosby penned Quality Is Free: The Art of Making Quality Certain which preserved the idea of Zero Defects in a Quality Management Maturity Grid, in a 14-step quality improvement program, and in the concept of the "Absolutes of Quality Management". [11] The quality improvement program incorporated ideas developed or popularized by others (for example, cost of quality (step 4), employee education (step 8), and quality councils (step 13)) with the core motivation techniques of booklets, films, posters, speeches, and the "ZD Day" centerpiece. [12]
According to Crosby, there are four Absolutes: [13]
Newcomers to manufacturing bring their own vague impressions of what quality involves. But in order to tackle quality-related problems, there must be widespread agreement on the specifics of what quality means for a particular product. Customer needs and expectations must be reduced to measurable quantities like length, or smoothness, or roundness and a standard must be specified for each. These become the requirements for a product and the organization must inspect, or measure what comes out of the production process against those standards to determine whether the product conforms to those requirements or not. [11] : 17 An important implication of this is that if management does not specify these requirements workers invent their own which may not align with what management would have intended had they provided explicit requirements to begin with. [14] : 78
Companies typically focus on inspection to ensure that defective product doesn't reach the customer. But this is both costly and still lets nonconformances through. [15] Prevention, in the form of "pledging ourselves to make a constant conscious effort to do our jobs right the first time", is the only way to guarantee zero defects. Beyond that, examining the production process for steps where defects can occur and mistake proofing them contributes to defect-free production. [16] [17]
Workers, at least during the post–World War II economic expansion, had a lackadaisical attitude on the whole toward work. Crosby saw statistical quality control and the MIL-Q-9858 standard as contributing to this through acceptable quality levels—a concept that allows a certain number of acceptable defects and reinforces the attitude that mistakes are inevitable. [14] : 80 [18] : 79–80 Another contributor is the self-imposed pressure to produce something to sell, even if that thing is defective. [12] : 72–73 Workers must "make the attitude of Zero Defects [their] personal standard." [18] : 172
To convince executives to take action to resolve issues of poor quality, costs associated with poor quality must be measured in monetary terms. [19] [11] : 121 Crosby uses the term "the price of nonconformance" in preference to "the cost of quality" to overcome the misimpression that higher quality requires higher costs. [18] The point of writing Quality Is Free was to demonstrate that quality improvement efforts pay for themselves. [20] Crosby divides quality-related costs into the price of conformance and the price of nonconformance. The price of conformance includes quality-related planning, inspection, and auditing; the price of nonconformance includes scrap, rework, claims against warranty, unplanned service [11] : 209
The main criticism is the amount of effort required to verify every person's performance in an organization. [2] : 121 Confidence in the program, and therefore compliance with it, fades without this verification. [2] : 118 [21]
Point 10 of Deming's 14 points ("Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity.") is clearly aimed at ZD. [22] [23] Joseph M. Juran was also critical of ZD. [24]
Another criticism is that Zero Defects is a motivational program aimed at encouraging employees to do better. [25] [26] [27] Crosby stated that "Motivation has nothing to do with it...It is merely setting performance standards that no one can misunderstand and then starting a two-way communications exercise to let everyone know about it." [28] He blamed management actions and attitudes for creating the opportunity for defects. [29] [30]
A software bug is a design defect (bug) in computer software. A computer program with many or serious bugs may be described as buggy.
Quality control (QC) is a process by which entities review the quality of all factors involved in production. ISO 9000 defines quality control as "a part of quality management focused on fulfilling quality requirements".
Total quality management (TQM) is an organization-wide effort to "install and make a permanent climate where employees continuously improve their ability to provide on-demand products and services that customers will find of particular value." Total emphasizes that departments in addition to production are obligated to improve their operations; management emphasizes that executives are obligated to actively manage quality through funding, training, staffing, and goal setting. While there is no widely agreed-upon approach, TQM efforts typically draw heavily on the previously developed tools and techniques of quality control. TQM enjoyed widespread attention during the late 1980s and early 1990s before being overshadowed by ISO 9000, Lean manufacturing, and Six Sigma.
Six Sigma (6σ) is a set of techniques and tools for process improvement. It was introduced by American engineer Bill Smith while working at Motorola in 1986.
Quality assurance (QA) is the term used in both manufacturing and service industries to describe the systematic efforts taken to assure that the product(s) delivered to customer(s) meet with the contractual and other agreed upon performance, design, reliability, and maintainability expectations of that customer. The core purpose of Quality Assurance is to prevent mistakes and defects in the development and production of both manufactured products, such as automobiles and shoes, and delivered services, such as automotive repair and athletic shoe design. Assuring quality and therefore avoiding problems and delays when delivering products or services to customers is what ISO 9000 defines as that "part of quality management focused on providing confidence that quality requirements will be fulfilled". This defect prevention aspect of quality assurance differs from the defect detection aspect of quality control and has been referred to as a shift left since it focuses on quality efforts earlier in product development and production and on avoiding defects in the first place rather than correcting them after the fact.
PDCA or plan–do–check–act is an iterative design and management method used in business for the control and continual improvement of processes and products. It is also known as the Shewhart cycle, or the control circle/cycle. Another version of this PDCA cycle is OPDCA. The added "O" stands for observation or as some versions say: "Observe the current condition." This emphasis on observation and current condition has currency with the literature on lean manufacturing and the Toyota Production System. The PDCA cycle, with Ishikawa's changes, can be traced back to S. Mizuno of the Tokyo Institute of Technology in 1959.
In the context of software engineering, software quality refers to two related but distinct notions:
Operations management is concerned with designing and controlling the production of goods and services, ensuring that businesses are efficient in using resources to meet customer requirements.
In process improvement efforts, defects per million opportunities or DPMO is a measure of process performance. It is defined as
Robert Harris Frank is the Henrietta Johnson Louis Professor of Management Emeritus and a professor of economics at the Samuel Curtis Johnson Graduate School of Management at Cornell University. He contributes to the "Economic View" column, which appears every fifth Sunday in The New York Times. Frank has published on the topic of wealth inequality in the United States.
Software assurance (SwA) is a critical process in software development that ensures the reliability, safety, and security of software products. It involves a variety of activities, including requirements analysis, design reviews, code inspections, testing, and formal verification. One crucial component of software assurance is secure coding practices, which follow industry-accepted standards and best practices, such as those outlined by the Software Engineering Institute (SEI) in their CERT Secure Coding Standards (SCS).
Philip Bayard "Phil" Crosby, was an American businessman and author who contributed to management theory and quality management practices.
Armand Vallin Feigenbaum was an American quality control expert and businessman. He devised the concept of Total Quality Control which inspired Total Quality Management.
The Quality Management Maturity Grid (QMMG) is an organizational maturity matrix conceived by Philip B. Crosby first published in his book Quality is Free in 1979. The QMMG is used by a business or organization as a benchmark of how mature their processes are, and how well they are embedded in their culture, with respect to service or product quality management.
Joseph Moses Juran was a Romanian-born American engineer, management consultant and author. He was an advocate for quality and quality management and wrote several books on the topics. He was the brother of Academy Award winner Nathan Juran.
In business, engineering, and manufacturing, quality – or high quality – has a pragmatic interpretation as the non-inferiority or superiority of something ; it is also defined as being suitable for the intended purpose while satisfying customer expectations. Quality is a perceptual, conditional, and somewhat subjective attribute and may be understood differently by different people. Consumers may focus on the specification quality of a product/service, or how it compares to competitors in the marketplace. Producers might measure the conformance quality, or degree to which the product/service was produced correctly. Support personnel may measure quality in the degree that a product is reliable, maintainable, or sustainable. In such ways, the subjectivity of quality is rendered objective via operational definitions and measured with metrics such as proxy measures.
In process improvement efforts, quality costs tite or cost of quality is a means to quantify the total cost of quality-related efforts and deficiencies. It was first described by Armand V. Feigenbaum in a 1956 Harvard Business Review article.
Dorian Shainin was an American quality consultant, aeronautics engineer, author, and college professor most notable for his contributions in the fields of industrial problem solving, product reliability, and quality engineering, particularly the creation and development of the "Red X" concept.
This glossary of civil engineering terms is a list of definitions of terms and concepts pertaining specifically to civil engineering, its sub-disciplines, and related fields. For a more general overview of concepts within engineering as a whole, see Glossary of engineering.
Steven J. Spear is a Senior Lecturer at MIT's Sloan School of Management and Senior Fellow at the Institute for Healthcare Improvement. As a Researcher and Author, he is the recipient of the McKinsey Award and five Shingo Prizes. His book, The High Velocity Edge, won both the Shingo Prize for Excellence in Manufacturing Research and Philip Crosby Medal from the American Society for Quality (ASQ).
Early in 1964 the Assistant Secretary of Defense (Installations and Logistics) invited the attention of the Military Departments and the Defense Supply Agency to the potential of Zero Defects. This gave the program substantial impetus. Since that time Zero Defects has been adopted by numerous industrial and Department of Defense activities.
Zero Defects was the brainchild of a gifted and articulate young engineer named Philip Crosby, who conceived it while working as quality control manager on Pershing.
Whenever the subject of Zero Defects comes up, it invariably prompts the question: "Exactly how did it all start?" The fact that it did start in the defense industry on an Army-Martin missile system is testimony to the dedication of a relatively small group of people.
While Zero Defects programs might appear on the surface to be a re-hash of worker motivation programs that appeared during World War II, there is a more clearly defined methodology and technique emerging in today's programs.
It reminds me of the E (for excellence) program during World War II.
So the company turned to a propaganda approach, a peacetime equivalent of patriotic campaigns waged in defense plants during World War II.
Appraisal is an expensive and unreliable way of getting quality. Checking and sorting and evaluating only sift what is done.
The concept of prevention is based on understanding the process that needs the preventive action...The secret of prevention is to look at the process and identify opportunities for error. These can be controlled.
Prevention is the orientation for causing quality. This is opposed to the "detection" way of thinking that was used for years. Inspectors, testers, and auditors scanned the output of an operation in order to sort good from bad. It is better to create an environment in which there is no "bad," to learn how to do things right the first time. That takes prevention.
Until quality is fitted into the cash flow and displayed as an equal with the other financial considerations, it will always be an add-on.
Quality is free. It's not a gift, but it is free. ... Every penny you don't spend on doing things wrong, over, or instead becomes half a penny right on the bottom line.
A year passed, and sure enough, he showed up with a huge yellow pin emblazoned with "ZD, 2 years." He had now gone two consecutive years without making a mistake. When you don't do anything, it is easy to not make mistakes or produce faulty product.
Eliminate slogans, exhortations, and targets for the work force asking for zero defects and new levels of productivity. Such exhortations only create adversarial relationships, as the bulk of the causes of low quality and low productivity belong to the system and thus lie beyond the power of the work force.
He was scathingly critical of the fads of management that would sweep through American industry. In the 1970s, the fad was called "zero defect." They would have no defects in their product—a condition that Deming knew was completely impossible.
Some consultants proposed a sweeping solution by exhorting the workforce to make no mistakes—"Do it right the first time." This simplistic approach was persuasive to those managers, who, at the time, believed that the primary cause of their company's quality problems was the carelessness and indifference of the workforce. The facts were that the bulk of the quality problems had their origin in the managerial and technical processes. In due course this approach was abandoned, but not before a lot of divisiveness had been generated.
Unfortunately, Zero Defects was picked up by industry as a "motivation" program.
A couple of well-known leaders in the quality consulting business formed the idea years ago that I was talking about "exhorting" workers to do better. So over the years they have made that part of every speech they delivered or article they wrote. I have never responded, even though it should be fairly obvious to anyone who has ever read anything I have written or has hard me speak that I hold management responsible for the whole mess.