14. Ethics, Governance and Sustainable Quality

Introduction and Context

Total Quality Management is often presented as a system for improving processes, reducing variation, satisfying customers, and strengthening organizational performance. Yet quality decisions are never purely technical. A decision to release a product, accept a supplier, classify a defect, use customer data, close an audit finding, or reduce inspection may affect safety, rights, livelihoods, the environment, and public trust. Consequently, operational excellence that ignores ethics and governance can produce efficient but harmful outcomes.

Ethics concerns the principles used to judge what ought to be done. Governance concerns the structures, authority, controls, and accountability through which decisions are directed and monitored. Sustainable quality extends the meaning of quality beyond immediate conformance and customer satisfaction. It asks whether value is created responsibly, consistently, safely, inclusively, and without transferring unacceptable costs to future generations or other stakeholders.

For quality professionals, this changes the central question from “Did the process meet specification?” to “Did the organization achieve a reliable and beneficial outcome through a fair, lawful, transparent, and sustainable process?” This chapter examines how ethical decision-making, regulatory compliance, independent assurance, privacy, fairness, safety, accountability, and environmental, social, and governance (ESG) principles can be integrated into quality projects and continuous improvement systems.

Learning Objectives

After studying this chapter, students should be able to:

1. Explain the relationship between ethics, governance, compliance, quality, and sustainability.

2. Apply ethical decision-making methods to quality and operational problems.

3. Design controls for audit independence, privacy, fairness, safety, and accountability.

4. Integrate ESG considerations into improvement projects and quality metrics.

5. Evaluate governance risks, ethical trade-offs, and unintended consequences.

6. Recommend responsible practices for data-enabled and AI-supported quality management.

Quality as a Moral and Governance Responsibility

Traditional quality management emphasizes conformance to requirements. This remains essential, but requirements may be incomplete, misleading, or legally insufficient. A product can conform to a narrow specification and still be unsafe for vulnerable users. A service can meet its average response-time target while systematically disadvantaging a particular group. A factory can achieve productivity gains while concealing unsafe working conditions or transferring pollution to nearby communities.

Ethical quality therefore has at least four dimensions. First is technical integrity: measurements, records, tests, and reports must be accurate. Second is human protection: products, services, and processes should not expose stakeholders to avoidable harm. Third is fair treatment: decisions should not discriminate without legitimate justification. Fourth is stewardship: organizational performance should account for social and environmental consequences.

Governance gives these principles practical force. A governance system clarifies who may make decisions, what evidence is required, how conflicts are managed, how exceptions are approved, and how misconduct is reported. Without governance, ethical conduct depends excessively on individual courage. With effective governance, responsible behavior is embedded in roles, processes, information systems, and leadership routines.

A useful distinction is that compliance is a floor, not the ceiling, of quality. Compliance means meeting applicable laws, regulations, standards, contracts, and internal rules. Ethical quality may require action beyond minimum legal requirements, particularly when regulations lag behind technology or when foreseeable harm is not explicitly prohibited. Conversely, ethical intentions do not excuse non-compliance. Both dimensions are necessary.

Core Concepts and Terminology

Stakeholders and the quality relationship

A stakeholder is any person or group that can affect, be affected by, or reasonably perceive itself to be affected by an organizational decision. Customers, employees, suppliers, regulators, owners, communities, and future generations may have different interests. A quality project should identify these interests rather than treating the paying customer as the only legitimate recipient of value.

Stakeholder analysis commonly considers power, legitimacy, urgency, vulnerability, and the extent of potential harm. Vulnerable stakeholders may have little power but a strong moral claim to protection. For example, patients, children, low-income consumers, migrant workers, and communities near industrial facilities may require special attention.

Integrity and transparency

Integrity means consistency between stated principles and actual conduct. It includes truthful reporting, accurate records, disclosure of conflicts of interest, and refusal to manipulate performance indicators. Transparency does not mean publishing every piece of information; it means providing relevant, understandable, and timely information to those entitled to receive it.

