Opening the book…
Processes rarely operate alone. The output of one process often becomes the input of another. Purchasing obtains a reagent, receiving checks and stores it, production uses it, and quality control tests the resulting product. A problem early in this chain can affect work much later.
These connections create interdependence, meaning that the performance of one part depends on other parts. If purchasing orders the correct chemical but the wrong grade, production may need to stop. If a storage unit fails overnight, a scheduled test may no longer have suitable materials. The employee who discovers the problem may be far from the activity where it began.
The quality functions introduced in Chapter 1 help support these relationships. Quality assurance (QA) focuses on planned activities that provide confidence requirements will be met. Quality control (QC) focuses on fulfilling requirements through operational activities, including testing and inspection. Continuous improvement uses evidence to strengthen performance over time. These functions connect prevention, detection, and learning, with responsibilities defined for the organization.
For the enzyme company, QA may help define the information required on a sample submission form. QC checks the enzyme against established specifications. An improvement team studies repeated sample delays and changes how the form is completed and checked. These activities support each other, but one cannot replace all the others.
A process owner is the person responsible for overseeing a defined process’s ongoing performance and coordinating needed changes. The owner may coordinate work across departments and help resolve gaps, while acting within assigned authority. Identifying an owner should make follow-up clear without transferring every technical or release approval to that person.
When investigating a problem, follow the movement of material and information. Ask what the next person needs, whether that need is clearly stated, and whether the previous process provides it. This approach supports accountability while avoiding the assumption that the last person handling the work caused the failure.
This page titled 5.2: Relationships among processes within a system was last modified on Fri, 06 Nov 2026 11:22:07 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by Emalee MacKenzie.
The book could not be loaded just now.