5. Quality Strategy, Policy and Deployment

Introduction: From Quality Intent to Strategic Performance

Quality becomes strategically significant when it moves beyond inspection, compliance, or isolated improvement projects and becomes a deliberate way of directing the organization. A quality strategy explains how an organization will create dependable value for customers and other stakeholders while achieving its competitive and corporate objectives. Quality policy expresses senior management’s commitment and broad direction. Quality objectives translate that direction into measurable results. Deployment connects objectives, resources, processes, and accountability throughout the organization.

This chapter examines how organizations align quality with business strategy through quality policy, strategic quality planning, Hoshin Kanri, the Balanced Scorecard, resource allocation, and cross-functional governance. The central issue is not simply whether an organization has a policy or a set of targets. The issue is whether strategic intent is understood, translated into operational priorities, supported with resources, reviewed through reliable evidence, and improved when assumptions change.

A manufacturing firm may seek cost leadership, a hospital may compete through patient safety and reliability, and a software company may differentiate through secure and responsive service. Their quality strategies will differ, but each must answer similar questions: What does value mean to stakeholders? Which capabilities create that value? Which quality risks threaten the strategy? How should priorities be deployed across functions? How will leaders know whether improvement is producing strategic results?

Learning Objectives

By the end of this chapter, learners should be able to:

1. Explain the relationship between corporate strategy, competitive strategy, quality policy, quality objectives, and operational deployment.

2. Construct and evaluate a strategic quality planning process.

3. Compare Hoshin Kanri and the Balanced Scorecard as approaches to strategic alignment.

4. Develop meaningful quality objectives, measures, targets, and review mechanisms.

5. Analyse resource-allocation and governance decisions affecting quality performance.

6. Identify common deployment failures, ethical risks, and limitations of strategic quality systems.

7. Apply the concepts to a cross-functional organizational case.

Quality as a Strategic Capability

Corporate strategy determines the broad scope and direction of the organization: the markets it will serve, the value it intends to create, and the capabilities it must develop. Competitive strategy concerns how the organization will achieve advantage, for example through lower cost, superior responsiveness, innovation, customization, reliability, or trust. Quality strategy links these choices to the design and control of products, services, processes, people, technology, and relationships.

Quality is therefore multidimensional. Customers may judge quality through conformance, performance, durability, availability, safety, ease of use, service recovery, or experience. Internal departments may use different language for the same strategic concern. Marketing may describe it as customer loyalty, operations as process capability, procurement as supplier reliability, and finance as cost of poor quality. Strategic quality management integrates these perspectives without assuming that a single measure can represent quality adequately.

A useful hierarchy is:

• Strategic intent: the desired long-term position of the organization.
• Quality policy: the organization’s formally stated principles and commitments concerning quality.
• Strategic quality objectives: specific results required to realize the policy and strategy.
• Operational objectives: departmental or process-level results that support strategic objectives.
• Measures and targets: evidence used to assess progress and trigger action.
• Initiatives and projects: coordinated interventions intended to close performance gaps.

The hierarchy is not purely vertical. Learning from processes, customers, employees, and suppliers may reveal that the strategy itself requires revision. Effective deployment is thus a cycle of alignment, execution, learning, and adjustment rather than a one-time cascade of targets.

Quality Policy: Commitment with Direction

A quality policy is a formally expressed statement of an organization’s intentions and direction concerning quality. It should be appropriate to the organization’s purpose and context, provide a framework for establishing objectives, communicate a commitment to applicable requirements and continual improvement, and guide decisions at all levels. A policy is valuable only when it influences priorities, investment, behaviour, and review.

Weak policies commonly use broad promises such as “to achieve excellence through customer satisfaction” without specifying what excellence means or how decisions will be made. A stronger policy identifies the organization’s value proposition and strategic commitments. For example, a medical-device manufacturer might commit to patient safety, evidence-based design, regulatory conformity, dependable supply, and rapid learning from field performance. Such a statement provides more guidance than a general promise to “deliver quality products.”

Policy development should involve senior leadership but should not be written in isolation. Customers, regulators, employees, process owners, and relevant partners can provide insight into important requirements and risks. Once approved, the policy must be communicated in language appropriate to different audiences. Communication is not equivalent to display. Employees should be able to explain how the policy affects their work and what evidence demonstrates its fulfilment.