Accountability and responsibility

Responsibility refers to the duty to perform an assigned role properly. Accountability is the obligation to explain decisions, accept scrutiny, and face appropriate consequences. A quality system that assigns responsibility but does not establish accountability may produce “orphan risks,” where everyone assumes that someone else is monitoring the issue.

Due care and precaution

Due care requires reasonable attention to foreseeable risks. The precautionary principle supports protective action where potential harm may be serious even if scientific certainty is incomplete. In quality projects, this may justify additional testing, restricted release, or temporary suspension while evidence is developed.

Materiality and proportionality

Materiality concerns whether information or an event could influence stakeholder decisions. Proportionality requires controls and responses to match the significance and likelihood of risk. A minor documentation error and a patient-safety failure should not receive identical investigation, approval, or escalation.

Ethical Decision-Making in Quality Projects

Ethical dilemmas arise when legitimate objectives conflict. A manager may face pressure to meet a launch date while test evidence remains incomplete. A procurement team may choose a low-cost supplier despite credible concerns about labor practices. An analyst may be asked to remove inconvenient observations from a dashboard. These situations cannot be resolved by technical optimization alone.

A practical ethical decision process consists of the following stages:

1. Clarify the decision. State what must be decided, by whom, and within what time frame.

2. Identify stakeholders and possible harms. Include indirect and vulnerable stakeholders, not only those represented in the meeting.

3. Establish facts and uncertainties. Separate verified evidence from assumptions, estimates, and pressure-driven interpretations.

4. Identify duties and constraints. Consider law, regulation, professional codes, contracts, policies, safety obligations, and promises made to stakeholders.

5. Generate alternatives. Avoid framing the choice as only “proceed” or “stop.” Consider staged release, additional controls, redesign, independent review, or transparent delay.

6. Test alternatives against ethical principles. Examine consequences, rights, fairness, care, and organizational character.

7. Decide and document. Record the evidence, rationale, dissenting views, approvals, and conditions.

8. Monitor consequences. Ethical responsibility continues after implementation. Unexpected harm requires correction and disclosure.

Several ethical lenses are useful. A consequentialist approach asks which alternative produces the best overall outcomes and minimizes harm. A rights-based approach asks whether the decision respects privacy, dignity, consent, and freedom from unjustified harm. A justice-based approach examines distribution: who receives benefits, who bears risks, and whether comparable cases are treated consistently. A duty-based approach emphasizes obligations that should not be violated even for attractive results. A virtue-based approach asks what a person or organization characterized by honesty, courage, prudence, and fairness would do.

No single lens is sufficient in every case. A cost-saving proposal may look favorable in aggregate but fail a rights-based test if it exposes a small group to unacceptable danger. A rigid application of a rule may also produce injustice in exceptional circumstances. Senior quality professionals should make the reasoning explicit and seek review when values conflict.

Governance Architecture for Sustainable Quality

Governance should connect strategic intent with operational control. At board or executive level, leaders establish purpose, risk appetite, ethical expectations, and accountability. At the process level, managers translate these into procedures, competence requirements, performance indicators, and escalation rules. At the operational level, employees collect evidence, control processes, report deviations, and act on risks.

A robust quality-governance architecture generally includes:

• a clearly approved quality and ethics policy;
• defined decision rights and segregation of incompatible duties;
• risk-based controls and documented acceptance criteria;
• reliable records and traceable change control;
• independent assurance through internal audit or review;
• protected channels for concerns and whistleblowing;
• timely corrective and preventive action;
• leadership review of adverse trends, not only favorable results; and
• stakeholder reporting that is accurate and understandable.

The “three lines” concept is useful. The first line consists of operational owners who identify and control risks. The second line includes risk, compliance, privacy, safety, or quality functions that develop methods and challenge performance. The third line is internal audit or an equivalent independent assurance function. These lines should cooperate but retain distinct responsibilities.

