4. Process Management and Standardization

Introduction and Context

Total Quality Management (TQM) treats quality not as the responsibility of an inspection department but as the result of how work is designed, performed, controlled and improved. Every product or service is created through a process: a linked sequence of activities that converts inputs into outputs for an internal or external customer. Consequently, recurring quality problems are often symptoms of poorly designed, unstable or inadequately controlled processes rather than isolated employee failures.

Process management provides the discipline for understanding this sequence, assigning responsibility, measuring performance and improving results. Standardization complements process management by establishing the agreed method for performing work under defined conditions. Together, they create a foundation for consistency, learning and continual improvement. Standardization does not mean that work must remain unchanged. Rather, it creates a current best-known method against which improvement can be planned, tested and institutionalized.

For production managers, process thinking is particularly important because manufacturing and service operations contain numerous interdependent activities. A delay in material release may disrupt machining, assembly and dispatch. An unclear approval procedure may create rework in procurement or product development. A service failure may arise from interactions among front-office employees, information systems and external partners. Process analysis makes these relationships visible.

This chapter develops the practical and managerial methods used to manage processes: SIPOC diagrams, flowcharts, value-stream maps, service blueprints, process ownership, critical-to-quality characteristics, controls, standard work, documentation and performance indicators. It also considers bottlenecks, waste, failure points, digital applications and the conditions required for effective standardization.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Explain process thinking and distinguish processes from departments and isolated tasks.

2. Construct and interpret SIPOC diagrams, flowcharts, value-stream maps and service blueprints.

3. Identify process customers, suppliers, inputs, outputs, bottlenecks, waste and failure points.

4. Define critical-to-quality characteristics and select suitable process controls and indicators.

5. Explain process ownership and the role of standard work in TQM.

6. Develop useful process documentation without creating unnecessary bureaucracy.

7. Evaluate process performance using measures such as yield, cycle time, first-pass yield, capability and customer-related indicators.

8. Apply process-management principles to production and service situations while considering risk, ethics, technology and continual improvement.

From Departmental Thinking to Process Thinking

A department is an organizational grouping of people and resources. A process is a flow of work that crosses organizational boundaries to produce a result. The distinction is fundamental. A purchasing department may achieve its internal target of processing purchase orders quickly, while production suffers because orders are released with incomplete specifications. A customer-service department may answer calls promptly, while customers remain dissatisfied because the underlying problem is not resolved. Local efficiency can therefore coexist with poor end-to-end performance.

Process thinking begins with five questions:

• Who is the customer of the process?
• What result does the customer require?
• What inputs are necessary to produce that result?
• How does work flow from beginning to end?
• How will conformity and performance be demonstrated?

The customer may be external, such as a buyer receiving a finished product, or internal, such as assembly receiving accurately prepared components. Quality is defined by requirements, and requirements must be translated into observable characteristics. For example, “fast delivery” is too vague for process control. It may be translated into an order-to-dispatch time of less than 48 hours, with a specified percentage of orders meeting that target.

A process has boundaries. The starting point might be receipt of a customer order, and the endpoint might be confirmed delivery. If boundaries are too narrow, important causes remain outside the analysis. If they are too broad, the process becomes difficult to understand and control. Defining boundaries is therefore a managerial judgement that should reflect the decision being made.

Processes may be classified as core, support or management processes. Core processes directly create customer value, such as product design, production, order fulfilment and service delivery. Support processes enable core processes, including maintenance, training, information technology and purchasing. Management processes establish direction and control, including strategic planning, risk management, auditing and performance review. The classification is useful, but processes are connected; quality improvement should not create gains in one process by damaging another.

Mapping a Process Before Improving It

Process mapping is not merely a drawing exercise. It is a method of making assumptions, handoffs, delays and decision points visible. A map should be developed with people who perform the work, people who receive its output and, where possible, people who experience the process as customers. The map should represent actual work rather than an idealized procedure. Comparing the actual and intended processes often reveals undocumented workarounds and control weaknesses.

SIPOC: Establishing the Process Boundary

SIPOC stands for Suppliers, Inputs, Process, Outputs and Customers. It is a high-level map used at the beginning of an improvement effort. It prevents premature attention to individual tasks before the team understands the overall process.

A SIPOC for order fulfilment might include:

• Suppliers: sales, customers, inventory records, approved vendors and logistics providers.
• Inputs: customer order, product specification, credit approval, available stock and delivery address.
• Process: validate order, confirm availability, pick and pack, dispatch, update records and confirm delivery.
• Outputs: correctly supplied product, dispatch information, invoice and customer confirmation.
• Customers: the purchasing customer, finance, warehouse and customer service.