The policy should be reviewed when there are significant changes in markets, technology, regulation, organizational purpose, or risk exposure. A policy that remains unchanged while the organization’s strategy changes can become ceremonial and misleading.

Strategic Quality Planning

Strategic quality planning converts strategic intent into a coherent pattern of choices. It normally begins with an assessment of the external and internal environment. External analysis includes customer expectations, competitors, regulation, technology, supply conditions, social expectations, and emerging risks. Internal analysis examines process capability, culture, leadership, knowledge, technology, financial capacity, supplier performance, and historical quality costs.

A practical planning sequence is as follows:

1. Clarify purpose and stakeholders. Identify the organization’s mission, strategic priorities, customer segments, and relevant stakeholder requirements.

2. Define value and critical quality characteristics. Determine the attributes that most strongly affect safety, satisfaction, performance, trust, and competitive position.

3. Assess the current state. Use customer data, audits, process measures, benchmarking, employee knowledge, risk analysis, and financial evidence.

4. Identify strategic gaps and risks. Distinguish symptoms from systemic causes and rank issues according to impact, urgency, likelihood, and organizational capability.

5. Set a limited number of strategic objectives. Objectives should be consequential, measurable, time-bound, and connected to value creation or risk reduction.

6. Select initiatives and process owners. Define the changes, capabilities, and cross-functional cooperation required.

7. Allocate resources and establish governance. Assign people, funds, technology, authority, and review routines.

8. Deploy, measure, learn, and revise. Monitor both results and leading indicators, investigate variation, and update plans when evidence demands it.

Strategic planning must distinguish outcomes from activities. “Train 500 employees” is an activity; “reduce critical process errors by 30 percent without increasing safety risk” is an outcome. Training may be one means of achieving the outcome, but it should not be mistaken for evidence of effectiveness.

Quality objectives should also express a balance between aspiration and feasibility. Targets set too low fail to mobilize improvement; targets set without regard to process knowledge may encourage concealment, manipulation, or unsafe shortcuts. Where uncertainty is high, leaders can use staged targets, assumptions, and review thresholds rather than pretending to possess false precision.

Hoshin Kanri and the Logic of Catchball

Hoshin Kanri, often translated as policy deployment or strategy deployment, is a systematic approach for aligning long-term direction with annual priorities and daily management. It seeks to prevent strategic objectives from remaining at headquarters while operational work proceeds according to unrelated local priorities.

A typical Hoshin process includes a small number of breakthrough objectives, annual objectives, improvement priorities, measures, owners, and review routines. Senior leaders define the direction, but objectives are negotiated through a process often called catchball. In catchball, proposed priorities move between levels and functions. Managers and employees test whether objectives are understandable, feasible, measurable, and supported by the required processes and resources. The dialogue may lead to revised targets, dependencies, or methods.

Hoshin Kanri usually distinguishes breakthrough work from routine management. Routine management maintains current process performance through standard work, control plans, audits, and problem response. Breakthrough work changes the level of performance or builds a new capability. Confusing the two can cause either strategic neglect or instability in basic operations.

The X-matrix is a commonly associated visual tool. It links long-term objectives, annual objectives, improvement priorities, measures, and responsible owners. It is not a substitute for judgement; its value lies in making relationships and accountability visible. Reviews such as monthly progress checks and periodic reflection examine not only whether targets were achieved but also whether the chosen methods were valid.

Hoshin’s strength is its emphasis on alignment, dialogue, and organizational learning. Its risks include excessive formality, too many priorities, mechanical target cascading, and a tendency to treat negotiation as compromise rather than evidence-based problem solving.

The Balanced Scorecard as a Strategic Quality Framework

The Balanced Scorecard translates strategy into a connected set of objectives and measures. Its conventional perspectives are financial, customer, internal process, and learning and growth. Quality strategy can be represented across all four rather than being confined to an operational dashboard.

For example, a service organization may establish the following chain:

• Learning and growth: develop employee problem-solving capability and improve knowledge access.
• Internal process: reduce avoidable handoffs and increase first-time-right completion.
• Customer: improve reliability and reduce complaints requiring repeat contact.
• Financial: lower cost of poor quality and improve customer retention.

The perspectives should form a strategy map showing hypotheses about cause and effect. The organization must test these hypotheses rather than assume that every training activity automatically creates financial value. Leading indicators, such as process adherence or capability development, should be examined alongside lagging indicators, such as complaints, warranty cost, and retention.