Governance fails when targets reward concealment, when escalation is punished, when audit findings are negotiated into insignificance, or when senior people are exempted from controls. A mature system treats bad news as information needed for learning rather than as disloyalty.

Regulatory Compliance and Audit Independence

Compliance management begins with identifying applicable obligations. These may include product-safety rules, sector regulations, environmental permits, labor requirements, data-protection laws, accessibility obligations, contractual commitments, and professional standards. A compliance register should identify each obligation, its owner, evidence of conformity, review frequency, and consequences of non-compliance.

Compliance should be integrated with operational risk management rather than maintained as a static legal list. A change in product design, supplier, software, data collection, or production location can alter the organization’s obligations. Regulatory interpretation should be documented, particularly where requirements are ambiguous.

Audit independence is essential to credible assurance. Auditors should be free from inappropriate influence and should not audit work for which they had direct operational responsibility. Independence is supported by objective appointment, access to relevant records, unrestricted communication with senior oversight, rotation where appropriate, and protection from retaliation. Impartiality also requires professional competence and freedom from conflicts of interest.

Independence does not mean ignorance of the business. An effective auditor understands the process while maintaining sufficient distance to evaluate it critically. Auditors should distinguish evidence from opinion, report significant limitations, preserve working papers, and avoid promising a favorable result. Management owns the process and corrective action; auditors evaluate and communicate assurance.

A common failure is “audit capture,” in which the auditor becomes dependent on the audited unit for status, rewards, or future work. Another is checklist compliance, where documentation is complete but actual practice is weak. Risk-based audits should therefore combine document review, interviews, observation, sampling, data analysis, and verification of corrective-action effectiveness.

Privacy, Data Governance, and Fairness

Quality improvement increasingly depends on customer, employee, machine, and service data. Data can reveal defects and improve prediction, but its use creates obligations concerning purpose, consent, minimization, security, accuracy, retention, access, and rights of individuals. Organizations should collect only data that is necessary for a legitimate purpose, define who may use it, protect it against unauthorized access, and delete or anonymize it when retention is no longer justified.

Privacy is not merely an information-technology issue. A quality team that links complaint records with demographic data may unintentionally identify individuals or enable discriminatory decisions. Data governance should include classification, access controls, encryption where appropriate, audit trails, retention schedules, breach response, and clear ownership.

Fairness requires examination of both outcomes and processes. A model or procedure may appear neutral while producing systematically worse results for a group. Fairness analysis should consider data quality, representation, proxy variables, error rates, accessibility, and the justification for different treatment. Where automated decisions affect employment, credit, healthcare, insurance, safety, or essential services, human review and appeal mechanisms are particularly important.

The relevant principle is not that every group must receive identical outcomes in every circumstance. Rather, differences should be relevant, proportionate, evidence-based, and open to review. Quality indicators should therefore be disaggregated where lawful and meaningful, rather than relying solely on averages that conceal disparity.

Product, Service, and Process Safety

Safety is a defining dimension of responsible quality. Safety management should identify hazards, estimate risk, implement controls, verify effectiveness, and learn from incidents and near misses. A useful hierarchy of controls prioritizes elimination of the hazard, substitution, engineering controls, administrative controls, and personal protective equipment. Controls that depend entirely on human memory are generally less robust than controls designed into the process.

Product and service safety also involves communication. Instructions, warnings, labeling, training, accessibility, and post-market monitoring must be appropriate for the intended user. An organization should not assume that a technically correct instruction is sufficient if users are unlikely to understand or follow it.

When a serious defect is identified, the organization must have a defined escalation and response process. This may involve containment, traceability, technical investigation, regulatory notification, customer communication, recall, remediation, and independent review. Delaying disclosure to protect reputation can increase harm and liability. Safety culture is demonstrated most clearly when leaders accept short-term cost to prevent foreseeable harm.

ESG and Sustainable Quality