The SIPOC should identify a small number of major process stages rather than every activity. Inputs and outputs should be expressed as tangible items or information. A useful SIPOC also indicates input and output requirements, because an input that is technically present but inaccurate or late can still cause process failure.

Flowcharts and Cross-Functional Maps

A flowchart describes the sequence of activities, decisions and movement of information or materials. Standard symbols commonly distinguish activities, decisions, documents, data and start or end points. The value of a flowchart lies less in the symbols than in the questions it prompts: Where does the work wait? Who makes the decision? What happens when the answer is no? Is the same information entered more than once? Which step detects an error, and where was the error created?

A cross-functional or swim-lane flowchart places activities in lanes representing departments, roles, systems or organizations. It is especially useful for identifying handoffs. Handoffs are risk points because information may be lost, interpreted differently or delayed. A process with many handoffs may require clearer specifications, integrated systems or a different process design.

Flowcharts should distinguish between value-adding, necessary but non-value-adding and avoidable activities. Inspection, for example, may not add physical value to a product but can be necessary while a process is being stabilized. Repeated inspection caused by unreliable work is usually a symptom of a larger problem, not a sustainable quality strategy.

Value-Stream Mapping

Value-stream mapping (VSM) examines the flow of material and information across an entire value stream. It is associated with lean management and is particularly useful for exposing waiting, excess inventory, transport, overprocessing, defects, overproduction and underused human capability. A current-state map records how the process actually operates; a future-state map proposes a more effective flow.

Important VSM measures include customer demand or takt time, processing time, waiting time, inventory levels, changeover time, uptime and first-pass yield. Takt time represents the available production time divided by customer demand. It is a planning rhythm, not a target to be achieved by working unsafely or sacrificing quality. If total lead time is several days but actual processing time is only a few minutes, the major improvement opportunity lies in waiting, batching, queues or information delays.

A value-stream map should not be used mechanically. Reducing inventory without improving supplier reliability or process stability can create shortages. Similarly, forcing every operation to run at the same speed may increase work-in-process rather than improve flow. The map must be interpreted in relation to demand patterns, constraints, product variety and process capability.

Service Blueprints

A service blueprint extends process mapping to services in which the customer participates in or observes delivery. It commonly distinguishes customer actions, visible employee actions, backstage activities, support systems and physical or digital evidence. For a hospital appointment, customer actions may include booking and arriving; front-stage actions include registration and consultation; backstage activities include record retrieval and scheduling; support processes include information systems and billing.

The blueprint helps identify moments of truth, where the customer forms a judgement about quality. It also reveals failures that a conventional production map may overlook, such as unclear communication, inconsistent employee discretion, inaccessible interfaces or a gap between a promised and an actual service.

Process Ownership and Governance

A process owner is accountable for the performance and improvement of an end-to-end process. Ownership is not identical to supervision. A supervisor may manage employees within one department, whereas a process owner coordinates across functions and is accountable for the result experienced by the customer.

Effective process ownership requires authority, information and resources. If a person is held responsible for delivery time but cannot influence scheduling, inventory policy or transport arrangements, ownership is nominal rather than real. Senior management should define the owner’s decision rights, escalation routes and relationship with functional managers.

A process governance arrangement generally includes:

• a defined process purpose and scope;
• identified customers and requirements;
• a process owner and accountable management sponsor;
• documented inputs, outputs and interfaces;
• agreed performance indicators and review frequency;
• risk, compliance and change-control arrangements; and
• a mechanism for corrective action and continual improvement.

Process owners should avoid optimizing one indicator at the expense of the whole system. For example, minimizing manufacturing cost may increase warranty claims; maximizing utilization may increase queues and lead time. Balanced performance review is therefore essential.

Critical-to-Quality Characteristics and Process Controls

A critical-to-quality (CTQ) characteristic is a measurable feature that is essential to meeting a customer, regulatory or process requirement. CTQs may relate to dimensions, strength, reliability, accuracy, delivery time, completeness, safety, responsiveness or user experience. A customer statement such as “the product must be dependable” must be translated into measurable requirements such as failure rate, operating life or on-time performance.

CTQ development commonly follows a chain:

Customer need → quality requirement → measurable characteristic → specification or target → method of measurement → process control.

For example, the need for a leak-free container may become a pressure-retention requirement, a maximum permissible leakage rate, a defined test method and a control plan for sealing temperature and pressure.