The Balanced Scorecard is particularly useful where leadership must balance competing demands. For example, reducing service time may improve productivity but harm accuracy or customer trust. A portfolio of measures makes such trade-offs more visible. However, balance does not mean using many measures. Excessive indicators dilute attention and create opportunities for contradictory incentives. A concise scorecard should contain measures that are strategically important, controllable or influenceable, clearly defined, and linked to decisions.

Hoshin Kanri and the Balanced Scorecard are complementary. Hoshin emphasizes deployment, dialogue, and disciplined execution; the Balanced Scorecard emphasizes strategic logic and multidimensional performance. Either approach can fail if leaders do not establish ownership, resource support, and honest review.

Measures, Targets, and Strategic Evidence

Measurement gives strategy operational visibility, but measurement can also distort behaviour. A measure should have a clear operational definition, data source, collection frequency, owner, baseline, target, and interpretation rule. Important distinctions include:

• Outcome measures: the results experienced by customers or the organization.
• Process measures: characteristics of the process that influence outcomes.
• Leading indicators: signals of future performance or capability.
• Lagging indicators: results observed after performance has occurred.
• Balancing measures: indicators used to detect harmful side effects of improvement.

Suppose a call centre sets a target to reduce average handling time. Without a balancing measure such as repeat contacts, customer resolution, or compliance accuracy, employees may shorten calls by transferring customers or ending interactions prematurely. A strategically responsible target might therefore combine handling time with first-contact resolution, customer effort, and error rates.

Targets should be disaggregated where appropriate. Aggregate performance can conceal inequity, unstable sub-processes, or failure in a high-risk customer group. At the same time, disaggregation should protect privacy and avoid stigmatizing small groups. The purpose is better understanding and action, not surveillance for its own sake.

Data quality is a strategic concern. Inconsistent definitions, delayed reporting, selective exclusions, and incompatible systems can make performance comparisons unreliable. Leaders should ask whether a measure is valid, reliable, timely, resistant to gaming, and useful for a decision. A sophisticated dashboard with poor data can create greater confidence in error rather than better quality.

Resource Allocation and Strategic Quality Choices

Quality strategy becomes credible when resources reflect stated priorities. Resource allocation includes budgets, staffing, leadership time, training, technology, maintenance, supplier development, analytical capability, and access to decision makers. Underinvestment in prevention often produces higher costs later through rework, complaints, warranty, disruption, litigation, or reputational damage.

Organizations must make choices among competing improvement opportunities. A useful portfolio approach considers expected benefit, risk reduction, regulatory importance, customer impact, implementation effort, interdependence, and reversibility. Financial appraisal may include cost of poor quality, expected-value analysis, lifecycle cost, and scenario analysis. Not all quality investments have immediate financial returns; safety, resilience, ethical compliance, and trust may justify investment even when benefits are difficult to monetize.

Resource decisions should also account for organizational capacity. Launching numerous initiatives without removing lower-value work creates change fatigue. A strategically coherent portfolio may contain fewer projects, each with sufficient expertise and management attention. Leaders should identify constraints such as scarce technical specialists, data limitations, production downtime, or supplier dependence before approving targets.

Cross-Functional Governance

Strategic quality problems rarely respect organizational boundaries. A customer complaint may involve product design, procurement, production, logistics, sales promises, installation, and service recovery. Functional optimization can therefore undermine total performance. Cross-functional governance creates mechanisms through which these dependencies are identified and managed.

Effective governance clarifies decision rights, escalation routes, review forums, data ownership, and accountability for shared outcomes. A steering committee may approve priorities and resources, while process councils coordinate improvement across departments. A process owner should have sufficient authority to influence the entire value stream, not merely one departmental segment.

Governance differs from bureaucracy. Its purpose is to improve decisions and accountability, not multiply meetings. Reviews should focus on evidence, risks, unresolved interdependencies, and corrective action. Psychological safety is essential: employees must be able to report defects, near misses, and unrealistic targets without retaliation. Otherwise governance receives polished reports rather than accurate information.

Quality governance also includes relationships with suppliers, contractors, regulators, professional bodies, and customers. Contracts should not transfer responsibility for quality without establishing clear requirements, communication, capability verification, and learning mechanisms. Outsourcing a process does not outsource the organization’s accountability for the customer outcome.