ESG provides a broad framework for considering environmental, social, and governance performance. It should not be treated as a communications label detached from operational quality. Environmental factors may include energy use, emissions, water, waste, hazardous materials, biodiversity, and product life-cycle impacts. Social factors may include occupational health, human rights, diversity, inclusion, customer welfare, community effects, and responsible supply chains. Governance factors include board oversight, ethics, anti-corruption, controls, transparency, and accountability.

Sustainable quality integrates these concerns into process design and improvement. For example, reducing material waste may lower cost and environmental impact, but replacing a material may create safety or durability problems. A supplier consolidation project may improve consistency while increasing dependency and resilience risk. A digital service may reduce paper use but increase energy consumption and exclude users with limited digital access. Sustainable decision-making therefore evaluates trade-offs across the life cycle rather than optimizing a single local metric.

Life-cycle thinking considers raw materials, design, production, distribution, use, maintenance, and end-of-life. Quality teams can support sustainability through design for repair, durability, reuse, recycling, resource efficiency, safe chemistry, supplier assessment, and reliable sustainability data. Claims should be supported by evidence; unsupported environmental claims create reputational and legal risk.

A balanced scorecard for a quality project may include customer outcomes, process capability, employee safety, compliance, emissions or resource intensity, supplier conduct, and equity indicators. Metrics should have defined boundaries, data sources, owners, and controls. Measuring only what is convenient invites gaming and creates blind spots.

Applying the Principles in Continuous Improvement

A conventional improvement cycle such as Plan–Do–Check–Act can incorporate ethical and governance gates. During Plan, the team identifies stakeholders, legal obligations, safety hazards, privacy implications, ESG impacts, and possible unintended consequences. During Do, it pilots the change under controlled conditions, protects affected individuals, and documents deviations. During Check, it evaluates not only efficiency and conformance but also adverse events, subgroup effects, data integrity, and stakeholder feedback. During Act, it standardizes successful controls, revises the risk assessment, communicates lessons, and defines ongoing monitoring.

Lean and Six Sigma projects require similar discipline. Waste reduction should not eliminate controls that protect safety or dignity. Statistical significance does not automatically establish ethical acceptability. A process with improved average performance may still have unacceptable variation for a vulnerable population. Project charters should therefore include ethical constraints and sustainability outcomes alongside financial and operational goals.

A practical project governance template asks:

• What benefit is being pursued, and for whom?
• What harms or rights violations could result?
• Which laws, standards, and internal policies apply?
• Who approves the change, and who independently reviews it?
• What data are collected, and how are privacy and security protected?
• How will fairness, safety, and environmental effects be measured?
• What triggers escalation, suspension, disclosure, or remediation?
• How will the organization verify that improvement is sustained?

Digital Quality, Automation, and Artificial Intelligence

Digital tools can strengthen traceability, detect anomalies, predict equipment failure, and support real-time quality decisions. However, automation may also reproduce biased data, create opaque decisions, increase surveillance, or encourage over-reliance on system outputs. The quality principle of “trust but verify” is especially important when an algorithm influences safety, employment, access to services, or release decisions.

Responsible use requires defined purposes, validated data, version control, cybersecurity, access management, monitoring for drift, explainability appropriate to the risk, and human accountability. A model should be tested before deployment and periodically reassessed after changes in data, process, regulation, or operating conditions. Performance should be evaluated across relevant subgroups, not only by overall accuracy.

Automation bias occurs when people accept an automated recommendation without adequate challenge. To reduce it, organizations can require documented human review for high-risk decisions, display uncertainty, establish override procedures, and investigate disagreements between human and system judgments. No automated system should become a way to avoid managerial accountability.

Illustrative Case: The Delayed Release Decision

Background

MedSure Devices, a fictional manufacturer of monitoring equipment, was preparing to release a revised patient-monitoring device. Pilot testing showed improved battery performance and lower production cost. A final validation test, however, identified intermittent signal loss under a combination of temperature and motion conditions. The failure rate was low in the available sample, and the commercial team argued that the launch should proceed because the issue affected only a small proportion of units.