Controls can be preventive, detective or corrective. Preventive controls act before failure, such as mistake-proofing, approved specifications, operator training and controlled software permissions. Detective controls identify nonconformity, such as inspection, alarms, automated tests and audits. Corrective controls contain and remove the cause, such as segregation, adjustment, maintenance and corrective-action analysis. A mature process relies primarily on prevention rather than attempting to inspect quality into the output.

A control plan should specify the characteristic being controlled, the process step, the measurement method, acceptance criteria, frequency, responsible role, reaction plan and records required. Measurement systems themselves must be suitable. An inaccurate gauge can make a stable process appear unstable or conceal real variation. Measurement-system analysis is therefore relevant where decisions depend on measured data.

Standard Work: Converting Knowledge into a Reliable Method

Standard work is the documented, currently agreed method for performing a task safely, efficiently and consistently. It normally identifies the work sequence, the expected time or pace, required materials and equipment, quality points, safety requirements and abnormal-condition response. In repetitive production, standard work may also specify standard work-in-process and the relationship between operator movement and machine cycle.

Standard work has three purposes. First, it reduces unwarranted variation. Second, it provides a baseline for training and auditing. Third, it enables improvement: without a defined current method, it is difficult to determine whether a change has produced a genuine benefit.

Standardization must not be confused with rigid bureaucracy. A standard should be clear enough to guide performance and flexible enough to accommodate legitimate variation. Employees should participate in developing standards because they possess practical knowledge about equipment, sequence, hazards and exceptions. A document prepared without worker involvement is likely to be ignored or followed only during audits.

A robust standard-work document answers the following questions:

1. What is to be done, and in what sequence?

2. What are the critical quality and safety points?

3. What tools, materials, settings and information are required?

4. What is the normal cycle or response time?

5. What should the employee do when conditions are abnormal?

6. Who approves, reviews and revises the standard?

Visual work instructions, photographs, diagrams, digital prompts and short videos can improve usability, but technology cannot compensate for an unclear process. Documents should have controlled identification, revision status, effective date, approval and withdrawal arrangements. Obsolete instructions must be removed from points of use.

Finding Bottlenecks, Waste and Failure Points

A bottleneck is a resource or stage that constrains the capacity of the entire process. It may be a machine, approval, specialist, information system or supplier. Bottlenecks are identified through queues, persistent high utilization, long waiting times, missed delivery commitments and accumulation of work before a particular stage. Increasing activity before the bottleneck usually increases work-in-process rather than output.

A practical approach is to exploit the constraint by ensuring that it performs only value-creating work, subordinate other activities to its capacity, elevate its capacity where justified and then reassess the system after the constraint moves. This logic reflects the Theory of Constraints, but it must be balanced with quality and safety requirements.

Waste is any consumption of resources that does not contribute to the required customer outcome. Common categories include defects and rework, overproduction, waiting, unnecessary transport, excess processing, inventory, motion and underuse of knowledge. Waste analysis should not assume that every non-value-adding activity can be eliminated immediately. Regulatory checks, essential maintenance and certain inspections may be necessary. The question is whether the activity is necessary, effective and performed at the appropriate point.

Failure points may be analyzed using Failure Mode and Effects Analysis (FMEA). For each potential failure mode, a team considers the effect, cause, existing controls and relative risk. Traditional risk-priority scoring uses severity, occurrence and detectability, although organizations should avoid treating a numerical score as a substitute for judgement. High-severity failures, safety risks and weak preventive controls deserve attention even when occurrence is currently low.

Measuring Process Performance

A process indicator should support a decision. A large number of measures can obscure rather than improve control. Useful indicators usually cover quality, delivery, cost, flexibility, safety, people and customer experience.

Common measures include:

• First-pass yield: the percentage of units meeting requirements without rework.
• Rolled throughput yield: the probability that a unit passes all stages without defect or rework.
• Cycle time: the time required to complete a process or defined activity.
• Lead time: elapsed time from customer request or order to fulfilment.
• On-time delivery: the proportion of deliveries meeting the agreed date or window.
• Process capability: the relationship between process variation and specification limits.
• Cost of poor quality: internal and external failure costs, including rework, scrap, returns and complaints.
• Overall equipment effectiveness: a combined view of availability, performance and quality for suitable equipment contexts.

Indicators should have operational definitions. “On-time delivery” must state whether the promise date is the original date, revised date or customer-requested date. “Defect rate” must define the unit of measurement and whether reworked units are counted. Indicators should also be segmented by product, shift, supplier, customer or process family when aggregate data conceals important variation.