Illustrative Case: Meridian Home Diagnostics

Background

Meridian Home Diagnostics is an illustrative regional company that supplies home testing kits through pharmacies and an online channel. Its corporate strategy is to grow by offering convenient, trustworthy testing at an affordable price. Sales have increased, but complaints about missing components, unclear instructions, and delayed replacement kits are also increasing.

Situation and Problem

The executive team initially proposes a target of reducing complaints by 40 percent within one year. The target is assigned to the customer-service department, which responds by adding temporary staff and closing tickets more quickly. Complaint numbers fall slightly, but repeat contacts rise, replacement costs increase, and pharmacy partners report declining confidence. The measure has encouraged administrative closure rather than improved quality.

Analysis

A cross-functional review maps the customer journey. The principal causes are found to be inconsistent packaging checks, two versions of the instruction leaflet in circulation, weak change control for suppliers, and no common definition of a “resolved” complaint. The problem is therefore strategic and systemic, not simply a customer-service workload issue.

The team identifies critical quality characteristics: kit completeness, instruction clarity, reliable delivery, and effective resolution. It establishes a baseline using complaint rates per thousand kits, first-contact resolution, repeat contacts, replacement cost, packaging defect rate, and customer comprehension in a small usability study. A balancing measure ensures that faster ticket closure does not reduce resolution quality.

Approach and Deployment

Senior leaders revise the quality policy to emphasize safe, understandable, and dependable access to testing. Through a Hoshin-style catchball process, the annual priorities are agreed as: reduce packaging defects, standardize controlled instructions, improve supplier change notification, and create closed-loop complaint learning.

The Balanced Scorecard links these priorities to customer trust, internal process capability, employee problem-solving competence, and cost of poor quality. Operations owns packaging capability; regulatory affairs owns document control; procurement owns supplier-change governance; customer service owns the learning loop, with a shared executive sponsor.

Resources are allocated for an automated vision check, controlled digital artwork, supplier audits based on risk, and training in structured problem solving. A monthly cross-functional council reviews outcome and process measures. The council is authorized to stop a shipment when a critical defect is suspected, rather than waiting for consensus across departments.

Outcome

After the first review cycle, complaint volume has not yet reached the final target, but packaging defect rates and repeat contacts have declined. The organization discovers that one supplier’s process variation is greater than previously reported and changes the supplier-development plan. Leaders retain the objective but revise the implementation assumptions. This illustrates the importance of learning rather than treating a target as proof that the original method was correct.

Learning Points

The case demonstrates five principles. First, a departmental target can conceal a system problem. Second, quality objectives require valid definitions and balancing measures. Third, policy must guide actual resource and authority decisions. Fourth, cross-functional ownership is necessary when value is created across a process. Fifth, strategic deployment is iterative: evidence can require a change in method without abandoning the underlying strategic intent.

Risks, Limitations, and Common Errors

Strategic quality systems can fail for reasons that are managerial rather than technical. Common errors include:

• treating the quality policy as a communication artifact rather than a decision criterion;
• setting too many objectives, creating fragmented attention;
• cascading targets mechanically without testing process capability;
• rewarding local performance that damages total system performance;
• using lagging indicators alone and discovering failure too late;
• confusing activity completion with improvement in outcomes;
• ignoring the cost and capacity required to sustain gains;
• manipulating data or suppressing bad news to protect target achievement;
• changing priorities so frequently that employees abandon long-term learning;
• assuming that technology will solve unclear processes or weak governance.

There are also limits to formal frameworks. Hoshin Kanri and the Balanced Scorecard do not remove uncertainty, resolve conflicting stakeholder values, or guarantee causal validity. A scorecard can simplify reality excessively; a catchball process can become political; a strategic plan can become obsolete after a major disruption. Professional judgement, experimentation, and open challenge remain necessary.

Ethically, leaders must ensure that quality targets do not encourage unsafe production, concealment of defects, unfair treatment of employees, or exclusion of vulnerable customers. Metrics should be used to improve systems, not merely to assign blame. Personal and customer data used for quality analytics must be collected lawfully, protected appropriately, and interpreted with awareness of bias. Regulatory compliance is a minimum requirement, not a replacement for responsibility to users and society.

Digital Applications and Emerging Developments