Situation and analysis

The quality manager faced competing pressures: customer commitments, revenue targets, patient safety, incomplete evidence, and uncertainty about the operating conditions in hospitals. The initial proposal was to release the device with an updated user instruction while further data were collected. The quality team recognized that the instruction might not adequately control a failure that could occur during critical monitoring.

Stakeholder analysis identified patients, clinicians, distributors, employees, regulators, investors, and hospitals. The most vulnerable stakeholders were patients whose clinical decisions could be affected by an undetected signal interruption. A rights-based analysis emphasized the duty not to expose users to an inadequately characterized safety risk. A consequentialist analysis also showed that a short launch delay could prevent larger costs associated with recall, injury, loss of trust, and regulatory action.

Approach and solution

The governance committee required an independent technical review, expanded testing under realistic conditions, and a documented risk assessment. The release was paused for the affected configuration. Engineering redesigned the signal-processing component, while the quality team introduced additional verification tests and a traceability requirement for the revised software. Regulatory specialists assessed notification obligations, and clinical users were consulted about the adequacy of alarms and instructions.

The committee also reviewed incentive structures and found that launch bonuses had encouraged narrow attention to schedule performance. The incentive design was changed to include safety and validated quality outcomes. A post-release monitoring plan was established, including complaint analysis, subgroup review, and escalation thresholds.

Outcome

The redesigned device passed expanded validation, and the controlled release occurred later than planned. The organization incurred short-term development and scheduling costs but avoided releasing a product with unresolved safety uncertainty. More importantly, the case led to improved design controls, independent review, and governance of launch decisions.

Learning points

The case illustrates that a low observed failure rate does not necessarily imply low ethical risk. Evidence must be interpreted in relation to severity, exposure, detectability, and vulnerable users. It also shows that governance is not an obstacle to innovation; it creates disciplined conditions under which innovation can be trusted. Finally, performance measures influence behavior. If schedule and revenue dominate safety and integrity, the quality system will eventually reflect those priorities.

Challenges, Risks, and Common Mistakes

The first challenge is conflicting objectives. Cost, speed, sustainability, safety, and fairness may not improve together automatically. Managers should make trade-offs explicit rather than hiding them behind a single composite score.

The second is ethical fading, in which a moral issue is described only as a technical or financial problem. Terms such as “acceptable loss,” “data cleansing,” or “temporary exception” can obscure who may be harmed. Quality professionals should use precise language and ask the human-impact question directly.

The third is metric gaming. If teams are judged only on closure rates, they may close findings superficially. If customer satisfaction is the sole measure, employees may avoid serving difficult cases. Balanced indicators, independent verification, and outcome-based review reduce this risk.

Other common mistakes include treating compliance documents as evidence of actual control; allowing auditors to assess their own work; collecting excessive personal data; relying on averages that conceal inequity; using sustainability claims without reliable boundaries; failing to investigate near misses; and punishing employees who raise concerns.

Ethical systems also have limitations. No framework eliminates judgment or uncertainty. Stakeholder interests may be genuinely incompatible, data may be incomplete, and legal requirements may differ across jurisdictions. Ethical review can require time and resources, and excessive bureaucracy can discourage responsible innovation. The answer is not to abandon controls but to apply them proportionately, use evidence intelligently, and preserve clear accountability.

Current Developments and Best Practices

Organizations are increasingly moving from periodic compliance to continuous assurance, using process data, automated controls, and risk indicators to identify problems earlier. Supply-chain transparency is also receiving greater attention as organizations are held responsible for labor, environmental, and human-rights conditions beyond their immediate facilities.

Climate risk, circular economy principles, responsible sourcing, accessibility, algorithmic accountability, and digital-product safety are becoming integrated with quality management. Assurance of sustainability information is developing because stakeholders increasingly expect claims to be supported by reliable evidence. At the same time, organizations face the danger of “greenwashing” or presenting isolated improvements as proof of overall responsibility.