A target is not automatically a control limit. Statistical process control distinguishes routine, common-cause variation from unusual, special-cause variation. Managers should avoid tampering—making frequent adjustments in response to ordinary fluctuation—because it can increase instability. When a process is stable but incapable of meeting specifications, the system requires redesign or variation reduction. When it is unstable, causes must first be investigated and removed.

Documentation, Digital Systems and Change Control

Process documentation may include policies, procedures, work instructions, forms, specifications, control plans, records, process maps and training materials. The purpose is to preserve organizational knowledge, communicate requirements, demonstrate conformity and support improvement. Documentation becomes harmful when it is excessive, inaccessible, inconsistent or disconnected from actual work.

Document control should ensure that the right version is available at the point of use, changes are authorized, obsolete versions are removed and records are retained according to organizational and regulatory requirements. Changes to processes should be assessed for effects on quality, safety, capacity, training, suppliers, software and customer commitments.

Digital manufacturing execution systems, workflow platforms, enterprise resource planning systems, sensors and process-mining tools can support process management. Process mining reconstructs actual flows from event logs and can reveal variants, delays and rework that are absent from formal procedures. Sensors and analytics can enable condition monitoring and predictive maintenance. Artificial intelligence may assist with anomaly detection, demand forecasting, document search and decision support.

These technologies introduce risks. Poor master data can automate incorrect decisions. Algorithms may embed bias or produce explanations that operators cannot evaluate. Cybersecurity failures can interrupt production or compromise customer and process data. Automation should therefore be governed through access control, validation, cybersecurity measures, human oversight, audit trails and clear accountability. A digital process is not necessarily a good process; automation can merely accelerate waste.

Illustrative Case: Stabilizing a Medical-Device Assembly Process

Background

The following is an illustrative case. A medical-device manufacturer assembles disposable infusion sets through cutting, component preparation, subassembly, final assembly, testing and packaging. The company has an established quality system, but customer complaints about missing components and delayed deliveries have increased.

Situation and Problem

The production manager initially attributes the problem to operator carelessness. However, a cross-functional team maps the process. The SIPOC shows that component kits are supplied by a separate warehouse, while the flowchart reveals three handoffs between warehouse, assembly and quality assurance. A value-stream map shows that actual assembly time is less than one hour, but orders spend two days waiting for kit verification and release. The service impact is significant because hospitals receive incomplete shipments and must place urgent replacement orders.

The team defines two CTQs: complete component kits at the point of assembly and shipment within the promised lead time. A review of records shows that first-pass yield is low at the kit-verification stage, although the defect data had previously been reported only at final inspection. FMEA identifies wrong component quantity and incorrect component identity as high-risk failure modes. Existing controls are primarily final inspection, which detects problems late.

Approach and Solution

The process owner establishes a cross-functional governance group involving warehouse, production, quality, planning and customer service. The team redesigns the handoff using a standard kit list linked to the production order. Barcode scanning provides positive identification of components, while a simple mistake-proofing feature prevents confirmation until the required quantity has been scanned. The control plan specifies scan accuracy, kit completeness, verification frequency and a reaction plan for discrepancies.

Standard work is developed with warehouse and assembly employees. It includes the sequence for picking, scanning, staging, reporting abnormalities and releasing a kit. A visual status board distinguishes kits awaiting information from kits ready for production. The production schedule is adjusted so that the constraint—kit verification during the peak period—is protected from avoidable interruptions.

The team also revises performance indicators. In addition to final defect rate, it monitors kit first-pass yield, waiting time before release, assembly rework, on-time shipment and customer complaints. Daily review is used for immediate abnormalities, while monthly review considers systemic trends and process capability.

Outcome

The principal improvement is not a single inspection device but a change from late detection to prevention at the point where the error could be created. The process becomes easier to understand because ownership, CTQs, controls and abnormal responses are explicit. The organization also learns that its previous final-inspection metric concealed an upstream problem.

Learning Points

The case illustrates five principles. First, quality problems should be traced through the entire process rather than assigned prematurely to individuals. Second, process maps expose waiting and handoff risk. Third, CTQs convert customer requirements into controllable characteristics. Fourth, standard work is most effective when developed with those who perform the task. Finally, indicators should locate failure, not merely report failure at the end of the system.

Challenges, Risks and Common Mistakes

Process management can fail when the organization maps only the official process. Actual work often includes informal approvals, spreadsheets, re-entry of data and workarounds. Observation and employee interviews are therefore essential.