Digital systems increasingly connect customer feedback, process data, supplier information, maintenance records, and financial consequences. Integrated dashboards can provide near-real-time visibility, while process mining can reveal delays, rework loops, and deviations from intended workflows. Statistical learning may support anomaly detection or predictive maintenance, but its outputs require validation and human oversight.

Artificial intelligence can help classify complaints, identify recurring defect patterns, generate summaries, and prioritize investigations. However, automated recommendations may reproduce biased historical decisions, misclassify rare but serious events, or create false confidence. Human review is especially important where safety, eligibility, privacy, or regulatory decisions are involved. Data governance should define ownership, traceability, model monitoring, access control, and escalation when system performance deteriorates.

Emerging quality strategies increasingly address resilience, cybersecurity, sustainability, and supply-chain transparency alongside traditional conformance. Climate-related disruption, geopolitical dependency, and digital vulnerability can affect the organization’s ability to deliver consistent quality. Strategic quality planning must therefore consider not only efficiency under normal conditions but also adaptability under stress.

Best Practices for Strategic Quality Deployment

A mature organization generally follows several practices:

1. Keep the quality policy short enough to guide decisions and specific enough to be meaningful.

2. Limit strategic priorities and explain why they matter.

3. Translate objectives through dialogue, not mechanical copying.

4. Combine customer, process, people, financial, risk, and learning evidence.

5. Assign end-to-end ownership for cross-functional outcomes.

6. Fund prevention, capability development, data quality, and improvement infrastructure.

7. Use balancing measures to detect unintended consequences.

8. Review assumptions and methods, not only target achievement.

9. Protect truthful reporting and treat bad news as a source of learning.

10. Integrate strategy deployment with daily management so that improvement is sustained.

Chapter Summary

Quality strategy aligns quality capability with the organization’s competitive and corporate direction. A quality policy expresses leadership commitment, but its value depends on translation into measurable objectives, supported initiatives, resources, and governance. Strategic quality planning begins with stakeholder and environmental analysis, identifies critical quality characteristics and risks, and converts gaps into a focused portfolio of objectives.

Hoshin Kanri contributes disciplined deployment, catchball dialogue, and alignment between breakthrough priorities and daily management. The Balanced Scorecard connects quality to customer, process, learning, and financial results through a strategic logic of leading and lagging indicators. Effective measurement requires valid definitions, suitable targets, balancing measures, and attention to data quality.

Resource allocation signals the seriousness of strategic intent, while cross-functional governance prevents departmental optimization from damaging total value. Digital tools can strengthen visibility and analysis, but they do not replace sound processes, ethical judgement, or human accountability. Strategic quality management is ultimately a cycle of direction, execution, evidence, learning, and renewal.

Key Terms

Quality strategy: A coordinated pattern of choices for creating stakeholder value through quality capabilities.

Quality policy: A formally stated direction and commitment concerning quality.

Quality objective: A specific intended result related to quality performance or capability.

Strategic quality planning: The process of translating organizational strategy into quality priorities, objectives, initiatives, and resources.

Policy deployment: The systematic translation of strategic intent into aligned objectives and actions throughout an organization.

Hoshin Kanri: An approach to strategy deployment that links long-term direction, annual priorities, implementation, and review.

Catchball: Two-way negotiation and learning between organizational levels during objective deployment.

Breakthrough objective: A significant strategic improvement intended to change the level of organizational performance.

Routine management: Activities that maintain and control current process performance.

Balanced Scorecard: A framework that links strategy to objectives and measures across financial, customer, internal-process, and learning perspectives.

Leading indicator: A measure that signals future performance or developing capability.

Lagging indicator: A measure of results observed after an activity or process has occurred.

Balancing measure: An indicator used to detect adverse side effects of pursuing another target.

Cost of poor quality: Costs arising from prevention failures, appraisal, internal defects, and external defects.

Strategic alignment: Consistency between organizational direction, objectives, resources, processes, and measures.

Cross-functional governance: Structures and practices for coordinating decisions and accountability across departments.

Process owner: The person accountable for the performance and improvement of an end-to-end process.

Quality deployment: The movement of quality priorities from policy and strategy into operational work and learning.

Review Questions

Short Answer Questions

1. How does a quality policy differ from a quality objective?

2. What is the purpose of catchball in Hoshin Kanri?