Best practice is characterized by leadership example, a speak-up culture, risk-based controls, independent challenge, protected reporting, transparent metrics, stakeholder participation, documented decisions, and learning from adverse events. Ethical and sustainable quality should be embedded in project charters, procurement, design reviews, audits, management review, training, and reward systems—not left to a specialist department.

Chapter Summary

Ethics, governance, and sustainability expand quality from narrow conformance to responsible value creation. Ethical quality protects stakeholders, respects rights, promotes fairness, and requires truthful evidence. Governance converts principles into decision rights, controls, assurance, escalation, and accountability. Compliance establishes a necessary minimum, while responsible quality may require action beyond legal requirements where foreseeable harm exists.

Quality projects should use structured ethical reasoning, stakeholder analysis, risk-based controls, independent audits, privacy safeguards, fairness checks, and robust safety processes. ESG considerations should be integrated into life-cycle thinking, project metrics, supplier management, and continuous improvement. Digital systems and AI can improve quality but require validation, cybersecurity, transparency, human oversight, and monitoring for bias and drift. Sustainable operational excellence is achieved when performance, integrity, safety, social responsibility, and environmental stewardship reinforce one another.

Key Terms

Ethical quality: Quality achieved while respecting duties, rights, fairness, safety, and stakeholder welfare.

Governance: The structures and processes used to direct, control, and hold an organization accountable.

Compliance: Conformance with applicable laws, regulations, standards, contracts, and internal requirements.

Stakeholder: A person or group affected by, able to affect, or legitimately concerned with an organizational decision.

Integrity: Consistency between stated principles, evidence, decisions, and conduct.

Transparency: Provision of relevant information in a timely, accurate, and understandable form.

Accountability: The obligation to explain decisions, accept scrutiny, and accept consequences.

Due care: Reasonable attention to foreseeable risks and responsibilities.

Precautionary principle: Protective action taken when potential serious harm exists despite incomplete certainty.

Materiality: The significance of information or an event to stakeholder decisions.

Audit independence: Freedom of an auditor from conflicts and inappropriate influence by the audited activity.

Privacy: Protection of individuals’ control over personal information and its legitimate use.

Fairness: Consistent and just treatment, with differences justified by relevant and proportionate reasons.

Product safety: Protection of users and others from unacceptable risks associated with a product.

ESG: Environmental, social, and governance factors used to assess responsible organizational performance.

Life-cycle thinking: Evaluation of impacts from inputs and design through use, maintenance, and end-of-life.

Ethical fading: Loss of awareness that a decision contains a moral issue because it is framed technically or financially.

Audit capture: Compromise of audit objectivity through dependence on or influence by the audited organization.

Automation bias: Excessive reliance on an automated recommendation or decision.

Continuous assurance: Ongoing evaluation of controls and risks using timely evidence rather than only periodic reviews.

Review Questions

Short Answer Questions

1. Why is compliance described as a floor rather than the ceiling of quality?

2. Distinguish responsibility from accountability.

3. What is the purpose of segregation of duties in quality governance?

4. Why can average quality indicators conceal unfairness?

5. Define automation bias and state one way to reduce it.

Long Answer Questions

1. Explain how ethical decision-making can be integrated into the Plan–Do–Check–Act cycle.

2. Discuss the relationship between audit independence, organizational governance, and reliable assurance.

3. Explain how privacy, fairness, and data governance affect digital quality improvement.

4. Discuss how ESG and life-cycle thinking alter traditional quality-project decisions.

5. Describe the role of leadership, incentives, and speak-up culture in sustainable quality.

Analytical / Application Questions

1. A supplier offers a major cost reduction but refuses to disclose labor-practice information. Develop a governance and ethical response using stakeholder analysis, risk assessment, and escalation.