Another mistake is confusing documentation with control. A detailed procedure does not ensure compliance, capability or customer value. Standards must be usable, trained, audited intelligently and revised when evidence changes. Excessive documentation can encourage ceremonial compliance, in which employees complete records without improving the process.

Organizations also frequently select indicators that are easy to count rather than important to customers. Utilization, number of inspections or number of procedures may improve while delivery, reliability or first-pass quality deteriorates. Measures should be balanced and reviewed for unintended consequences.

Resistance to standardization is another challenge, particularly where standards are associated with surveillance or loss of professional judgement. Leaders should explain the purpose, involve employees, protect reporting of abnormalities and distinguish learning from blame. At the same time, deliberate disregard of safety or regulatory requirements cannot be excused as individual preference.

Ethically, process decisions must protect workers, customers and affected communities. Production targets must not encourage unsafe work, falsification of records or shipment of known nonconforming products. Traceability, confidentiality, data integrity and truthful reporting are professional obligations. Regulatory requirements may define mandatory controls, validation, records, training and change approval, particularly in sectors such as healthcare, aerospace, food and automotive production.

Current Developments and Best Practices

Contemporary process management increasingly combines lean thinking, Six Sigma, risk-based thinking, operational excellence and digital analytics. Organizations are moving from static procedure manuals toward visual, role-based and digitally accessible standards. Real-time dashboards link process indicators with production orders, equipment status and customer commitments. Digital twins and simulation can test capacity and layout changes before physical implementation, although their usefulness depends on valid models and data.

Several practices consistently strengthen process management:

• Begin with customer requirements and define the process boundary clearly.
• Map the actual process with the people who perform and receive the work.
• Assign one accountable owner for end-to-end performance.
• Translate important requirements into measurable CTQs.
• Prefer prevention, mistake-proofing and process capability to dependence on final inspection.
• Keep standard work visible, current and easy to use.
• Measure flow, quality, cost, delivery, safety and customer outcomes together.
• Separate common-cause variation from special-cause events before taking action.
• Use risk analysis to prioritize controls, especially for high-severity failures.
• Treat every improvement as a controlled change and verify that gains are sustained.

Chapter Summary

Process management views quality as the outcome of linked activities rather than isolated departmental effort. SIPOC establishes process scope; flowcharts reveal sequence, decisions and handoffs; value-stream maps expose material, information and waiting losses; and service blueprints explain customer-facing and backstage interactions. Process ownership provides accountability across functional boundaries.

Critical-to-quality characteristics translate customer and regulatory requirements into measurable features. Control plans, preventive controls, suitable measurement systems and risk analysis help maintain conformity. Standard work defines the current best-known method, supports training and creates a baseline for improvement. Bottleneck analysis, waste identification, FMEA and balanced performance indicators help managers understand process behaviour and prioritize action. Documentation and digital systems strengthen control when they are accurate, accessible and governed, but automation cannot correct a poorly designed process. Effective standardization is therefore dynamic: it stabilizes work, enables learning and is revised when a demonstrably better method is established.

Key Terms

Process: A connected set of activities that transforms inputs into outputs for a customer.

Process thinking: Viewing work as an end-to-end flow rather than as isolated departmental tasks.

SIPOC: A high-level representation of Suppliers, Inputs, Process, Outputs and Customers.

Flowchart: A graphical representation of activities, decisions and sequence in a process.

Swim-lane map: A flowchart that assigns activities to roles, departments or systems.

Value-stream mapping: A method for analyzing material and information flow, including value-adding and waiting time.

Service blueprint: A map showing customer actions, visible service actions, backstage work and support processes.

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

Critical-to-quality characteristic: A measurable feature essential to satisfying a customer, regulatory or process requirement.

Control plan: A document specifying process controls, measures, frequencies, responsibilities and reaction plans.

Standard work: The documented, agreed method for performing work safely, consistently and effectively.

Bottleneck: A resource or stage that limits the capacity of the entire process.

Waste: Resource consumption that does not contribute to the required customer outcome.

First-pass yield: The proportion of units meeting requirements without rework.

Lead time: The elapsed time from the beginning of a customer-related process to its completion.

Process capability: The ability of a stable process to meet specified requirements.

Common-cause variation: Routine variation arising from the process system itself.

Special-cause variation: Non-routine variation attributable to a specific, identifiable event or condition.

FMEA: A structured method for identifying potential failures, effects, causes and controls.

Document control: Governance ensuring that approved, current and usable process information is available.