3. Distinguish between a leading indicator and a lagging indicator.

4. Why are balancing measures important when setting performance targets?

5. What is meant by cross-functional governance?

Long Answer Questions

1. Explain how corporate strategy, competitive strategy, quality policy, and operational objectives are connected.

2. Describe the stages of a strategic quality planning process and discuss the managerial decisions involved at each stage.

3. Compare Hoshin Kanri and the Balanced Scorecard in terms of purpose, strengths, and limitations.

4. Discuss how resource allocation affects the credibility and success of a quality strategy.

5. Explain the ethical and governance risks associated with target-driven quality management.

Analytical / Application Questions

1. A hospital reduces average patient discharge time, but readmissions and medication errors increase. Design a balanced set of quality measures and explain how you would govern the improvement initiative.

2. A manufacturer’s corporate strategy is based on customization and rapid delivery. Develop three strategic quality objectives, suitable measures, and likely cross-functional owners.

3. An organization has a detailed scorecard but continues to miss customer expectations. Analyse at least four possible causes and propose a revised deployment and review process.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes the relationship between a quality policy and quality objectives?

A. The policy provides broad direction, while objectives specify intended measurable results.

B. The policy is prepared by operational employees, while objectives are prepared only by customers.

C. The policy measures daily performance, while objectives describe organizational values only.

D. The policy and objectives are interchangeable terms.

Correct Answer: A. The policy provides broad direction, while objectives specify intended measurable results.

Question 2

The primary purpose of catchball in Hoshin Kanri is to:

A. Transfer all strategic decisions to the finance department.

B. Enable two-way negotiation to test the feasibility and alignment of objectives.

C. Replace performance measurement with informal discussion.

D. Ensure that every department receives identical numerical targets.

Correct Answer: B. Enable two-way negotiation to test the feasibility and alignment of objectives.

Question 3

A call centre reduces average handling time, but repeat contacts increase. Which measure would best serve as a balancing measure?

A. Number of employees attending training

B. Total number of calls received

C. First-contact resolution rate

D. Number of supervisor meetings

Correct Answer: C. First-contact resolution rate

Question 4

Which of the following is an outcome rather than an activity?

A. Train 500 employees in problem solving.

B. Install a new dashboard.

C. Hold monthly quality meetings.

D. Reduce critical process errors by 30 percent.

Correct Answer: D. Reduce critical process errors by 30 percent.

Question 5

Which Balanced Scorecard perspective most directly concerns employee capability and organizational learning?

A. Financial

B. Customer

C. Internal process

D. Learning and growth

Correct Answer: D. Learning and growth

Question 6

A department meets its delivery target by transferring incomplete work to another department. What strategic quality problem does this illustrate?

A. Excessive use of leading indicators

B. Local optimization that harms total system performance

C. Successful cross-functional governance

D. Overinvestment in prevention

Correct Answer: B. Local optimization that harms total system performance

Question 7

Which practice most strengthens the credibility of a quality strategy?

A. Displaying the policy without reviewing it

B. Using only financial indicators

C. Aligning resources, authority, objectives, and review mechanisms

D. Increasing the number of targets assigned to each employee

Correct Answer: C. Aligning resources, authority, objectives, and review mechanisms

Question 8

Why should strategic quality reviews examine assumptions and methods, not only results?

A. Targets are always inappropriate.

B. A missed or achieved target may not reveal whether the chosen method is valid.

C. Measures are unnecessary when leaders have experience.

D. Methods cannot be changed after approval.

Correct Answer: B. A missed or achieved target may not reveal whether the chosen method is valid.

Question 9

Which situation presents the clearest ethical risk in target-driven quality management?

A. Using a baseline before setting a target

B. Reviewing supplier performance with process data

C. Encouraging employees to conceal defects to protect reported performance

D. Using a balancing measure to monitor unintended effects

Correct Answer: C. Encouraging employees to conceal defects to protect reported performance

Question 10

An organization wants to use AI to classify safety-related complaints. What is the most appropriate governance response?

A. Accept all automated classifications without review.

B. Remove human oversight because AI is more consistent.

C. Validate the system, monitor errors and bias, and retain human escalation for serious cases.

D. Use only historical data and prohibit model monitoring.

Correct Answer: C. Validate the system, monitor errors and bias, and retain human escalation for serious cases.