2. An AI inspection system has high overall accuracy but a significantly higher false-rejection rate for products from one production line. Analyze the possible causes and recommend controls before deployment.

3. A hospital quality team wants to reduce average waiting time by prioritizing patients who can complete digital forms quickly. Evaluate the proposal from efficiency, fairness, accessibility, privacy, and safety perspectives, and design a better alternative.

22. Multiple Choice Questions with Answers

Question 1

A quality project meets all stated technical specifications but creates a foreseeable and serious risk for vulnerable users. What is the most responsible conclusion?

A. The project is acceptable because specification compliance is sufficient

B. The risk should be ignored unless a customer files a complaint

C. The project requires ethical and safety review beyond technical conformance

D. The project should proceed if its financial benefits are substantial

Correct Answer: C. The project requires ethical and safety review beyond technical conformance

Question 2

Which action best demonstrates audit independence?

A. Allowing managers to rewrite unfavorable findings

B. Having auditors evaluate work for which they had direct operational responsibility

C. Providing auditors unrestricted access and protection from inappropriate influence

D. Selecting auditors solely because they are familiar to the process owner

Correct Answer: C. Providing auditors unrestricted access and protection from inappropriate influence

Question 3

During an ethical decision, why should vulnerable stakeholders be explicitly identified?

A. They always have greater decision-making power

B. Their interests may be overlooked despite their exposure to significant harm

C. They eliminate the need to consider other stakeholders

D. They are legally responsible for organizational decisions

Correct Answer: B. Their interests may be overlooked despite their exposure to significant harm

Question 4

Which statement best describes the relationship between compliance and ethical quality?

A. Compliance makes ethical analysis unnecessary

B. Ethical quality permits violation of regulations when intentions are good

C. Compliance is a minimum requirement, while ethical quality may require additional protection

D. Compliance applies only to financial processes

Correct Answer: C. Compliance is a minimum requirement, while ethical quality may require additional protection

Question 5

A dashboard reports excellent average service performance, but one demographic group experiences much longer delays. What is the most appropriate quality response?

A. Retain the average because it represents the whole organization

B. Disaggregate the data and investigate the disparity

C. Remove demographic information from the analysis

D. Declare the difference acceptable without examining its cause

Correct Answer: B. Disaggregate the data and investigate the disparity

Question 6

Which control most directly reduces automation bias in a high-risk decision?

A. Removing uncertainty information from the interface

B. Requiring documented human review and an override process

C. Allowing the algorithm to make all decisions without intervention

D. Evaluating the system only on its overall accuracy

Correct Answer: B. Requiring documented human review and an override process

Question 7

In the illustrative MedSure case, why was delaying release ethically justified?

A. The product had no potential commercial value

B. The unresolved failure involved a potentially serious safety risk under realistic conditions

C. All product launches must be delayed regardless of evidence

D. The quality team wanted to avoid collecting more data

Correct Answer: B. The unresolved failure involved a potentially serious safety risk under realistic conditions

Question 8

Which practice best reflects life-cycle thinking?

A. Optimizing factory cost without considering product disposal

B. Evaluating environmental and social effects from raw materials through end-of-life

C. Measuring only energy use during final assembly

D. Treating supplier conduct as unrelated to quality

Correct Answer: B. Evaluating environmental and social effects from raw materials through end-of-life

Question 9

What is a common consequence of rewarding teams only for rapid audit closure?

A. More thorough investigation of root causes

B. Improved auditor independence

C. Superficial closure and concealment of unresolved problems

D. Greater protection of whistleblowers

Correct Answer: C. Superficial closure and concealment of unresolved problems

Question 10

Which governance arrangement most clearly separates operational control from independent assurance?

A. The process owner audits and approves the same process

B. Internal audit evaluates controls while operational owners manage them

C. The compliance team performs production tasks and certifies its own work

D. Senior executives approve findings without reviewing evidence

Correct Answer: B. Internal audit evaluates controls while operational owners manage them