Review Questions

Short Answer Questions

1. Why can a department achieve its local target while the end-to-end process performs poorly?

2. What information does a SIPOC provide, and why is it prepared at a high level?

3. Distinguish between a CTQ and a general customer statement.

4. What are the three principal purposes of standard work?

5. Explain the difference between common-cause and special-cause variation.

Long Answer Questions

1. Explain how flowcharts, value-stream maps and service blueprints differ in purpose and application.

2. Discuss the responsibilities, authority and governance requirements of a process owner.

3. Describe how a control plan can convert customer requirements into operational controls.

4. Explain the role of standardization in continual improvement and discuss why standardization should not become bureaucracy.

5. Examine the benefits and risks of applying digital systems, process mining and AI to process management.

Analytical / Application Questions

1. A production line has high equipment utilization but increasing queues, overtime and late deliveries. How would you use process mapping and bottleneck analysis to diagnose the situation?

2. A service organization receives complaints about inconsistent response times even though average response time meets its target. Design a measurement and blueprinting approach to investigate the problem.

3. A factory relies on final inspection to detect recurring assembly errors. Propose a CTQ, risk-analysis, control and standard-work approach that shifts quality control toward prevention.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a process from a department?

A. A process is always performed by one department, while a department crosses organizations.

B. A process is an end-to-end flow that produces a result, while a department is an organizational grouping.

C. A process is concerned only with production, while a department is concerned only with services.

D. A process has no customer, while a department always has an external customer.

Correct Answer: B. A process is an end-to-end flow that produces a result, while a department is an organizational grouping.

Question 2

What is the principal purpose of a SIPOC diagram?

A. To calculate process capability for individual machines

B. To document every detailed task in a work instruction

C. To establish the broad boundaries, participants, inputs and outputs of a process

D. To replace all forms of process measurement

Correct Answer: C. To establish the broad boundaries, participants, inputs and outputs of a process

Question 3

A value-stream map shows two days of waiting but only one hour of actual processing. What does this most strongly suggest?

A. The process has no opportunity for improvement because processing time is low.

B. The main improvement opportunity may involve queues, batching or information delays.

C. Operators should work faster at every processing step.

D. Final inspection should be increased immediately.

Correct Answer: B. The main improvement opportunity may involve queues, batching or information delays.

Question 4

Which example is a critical-to-quality characteristic?

A. Employees should work harder.

B. Customers should receive excellent service.

C. Ninety-five percent of orders should be dispatched within 48 hours.

D. The department should improve communication.

Correct Answer: C. Ninety-five percent of orders should be dispatched within 48 hours.

Question 5

What is the most appropriate role of a process owner?

A. To supervise only employees in one functional department

B. To approve every individual work activity personally

C. To be accountable for end-to-end process performance across functional boundaries

D. To replace all functional managers

Correct Answer: C. To be accountable for end-to-end process performance across functional boundaries

Question 6

Which control is primarily preventive?

A. Final inspection after packaging

B. Customer complaint analysis after delivery

C. A barcode interlock that prevents use of an incorrect component

D. Sorting defective products from finished inventory

Correct Answer: C. A barcode interlock that prevents use of an incorrect component

Question 7

Why is standard work important for continual improvement?

A. It prevents all future changes to the process.

B. It provides a baseline against which proposed improvements can be evaluated.

C. It eliminates the need for employee knowledge.

D. It ensures that every process has the same cycle time.

Correct Answer: B. It provides a baseline against which proposed improvements can be evaluated.

Question 8

A manager adjusts machine settings after every small fluctuation in output, although the process is statistically stable. What problem may result?

A. Improved process capability through automatic adjustment

B. Tampering that increases process instability

C. Removal of all common-cause variation

D. A reduction in measurement-system error

Correct Answer: B. Tampering that increases process instability

Question 9

Which finding most clearly indicates a bottleneck?

A. A resource has occasional idle time and no queue before it.

B. A stage has persistent work accumulation and constrains total output.

C. A department has many documented procedures.

D. A product passes inspection on the first attempt.

Correct Answer: B. A stage has persistent work accumulation and constrains total output.

Question 10

What is a major governance risk when AI is used for process decisions?

A. It always reduces the need for data validation.

B. It guarantees unbiased and explainable decisions.

C. Poor data, opaque recommendations or inadequate human oversight may create uncontrolled errors.

D. It prevents all cybersecurity incidents.

Correct Answer: C. Poor data, opaque recommendations or inadequate human oversight may create uncontrolled errors.