1. Foundations and Evolution of Quality Management SystemsIntroduction: Quality as an Organisational SystemQuality Management Systems (QMS) are structured arrangements through which an organisation directs, controls, and improves activities affecting the quality of its products, services, and processes. A QMS is more than a collection of procedures or a certificate displayed on a wall. It connects customer requirements, organisational purpose, processes, people, information, resources, measurement, and improvement. The importance of quality has expanded considerably. In early industrial production, quality was often judged by inspecting finished goods and separating acceptable items from defective ones. As production became more complex, organisations recognised that defects were frequently created by poorly designed processes, inadequate materials, unclear specifications, weak training, or ineffective management decisions. Quality therefore shifted from an activity performed at the end of production to a management responsibility embedded throughout the organisation. This chapter establishes the conceptual foundation for studying Quality Management Systems. It explains the language of quality, distinguishes quality assurance from quality control, traces the movement from inspection to Total Quality Management (TQM), and examines systems thinking. It also considers the contributions of W. Edwards Deming, Joseph M. Juran, Philip B. Crosby, Armand V. Feigenbaum, Kaoru Ishikawa, and Genichi Taguchi. Their ideas remain influential because they address different but complementary dimensions of quality: variation, management responsibility, planning, prevention, organisational participation, customer needs, and robust design. Learning ObjectivesAfter studying this chapter, the learner should be able to: 1. Define quality and explain major quality-related terminology. 2. Distinguish inspection, quality control, quality assurance, quality management, and TQM. 3. Explain the historical evolution of quality thinking. 4. Apply systems theory to the design and evaluation of a QMS. 5. Compare the principal contributions of Deming, Juran, Crosby, Feigenbaum, Ishikawa, and Taguchi. 6. Interpret the managerial and professional implications of prevention, process control, customer focus, and continual improvement. 7. Identify common weaknesses, ethical risks, and implementation challenges in quality systems. 8. Apply foundational quality concepts to an organisational case. The Language of QualityQualityQuality is commonly understood as the degree to which a product, service, process, or system fulfils stated, implied, or obligatory requirements. This definition is deliberately broader than conformance to a technical specification. A product may conform to its design specification and still fail to meet customer expectations if the specification itself is incomplete or inappropriate. Quality has at least two interconnected dimensions. The first is conformance quality, meaning consistency with requirements, standards, or specifications. The second is design quality, meaning the extent to which the design itself reflects customer needs and intended use. For example, a medical device may be manufactured exactly as designed but remain poor in quality if the design is difficult to use safely. Quality is also contextual. A level of performance suitable for a budget service may be unsuitable for aviation, healthcare, or nuclear operations. Consequently, quality decisions must consider users, risks, legal requirements, performance expectations, accessibility, reliability, and lifecycle consequences. Customer and Interested PartyThe customer is the recipient of a product or service. Customers may be external, such as buyers and users, or internal, such as departments receiving work from another department. A QMS must also consider interested parties: persons or groups that can affect, be affected by, or perceive themselves to be affected by organisational decisions. These may include regulators, employees, owners, suppliers, communities, and professional bodies. Customer focus does not mean accepting every demand without analysis. It means understanding relevant needs, translating them into requirements, fulfilling them consistently, and learning from feedback. In regulated sectors, legal and safety requirements may take priority over preferences expressed by an individual customer. Requirement, Specification, and ConformityA requirement is a need or expectation that is stated, generally implied, or obligatory. A specification is a precise description of characteristics, dimensions, performance criteria, materials, or methods. Conformity means fulfilment of a requirement, while nonconformity means failure to fulfil one. Nonconformity is not always synonymous with product failure. A missing approval signature, an expired calibration record, or an unapproved change in a process may constitute a system nonconformity even if the final product appears satisfactory. This distinction is important because quality management addresses both outcomes and the integrity of the processes that produce them. Defect, Error, Variation, and RiskA defect is a failure to meet a requirement associated with an intended or specified use. An error is an incorrect action, decision, entry, or result. Variation refers to differences among outcomes of a process. Variation may be caused by routine factors inherent in the process, called common causes, or by identifiable and unusual factors, called special causes. Risk is the effect of uncertainty on objectives. In quality management, risk may involve product failure, patient harm, regulatory violation, customer dissatisfaction, data loss, or interruption of operations. A mature QMS does not wait for a defect to occur; it identifies potential failures and controls their likelihood or impact. Effectiveness, Efficiency, and ImprovementEffectiveness concerns whether planned results are achieved. Efficiency concerns the relationship between results and resources used. A process can be effective but inefficient if it achieves requirements through excessive labour, rework, or delay. It can also be efficient but ineffective if it produces outputs quickly that do not satisfy customer or regulatory needs. Continual improvement is the recurring activity of enhancing performance. It may involve incremental changes, breakthrough innovation, redesign, corrective action, or learning from experience. Improvement should be based on evidence rather than on untested enthusiasm. From Inspection to Total Quality ManagementThe Inspection EraIn craft production, the producer often controlled the entire activity and personally judged the work. Industrial mass production separated design, production, and inspection. Inspection became a specialised function intended to identify defective products before delivery. Inspection provides information and can protect customers from receiving visibly defective goods. However, it is fundamentally reactive. It does not, by itself, explain why defects occurred or prevent recurrence. It also creates the possibility that defects are discovered only after significant material, labour, and time have been invested. In destructive testing, inspection may even consume the item being tested. Statistical Quality ControlDuring the twentieth century, statistical methods introduced a more analytical approach. Walter A. Shewhart distinguished between common-cause and special-cause variation and developed the control chart as a means of studying process stability. Statistical quality control shifted attention from merely sorting outputs to understanding process behaviour. A stable process is not necessarily a capable process. Stability means that variation is predictable within the process, whereas capability means that the stable process can meet specified limits. This distinction remains central to process improvement and performance measurement. Quality AssuranceQuality assurance developed as a planned and systematic approach intended to provide confidence that quality requirements will be fulfilled. It includes documented methods, competence requirements, design reviews, supplier controls, audits, validation, calibration, and process monitoring. Quality assurance is preventive and system-oriented. The phrase “assurance” should not be interpreted as an absolute guarantee. Assurance is credible only when supported by suitable evidence. A procedure that is never followed, an audit that ignores important risks, or a certificate obtained without genuine implementation provides little assurance. Quality ControlQuality control comprises operational techniques and activities used to fulfil quality requirements. It includes inspection, testing, measurement, sampling, process monitoring, acceptance decisions, and corrective responses. Quality control is often associated with detecting and controlling nonconforming outputs, although modern quality control also includes process-based prevention. Quality assurance and quality control are complementary. Assurance asks whether the system is designed and operated to produce quality consistently. Control asks whether requirements are being met in particular outputs or processes. A testing department cannot compensate for poor design, unclear requirements, or inadequate management. Conversely, a well-designed system still requires measurement and control to verify actual performance. Quality Management and TQMQuality management refers to coordinated activities for directing and controlling an organisation with regard to quality. It includes quality planning, quality assurance, quality control, and quality improvement. Total Quality Management is a broad management philosophy and organisational approach in which quality is treated as the responsibility of everyone and is pursued through customer focus, process management, employee involvement, evidence-based decisions, leadership commitment, and continual improvement. “Total” refers to the scope of involvement: all functions, levels, processes, suppliers, and customer relationships may affect quality. TQM is not simply a motivational programme or a set of statistical tools. It requires alignment between strategy, structure, culture, technology, leadership, and measurement. A company cannot credibly claim TQM while rewarding departments solely for local output, concealing defects, or treating quality staff as the only owners of quality. Quality Management Through a Systems LensSystems theory provides a powerful way to understand a QMS. A system is a set of interrelated elements that function as a whole. Organisations are open systems: they receive inputs from their environment, transform those inputs through interconnected processes, produce outputs, and receive feedback. A simplified quality system can be represented as: Inputs → Processes → Outputs → Feedback and learning Inputs include customer requirements, materials, information, equipment, competence, infrastructure, and legal obligations. Processes transform inputs into products or services. Outputs include delivered products, customer experiences, waste, information, and unintended consequences. Feedback comes from complaints, audits, performance data, market information, employee observations, and regulatory findings. Systems thinking discourages isolated fixes. If a hospital experiences medication errors, blaming individual nurses without examining prescribing systems, workload, labelling, information technology, communication, and training may leave the underlying causes untouched. Similarly, reducing inspection staff may appear efficient but may shift costs to rework, complaints, warranty claims, and reputational damage. A QMS can be understood through several system principles: - Interdependence: Changes in one process may affect others.
- Purpose: Processes should be connected to organisational and customer objectives.
- Boundaries: The organisation must determine which internal and external processes are relevant to quality.
- Feedback: Performance information must lead to learning or corrective action.
- Emergence: Overall performance can differ from the apparent performance of individual departments.
- Adaptation: The system must respond to changing technology, risks, customer needs, and regulation.
The process approach translates systems thinking into management practice. Each process should have defined inputs, outputs, owners, resources, controls, measures, risks, and interfaces with other processes. Process mapping can reveal handoff failures, duplicated work, unclear authority, and points at which errors become difficult or expensive to correct. The Architects of Modern Quality ThinkingW. Edwards Deming: Variation and Management ResponsibilityDeming emphasised that most quality problems are rooted in the system of work rather than in individual carelessness. Management designs the system, establishes targets, allocates resources, selects suppliers, and creates the conditions in which people work. His teaching encouraged organisations to understand variation, reduce fear, improve processes, and pursue long-term purpose. Deming’s well-known system of profound knowledge includes appreciation for: 1. A system and its interrelationships. 2. Variation and statistical thinking. 3. Theory of knowledge, including how learning is established. 4. Psychology and human motivation. Deming’s Plan-Do-Study-Act cycle expresses improvement as a learning process. An organisation plans a change, implements it, studies evidence from the results, and acts by adopting, adapting, or abandoning the change. Deming opposed reliance on slogans, numerical quotas, and mass inspection as substitutes for better systems. A managerial implication of Deming’s work is that performance targets must be interpreted carefully. Pressuring employees to meet a numerical target may produce gaming, concealment, or undesirable trade-offs if the measure does not represent the true objective. Joseph M. Juran: Planning, Control, and ImprovementJuran described quality as fitness for use. This formulation places emphasis on whether a product or service is suitable for the customer’s actual purpose, not merely whether it meets internal specifications. His quality trilogy consists of: - Quality planning: Identify customers, discover their needs, translate those needs into product and process features, and design processes capable of delivering them.
- Quality control: Evaluate actual performance, compare it with goals, and act on differences.
- Quality improvement: Organise projects to eliminate chronic problems and achieve superior levels of performance.
Juran distinguished between sporadic problems, which create sudden deviations, and chronic problems, which are built into the existing system. Management attention is often captured by sporadic crises, while substantial gains may require systematic work on chronic waste, delay, and failure. Philip B. Crosby: Conformance and PreventionCrosby defined quality as conformance to requirements and argued that quality is free in the sense that the investment in prevention is generally preferable to the costs generated by nonconformance. His approach stressed “zero defects” as a performance standard and promoted the idea of doing work correctly the first time. Zero defects should not be misunderstood as a claim that human beings will never make mistakes. It is a managerial aspiration that rejects the assumption that defects are an unavoidable and acceptable feature of work. Crosby’s framework highlighted management commitment, education, prevention, measurement of quality, and the cost of nonconformance. A limitation of applying Crosby mechanically is that an organisation may focus narrowly on conformance to existing requirements and neglect whether the requirements remain appropriate. Prevention therefore must be combined with customer learning and design improvement. Armand V. Feigenbaum: Total Quality ControlFeigenbaum developed the concept of Total Quality Control, asserting that quality is not confined to manufacturing or to a quality department. It begins with customer requirements and extends through design, purchasing, production, installation, service, and after-sales support. His work drew attention to the “hidden plant”: the capacity consumed by rework, sorting, correction, complaint handling, and other activities caused by failure. This idea helped establish quality as an economic and strategic concern. Quality costs are commonly considered under prevention, appraisal, internal failure, and external failure categories. The objective is not simply to maximise inspection or minimise prevention spending, but to optimise the total cost and risk of achieving quality. Kaoru Ishikawa: Participation and Root-Cause AnalysisIshikawa made quality accessible to employees through practical tools and participative methods. He promoted quality circles, in which small groups systematically identify and solve work-related problems. He also popularised the cause-and-effect, or fishbone, diagram, which organises possible causes under categories such as people, methods, machines, materials, measurement, and environment. Ishikawa’s approach reflects the belief that employees close to a process possess valuable knowledge about its difficulties and improvement opportunities. Participation, however, must be genuine. Asking employees to identify problems while denying them authority, time, information, or resources can create frustration rather than improvement. Genichi Taguchi: Robust Design and LossTaguchi extended quality thinking upstream into product and process design. His robust design philosophy seeks performance that is relatively insensitive to sources of variation, often called noise factors. Instead of relying solely on final inspection, engineers design products and processes that continue to perform under realistic conditions. Taguchi also proposed that deviation from a target creates loss to society, even when the output remains within specification limits. This challenges the assumption that all values inside tolerance are equally good. His methods include designed experiments and signal-to-noise concepts for evaluating designs under varying conditions. The practical significance is substantial: design decisions can reduce future defects, maintenance, warranty costs, and customer inconvenience. Taguchi’s work also encourages organisations to distinguish between controlling a process after design and improving the design so that control becomes easier. Applying the Ideas in OrganisationsA QMS should translate quality principles into a coherent management architecture. This commonly involves defining quality policy and objectives, identifying processes, assigning responsibilities, controlling documented information, managing suppliers, ensuring competence, monitoring performance, addressing nonconformities, conducting audits, and implementing improvement. In manufacturing, these practices may include process capability studies, preventive maintenance, measurement-system analysis, supplier development, and statistical process control. In healthcare, they may involve patient identification, medication reconciliation, infection prevention, clinical audits, incident learning, and safe handoffs. In software and digital services, quality may involve requirements traceability, code review, automated testing, cybersecurity controls, usability evaluation, release governance, and monitoring after deployment. Quality objectives should be meaningful and balanced. Measures such as defect rate, first-pass yield, complaint frequency, on-time delivery, service availability, turnaround time, and customer effort can provide useful evidence. However, metrics may distort behaviour when they are treated as ends in themselves. A call centre that measures only average handling time may encourage premature termination of calls and reduce actual service quality. Corrective action should address causes rather than merely symptoms. A disciplined approach asks what happened, how it happened, why existing controls failed, whether similar risks exist elsewhere, and how effectiveness will be verified. Root-cause tools can support investigation, but no tool replaces sound judgement and accurate evidence. Illustrative Case: Improving Quality in a Diagnostic LaboratoryBackgroundThe following is a fictional illustrative case. Meridian Diagnostics is a regional laboratory processing hospital and outpatient samples. It has a reputation for technical competence, but physicians have reported delayed results and occasional requests for repeat samples. Situation and ProblemAn internal review found that the laboratory’s overall analytical accuracy was acceptable, but 7 percent of samples required clarification or recollection. Problems included incomplete request forms, mislabelled tubes, unsuitable transport temperatures, and delays during shift changes. Each department had attempted local fixes, but performance remained unstable. AnalysisThe laboratory initially treated the matter as an inspection problem by adding a final administrative check. This reduced some errors but increased turnaround time. A cross-functional team mapped the complete process from patient identification to result communication. The map showed that most failures occurred before analysis, especially at the interfaces among clinical wards, transport staff, reception, and the laboratory. Using a cause-and-effect diagram, the team identified multiple contributors: inconsistent specimen labels, different ward procedures, unclear responsibility for rejected samples, inadequate transport containers, incomplete training for temporary staff, and a computer system that permitted incomplete entries. The team also separated common causes from special causes. A single damaged transport box was a special cause; inconsistent labelling practices were a chronic system cause. Approach and SolutionThe laboratory adopted a systems-based improvement plan. It standardised labels and collection instructions, introduced barcode verification, established temperature monitoring for sensitive specimens, clarified ownership at each handoff, and redesigned the electronic request form to prevent submission of missing information. Staff from the wards and transport service participated in testing the changes. The team used a Plan-Do-Study-Act cycle. It piloted the new process in one ward, studied rejection and turnaround data, collected staff feedback, and modified the barcode workflow before extending it. Audits were used not merely to find blame but to verify whether the redesigned process was being followed and whether results were improving. OutcomeAfter implementation, specimen rejection declined substantially, and turnaround-time variation narrowed. The improvement did not result from adding a larger inspection workforce. It resulted from better design, clearer interfaces, employee involvement, preventive controls, and measurement of the whole process. Learning PointsThe case illustrates Deming’s concern with systems and variation, Juran’s distinction between control and improvement, Crosby’s emphasis on prevention, Feigenbaum’s cross-functional view, Ishikawa’s participative analysis, and Taguchi’s interest in designing processes that are robust to variation. It also demonstrates that quality ownership crosses organisational boundaries. Challenges, Risks, and Professional ResponsibilitiesQuality systems can fail through bureaucracy. Excessive documentation may consume time without improving control, while insufficient documentation may create ambiguity and prevent learning. The appropriate question is not how many forms exist, but whether information is available, reliable, accessible, and used for decisions. A second risk is certification-oriented behaviour. An organisation may prepare for an audit by temporarily correcting records or training employees to repeat approved answers. Such behaviour undermines the purpose of assurance and can conceal operational risk. Audits should be independent, evidence-based, proportionate to risk, and followed by effective action. A third risk is the misuse of performance data. Data can be incomplete, biased, poorly defined, or manipulated. Quality professionals must understand measurement validity, sampling limitations, denominator definitions, and the difference between correlation and causation. Confidentiality and privacy are especially important when quality data contain patient, employee, or customer information. Ethically, quality management requires truthful reporting of defects and near misses, respect for affected persons, protection from retaliation, and fair allocation of responsibility. Blame may be appropriate when there is deliberate misconduct, but honest reporting of system weaknesses should not be punished. Leaders have a duty to prevent unsafe pressure, conflicts of interest, falsification, and concealment of nonconformity. Technology can strengthen QMS performance through electronic document control, workflow automation, dashboards, traceability systems, statistical monitoring, sensors, and artificial intelligence. AI may help detect patterns in complaints, predict equipment failures, classify nonconformities, or identify unusual process behaviour. Nevertheless, algorithmic outputs require validation, human oversight, data-quality controls, cybersecurity, explainability where decisions affect people, and protection against automation bias. Digital tools should support quality thinking, not replace professional judgement. Current Developments and Best PracticesContemporary QMS practice increasingly combines risk-based thinking, process management, customer experience, sustainability, resilience, and data-driven improvement. Organisations are examining quality across supply networks rather than only within legal organisational boundaries. Climate-related disruption, geopolitical uncertainty, cyber threats, and dependence on critical suppliers have made continuity and resilience part of quality governance. Effective practice commonly includes the following: - Leadership that connects quality with strategy, ethics, and resource decisions.
- Clear process ownership and well-managed interfaces.
- Prevention and risk reduction before final inspection.
- Reliable measures linked to meaningful objectives.
- Employee competence, participation, and psychological safety.
- Supplier collaboration based on capability and risk, not price alone.
- Audits that generate learning rather than ceremonial compliance.
- Corrective actions whose effectiveness is verified.
- Design reviews that consider usability, safety, reliability, and lifecycle impact.
- Continual improvement supported by disciplined experimentation.
The central lesson is that quality is created by an interconnected system. Inspection remains useful, but it is not a substitute for capable processes. Standards provide structure, but they do not replace leadership. Tools support analysis, but they do not replace understanding. A QMS becomes valuable when it enables an organisation to fulfil requirements consistently, learn from evidence, prevent harm, and improve the value delivered to customers and society. Chapter SummaryQuality is the ability of a product, service, process, or system to fulfil relevant requirements and satisfy intended use. Important concepts include conformity, nonconformity, defect, variation, risk, effectiveness, efficiency, and continual improvement. Inspection detects problems after production; quality control manages operational conformity; quality assurance provides confidence through planned and systematic practices; and quality management integrates planning, assurance, control, and improvement. The historical movement from inspection to statistical quality control and then to TQM reflects a shift from detecting defective outputs to designing capable processes and managing quality across the organisation. Systems theory explains why quality cannot be assigned to a single department: inputs, processes, outputs, feedback, people, suppliers, and customers are interdependent. Deming emphasised systems, variation, learning, and management responsibility. Juran contributed the quality trilogy of planning, control, and improvement. Crosby stressed conformance, prevention, and the cost of nonconformance. Feigenbaum presented quality as a total organisational responsibility. Ishikawa advanced participation and root-cause analysis. Taguchi moved attention toward robust design and the loss caused by deviation from target. Together, these contributions provide a foundation for designing QMSs that are preventive, customer-focused, evidence-based, ethical, and continuously improving. Key TermsQuality: The degree to which characteristics fulfil stated, implied, or obligatory requirements. Conformance: Fulfilment of a specified requirement. Nonconformity: Failure to fulfil a requirement. Defect: Failure related to an intended or specified use. Customer: Recipient of a product or service, internal or external. Interested party: Person or group that can affect, be affected by, or perceive itself affected by an organisation’s decisions. Quality control: Operational techniques and activities used to fulfil quality requirements. Quality assurance: Planned and systematic activities that provide confidence that requirements will be fulfilled. Quality management: Coordinated activities for directing and controlling an organisation regarding quality. Total Quality Management: Organisation-wide management philosophy based on customer focus, participation, process management, and continual improvement. Variation: Differences in process or product outcomes. Common cause: A routine source of variation inherent in a process. Special cause: An identifiable, unusual source of variation. Risk: The effect of uncertainty on objectives. Process capability: The ability of a stable process to meet specified requirements. Continual improvement: Recurring activity to enhance performance. Quality planning: Establishing quality objectives and processes needed to achieve them. Root cause: An underlying cause whose removal prevents recurrence of a problem. Robust design: Designing products or processes to perform consistently despite sources of variation. Cost of nonconformance: Costs arising because requirements are not fulfilled, including rework, complaints, and failures. Review QuestionsShort Answer Questions1. Distinguish between conformance quality and design quality. 2. What is the difference between quality assurance and quality control? 3. Explain the distinction between common-cause and special-cause variation. 4. What does the process approach contribute to a Quality Management System? 5. State the main elements of Juran’s quality trilogy. Long Answer Questions1. Trace the evolution from inspection to Total Quality Management and explain the managerial significance of this transition. 2. Discuss systems theory and show how it changes the way organisations investigate quality problems. 3. Compare the contributions of Deming, Juran, Crosby, Feigenbaum, Ishikawa, and Taguchi. 4. Explain why prevention is generally more valuable than reliance on final inspection. 5. Discuss the role of leadership, employee participation, measurement, and ethics in an effective QMS. Analytical / Application Questions1. A company has reduced its inspection department and observed an increase in complaints. Analyse why the change may have failed using the distinction between quality control, quality assurance, and systems thinking. 2. A call centre meets its average handling-time target but receives increasing complaints about unresolved issues. Diagnose the weakness in its measurement system and recommend a balanced quality approach. 3. A hospital experiences repeated specimen-identification errors despite retraining staff after each incident. Use the ideas of variation, root-cause analysis, prevention, and robust design to propose a more effective intervention. 22. Multiple Choice Questions with AnswersQuestion 1Which statement best distinguishes quality assurance from quality control? A. Quality assurance focuses only on final inspection, whereas quality control focuses on employee training. B. Quality assurance provides confidence through planned systems, whereas quality control uses operational activities to fulfil requirements. C. Quality assurance is concerned with costs, whereas quality control is concerned only with customers. D. Quality assurance applies only to manufacturing, whereas quality control applies only to services. Correct Answer: B. Quality assurance provides confidence through planned systems, whereas quality control uses operational activities to fulfil requirements. Question 2A process produces outputs within specification limits, but its average performance is consistently close to the upper limit. Which quality concern is most relevant? A. The process may be stable but have inadequate capability or poor centring. B. The process necessarily has only special-cause variation. C. Inspection has eliminated the need for process improvement. D. The process is automatically robust because all outputs conform. Correct Answer: A. The process may be stable but have inadequate capability or poor centring. Question 3Which situation best illustrates systems thinking in quality management? A. Blaming an employee immediately after a data-entry error. B. Increasing final inspection without examining upstream activities. C. Studying the interaction of software, workload, training, procedures, and handoffs after repeated errors. D. Measuring only the performance of the department where a defect was discovered. Correct Answer: C. Studying the interaction of software, workload, training, procedures, and handoffs after repeated errors. Question 4Juran’s quality trilogy consists of: A. Inspection, certification, and benchmarking. B. Planning, control, and improvement. C. Leadership, motivation, and automation. D. Design, production, and distribution. Correct Answer: B. Planning, control, and improvement. Question 5Crosby’s emphasis on zero defects is best interpreted as: A. A claim that human error can be completely eliminated in every circumstance. B. A rejection of prevention because inspection is more reliable. C. A managerial aspiration to prevent defects rather than accept them as unavoidable. D. A requirement that every process use statistical control charts. Correct Answer: C. A managerial aspiration to prevent defects rather than accept them as unavoidable. Question 6Which contribution is most closely associated with Taguchi? A. Quality circles and fishbone diagrams. B. The quality trilogy. C. Robust design and loss from deviation from target. D. The system of profound knowledge. Correct Answer: C. Robust design and loss from deviation from target. Question 7A company meets its internal specification but customers find the product difficult to use. Which concept best explains the problem? A. The product has conformance quality but inadequate design quality or fitness for use. B. The product has special-cause variation only. C. The product demonstrates effective quality assurance. D. The product has zero cost of nonconformance. Correct Answer: A. The product has conformance quality but inadequate design quality or fitness for use. Question 8Which action is most consistent with Feigenbaum’s view of total quality control? A. Assigning all quality responsibility to the inspection department. B. Managing quality across design, purchasing, production, service, and customer support. C. Replacing supplier evaluation with final product testing. D. Treating quality as separate from organisational strategy. Correct Answer: B. Managing quality across design, purchasing, production, service, and customer support. Question 9A laboratory adds a final document check, but errors continue because forms are incomplete at the point of collection. What is the strongest improvement response? A. Add more final inspectors indefinitely. B. Punish the last employee who handled each form. C. Redesign the upstream process, clarify responsibilities, and introduce preventive controls. D. Stop measuring errors because measurement increases reported problems. Correct Answer: C. Redesign the upstream process, clarify responsibilities, and introduce preventive controls. Question 10Why can a performance target produce undesirable behaviour? A. All targets are inherently invalid. B. Employees may optimise the measured indicator rather than the underlying quality objective. C. Targets prevent organisations from using any feedback. D. Numerical measures cannot be used in quality management. Correct Answer: B. Employees may optimise the measured indicator rather than the underlying quality objective.
|
