4. Process and Systems Approach to Quality

Introduction and Context

Quality is not created by an inspection department at the end of a production line. It is created through the way work is designed, resourced, performed, controlled, measured, and improved. This observation is the foundation of the process and systems approach to quality management. It changes the central managerial question from “Which department is responsible for the defect?” to “Which process, interaction, condition, or decision allowed the defect to occur?”

Organizations are often represented through functional structures: marketing, purchasing, operations, finance, human resources, information technology, and quality. Functional structures are useful for allocating expertise and authority, but customers experience the organization differently. They encounter a sequence of activities that begins with a need and ends with a product, service, decision, or experience. That sequence commonly crosses several departments. A customer order, for example, may pass through sales, credit approval, planning, procurement, production, logistics, invoicing, and after-sales service. Quality depends not only on the performance of each function but also on the interfaces between them.

The process approach therefore views an organization as a network of interconnected processes that transform inputs into outputs. The systems approach extends this view by examining how processes interact as a whole, how they support organizational objectives, and how changes in one part of the system produce consequences elsewhere. Together, these approaches provide a foundation for quality management systems, risk-based thinking, operational control, performance measurement, continual improvement, and effective leadership.

Learning Objectives

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

1. distinguish process, functional, and systems perspectives;

2. explain the components and characteristics of a quality-relevant process;

3. model processes using SIPOC diagrams, flowcharts, and value-stream representations;

4. identify process owners, inputs, outputs, controls, interfaces, risks, and performance criteria;

5. analyse the relationship between individual processes and the wider management system;

6. apply process thinking to service, manufacturing, and administrative situations;

7. evaluate common weaknesses in process design and measurement; and

8. recommend practical and digitally enabled improvements while considering governance and ethical issues.

From Departments to Interacting Processes

A process is a set of interrelated or interacting activities that transforms inputs into intended outputs. The input may be physical material, information, a customer requirement, a request, a decision, or a combination of these. The output may be a manufactured item, a delivered service, a payment, an approved document, or information for a subsequent process.

A process is more than a list of activities. It has a purpose, a beginning and an end, a customer or recipient, resources, controls, criteria, and measurable results. For example, “process a customer complaint” includes receiving the complaint, recording it, classifying its urgency, investigating the cause, deciding on a response, communicating with the customer, and verifying closure. The process is complete only when the intended result has been achieved, not merely when an employee has completed a task.

The functional perspective groups people according to specialization. Its strengths include professional competence, efficient supervision, and clear technical communities. Its weakness is the risk of local optimization. A department may achieve its own target while damaging the end-to-end customer outcome. Purchasing may reduce unit price by selecting a distant supplier, while logistics and production experience longer lead times and more damaged material. A call centre may reduce average call duration, while unresolved customer problems increase repeat contacts.

The process perspective follows the flow of value and responsibility across functional boundaries. It asks what the customer needs, what sequence of work satisfies that need, where delays or errors occur, and how performance should be controlled. The systems perspective goes further. It considers the organization as an integrated arrangement of processes, resources, policies, leadership decisions, external providers, interested parties, and feedback mechanisms. It examines both vertical alignment with strategy and horizontal interaction across processes.

These perspectives are complementary rather than mutually exclusive. Functions provide expertise and capacity; processes provide flow and customer-oriented results; the system provides integration, direction, and learning.

Anatomy of a Process

A robust process description normally includes the following elements.

Purpose and scope. The purpose states why the process exists. Scope defines its boundaries, such as the point at which a request is accepted and the point at which the completed service is handed over.

Inputs and sources. Inputs include requirements, materials, data, equipment, human capability, approvals, and information from preceding processes. Each important input should have a source and acceptance criteria.

Activities and sequence. Activities describe what is done and in what order. The sequence may be linear, conditional, iterative, or parallel. Decision points should be visible rather than hidden in informal practice.

Outputs and recipients. Outputs are the results delivered to an internal or external customer. They should be described in observable terms, with requirements for completeness, accuracy, timeliness, safety, or conformity.

Resources. Resources include people, infrastructure, technology, facilities, documents, finance, and working conditions. Competence is a process resource, not merely an individual attribute.

Controls and criteria. Controls prevent, detect, or correct undesired results. Examples include specifications, approval rules, standard operating procedures, training, access restrictions, inspections, automated validations, and escalation thresholds.

Ownership and accountability. A process owner is accountable for the performance and improvement of the process across organizational boundaries. This differs from a task performer or departmental supervisor. Ownership must include authority to coordinate interfaces and obtain necessary resources.

Risks and opportunities. Process risks arise from uncertain conditions that may affect results, such as inaccurate data, supplier failure, equipment breakdown, unclear authority, or excessive workload. Opportunities include simplification, automation, prevention, and better use of information.

Performance criteria. Measures should reflect the intended result. Typical criteria include conformity, cycle time, first-pass yield, responsiveness, cost, reliability, customer experience, safety, and environmental performance. A measure is useful only when its definition, data source, frequency, responsibility, and decision rule are clear.

SIPOC as a Boundary-Setting Tool

SIPOC represents Suppliers, Inputs, Process, Outputs, and Customers. It is particularly useful at the beginning of process analysis because it establishes a shared high-level view before detailed mapping begins.

A SIPOC for a hiring process might identify recruitment agencies and internal managers as suppliers; an approved vacancy, job specification, and budget as inputs; screening, interviewing, selection, and offer activities as the process; a competent appointment and employment records as outputs; and the hiring manager, employee, payroll, and regulatory authorities as customers or recipients.

SIPOC is not intended to show every decision or handoff. Its value lies in clarifying boundaries and relationships. A team constructing a SIPOC should agree on the process name, start and end points, principal suppliers, critical inputs, major outputs, and recipients. It should then ask whether each input has a requirement and whether each output satisfies a customer need.

SIPOC also reveals hidden customers. In a laboratory testing process, the external customer may receive a report, while an internal medical or production decision-maker relies on its accuracy and timing. Recognizing both recipients prevents a narrow definition of quality.

Process Mapping and Value-Stream Thinking

Once the high-level boundary is agreed, a detailed process map can represent activities, decisions, documents, systems, roles, queues, rework loops, and handoffs. Flowcharts are suitable for logical sequence; swim-lane maps emphasize responsibility; cross-functional maps expose interfaces; and value-stream maps distinguish value-adding work from waiting, movement, inspection, inventory, and rework.

A useful map is neither a decorative diagram nor a transcription of an ideal procedure. It should represent the actual process, including workarounds and informal approvals. Analysts should validate it through observation, interviews, records, and data. The difference between the documented process and the performed process is often a significant source of risk.

Value-stream thinking asks how an order or request moves from demand to fulfilment. It distinguishes activities that transform the product or service in a way the customer values from activities that consume resources without increasing value. Some non-value-adding activities are nevertheless necessary for compliance, safety, or risk control. The objective is not to eliminate all controls but to make them proportionate, effective, and as close as possible to prevention rather than late detection.

For example, in invoice processing, entering the same information into three systems adds no customer value and creates opportunities for transcription error. A validated interface may remove duplication. By contrast, a segregation-of-duties approval may not add visible value to the invoice, but it protects organizational integrity and should not be removed without an equivalent control.

Interfaces, Handoffs, and Process Ownership

Interfaces are points at which information, materials, decisions, or responsibility pass between people, teams, processes, systems, or organizations. They are frequent locations of quality failure because assumptions are rarely visible at boundaries. An engineering team may issue a drawing without a revision status; production may use an obsolete version; quality may discover the issue only after inspection.

Effective interface design specifies what is transferred, in what format, by whom, when, with what acceptance criteria, and what happens when the requirements are not met. Service-level agreements, standard data fields, electronic workflow rules, confirmation messages, and escalation paths can all strengthen interfaces.

Process ownership prevents the “everybody and nobody” problem. A process owner should define objectives, coordinate resources, monitor results, manage risks, review customer feedback, and initiate improvement. Ownership does not mean that the owner performs every activity. It means that accountability for end-to-end performance is explicit.

RACI analysis can clarify roles: Responsible identifies who performs the work; Accountable identifies who owns the result; Consulted identifies those whose knowledge is needed; and Informed identifies those who must receive information. RACI is useful, but it should not replace judgement. Excessive consultation can slow a process, while multiple “accountable” parties can obscure decision rights.

Controls and Performance Criteria

Controls should be designed according to the nature of the risk. Preventive controls act before an error occurs, such as competence requirements, design reviews, supplier qualification, and automated range checks. Detective controls identify a problem after occurrence, such as inspection, reconciliation, audit, or complaint analysis. Corrective controls address the cause and prevent recurrence.

A mature quality system uses a hierarchy of control. It first seeks robust design and error prevention, then uses monitoring and detection as appropriate. Inspection alone is weak when the cost of failure is high or defects can escape to customers. For example, a mistake-proof fixture may be more reliable than relying solely on final inspection.

Performance criteria should combine leading and lagging indicators. A lagging indicator, such as customer complaints or warranty cost, shows an outcome after the event. A leading indicator, such as completion of preventive maintenance or response time to abnormal conditions, provides earlier information. Measures should be balanced: pursuing speed without accuracy, or cost without reliability, encourages dysfunctional behaviour.

A useful process dashboard may include:

• effectiveness: whether the intended result is achieved;
• efficiency: resources and time used relative to output;
• conformity: compliance with specified requirements;
• adaptability: ability to handle changing demand;
• risk: exposure to failure and control effectiveness; and
• stakeholder experience: satisfaction, trust, and accessibility.

Targets require interpretation. A process may meet its average cycle-time target while producing unacceptable variation for vulnerable customers. Statistical thinking therefore considers distributions, trends, special causes, and relationships between measures rather than relying only on averages.

Systems Thinking and Organizational Alignment

A system is a set of interacting elements that function as a whole. In quality management, the system includes processes, people, infrastructure, information, suppliers, policies, objectives, measurement, leadership, and feedback. System thinking discourages isolated solutions. Improving one process can create a bottleneck in another; reducing inventory can increase stock-out risk; accelerating approvals can weaken compliance if decision criteria are unclear.

Several concepts are central. Emergence refers to outcomes produced by interactions rather than by one component alone. Organizational reliability may emerge from communication, training, equipment design, and leadership behaviour. Feedback connects results to future action. Customer complaints, audit findings, process data, and employee suggestions can all provide feedback. Interdependence means that process performance is conditional on other processes and external parties. System boundaries determine what is included in analysis, but boundaries should not conceal significant dependencies.

Strategic objectives should cascade into process objectives. If the strategy emphasizes dependable delivery, planning, procurement, production, logistics, and customer service need aligned measures. A process map can therefore be used not only for operational analysis but also for strategic deployment. The management system should answer three questions: What results matter? Which processes create those results? How will leadership know whether the system remains capable?

Applying the Approach in Practice

Process analysis is most effective when it is conducted as a disciplined, cross-functional activity. A practical sequence is as follows:

1. Select a process based on customer importance, risk, poor performance, regulatory significance, or strategic priority.

2. Define its purpose, boundaries, owner, customers, and intended outputs.

3. Construct a SIPOC with representatives from relevant functions.

4. Observe and map the current state, distinguishing documented and actual practice.

5. Identify requirements, risks, controls, interfaces, delays, rework, and failure points.

6. Establish meaningful measures and a method for collecting reliable data.

7. Analyse causes using evidence rather than assigning blame.

8. Design improvements, test them on a controlled scale, and assess unintended effects.

9. Standardize successful changes and continue monitoring.

The sequence is iterative. Mapping may reveal that the process boundary is wrong; measurement may expose an unrecognized customer; and a proposed improvement may shift work or risk to another process.

In a hospital appointment process, for example, the objective is not merely to schedule patients. It is to provide timely access to the appropriate service with accurate information and safe handling of urgent cases. Inputs include referral information, capacity, patient preferences, and clinical priority. Outputs include a confirmed appointment, updated records, and information for clinicians. Performance criteria may include waiting time, appointment accuracy, missed-appointment rate, and correct escalation of urgent cases. An apparent scheduling delay may actually arise from incomplete referrals or unclear ownership of cancellations.

In manufacturing, a process approach links customer requirements to design, supplier control, production, inspection, release, delivery, and feedback. In financial services, it links customer onboarding, identity verification, risk assessment, account activation, transaction monitoring, and complaint handling. In public administration, it clarifies how policy intent becomes a transparent and accessible service. The principle remains the same: quality is an outcome of connected work.

Illustrative Case: Reducing Errors in a University Procurement Process

Background

The following is a fictional illustrative case. A university’s procurement process was formally compliant, yet academic departments frequently reported delayed equipment deliveries, incorrect purchase orders, and repeated requests for information.

Situation and Problem

The process crossed departments, procurement, finance, suppliers, and receiving. Each function met its local objective: departments submitted requests, procurement sought quotations, finance checked budgets, and stores recorded deliveries. However, the end-to-end cycle averaged six weeks, and 18 percent of orders required correction before payment.

Analysis

A cross-functional team prepared a SIPOC. The principal inputs were an approved specification, budget code, supplier information, and delivery requirement. The major output was a correct purchase order and accepted delivery. Mapping showed three important interface failures. First, departments used different descriptions for equivalent equipment. Second, finance returned requests because budget codes were missing or outdated. Third, procurement and stores used separate supplier and item identifiers.

The team also distinguished value-adding and non-value-adding work. Selecting an appropriate supplier and confirming technical requirements added value; re-entering descriptions and correcting incomplete forms did not. A RACI review showed that no person owned the complete process. Procurement was responsible for issuing orders but not for the quality of requests or delivery performance.

Approach and Solution

The university introduced a standard electronic request form with mandatory fields, a controlled catalogue for frequently purchased items, and automated validation of budget codes. A procurement process owner was appointed. The owner coordinated finance, stores, information technology, and academic representatives. A supplier identifier was standardized across systems, and an exception route was created for urgent research purchases.

Measures were revised to include request completeness at first submission, end-to-end cycle time, correction rate, on-time delivery, and user satisfaction. A pilot was conducted in two faculties before wider implementation. The team retained human approval for high-value purchases and conflict-of-interest declarations; automation was not allowed to replace governance controls.

Outcome

In the illustrative case, the pilot reduced avoidable corrections and shortened routine processing time. More importantly, departments gained visibility of request status, and unresolved exceptions had a named owner. The case demonstrates that process improvement did not result from asking staff to work faster. It resulted from clarifying requirements, strengthening interfaces, removing duplication, and aligning measures with the user’s outcome.

Learning Points

The case illustrates five lessons. First, functional compliance does not guarantee process effectiveness. Second, poor input quality creates downstream delay. Third, ownership must cross departmental boundaries. Fourth, digital automation is valuable only when the underlying process is understood. Finally, controls for integrity and accountability should be redesigned carefully, not eliminated in the pursuit of speed.

Challenges, Risks, and Common Mistakes

Process initiatives often fail when mapping becomes a documentation exercise detached from performance. Other common mistakes include designing the process from the policy rather than observing actual work; treating every activity as equally important; assigning ownership without authority; measuring departmental output instead of customer outcome; and using excessive indicators that no one reviews.

Over-standardization is another risk. Standard work is valuable where variation creates errors, but professional judgement is necessary in complex, uncertain situations. A process should specify decision criteria and escalation rather than force inappropriate uniformity. Conversely, excessive dependence on individual expertise creates fragility when people leave or workloads change.

Technology can amplify a poor process. Automating duplicate data entry may make duplication faster rather than remove it. Data quality, cybersecurity, access control, system availability, and change management must therefore be included in process design. Outsourcing does not remove responsibility: the organization must define requirements, monitor external providers, and manage interfaces.

There are also human risks. Process analysis can be perceived as surveillance or blame, producing defensive behaviour and inaccurate information. A learning-oriented culture treats errors as opportunities to understand system conditions while retaining accountability for negligence, fraud, or deliberate violations.

Governance, Ethics, and Professional Responsibility

Process decisions affect fairness, privacy, safety, accessibility, and public trust. Measures should not encourage employees to manipulate records, refuse complex customers, or prioritize easy cases merely to meet targets. Data used for performance management should be accurate, proportionate, transparent, and protected from unauthorized access.

Governance requires clear authority, documented decisions, segregation of incompatible duties, traceability, and effective escalation. Regulated processes may require retention of records, validation of systems, competency evidence, or formal change approval. Ethical process design asks not only whether a process is efficient, but also whether it is fair, explainable, safe, and respectful of affected people.

Digital Process Management and Emerging Practice

Digital process-management platforms can connect workflow, electronic forms, document control, dashboards, robotic process automation, and event logs. Process mining uses system records to reconstruct how work actually flows, identify variants, locate bottlenecks, and compare performance across cases. It is especially useful where documented maps differ from operational reality.

Artificial intelligence may assist classification, forecasting, anomaly detection, document extraction, and decision support. However, AI-based controls require validated data, defined accountability, monitoring for bias, protection of confidential information, and human review where consequences are significant. An algorithm should not become an unexamined process owner. Organizations must know what the system does, what data it uses, when it can fail, and how decisions can be challenged.

Current practice is moving toward end-to-end value-stream governance, integrated risk management, real-time operational visibility, and resilience measurement. Organizations increasingly examine not only efficiency but also their ability to absorb disruption, recover service, and learn from weak signals. These developments strengthen, rather than replace, the basic discipline of defining processes, interfaces, controls, and intended results.

Best-Practice Principles

Effective process and systems management is supported by several principles:

• begin with purpose and customer requirements, not with an existing department chart;
• define boundaries, ownership, inputs, outputs, and acceptance criteria explicitly;
• map actual work and validate it with the people who perform and receive it;
• manage interfaces as carefully as activities within departments;
• prefer prevention and robust design to dependence on final inspection;
• use a balanced set of outcome, process, risk, and experience measures;
• examine system-wide consequences before optimizing a local process;
• involve relevant functions, suppliers, users, and affected stakeholders;
• pilot changes and evaluate unintended effects; and
• preserve governance, ethical safeguards, and human accountability when using technology.

Chapter Summary

The process approach views quality as the result of interconnected activities that transform defined inputs into intended outputs. It complements the functional perspective by following value across departmental boundaries. The systems approach places those processes within a larger network of resources, leadership, suppliers, objectives, controls, feedback, and stakeholders.

SIPOC provides a high-level view of suppliers, inputs, process, outputs, and customers. Detailed process maps expose sequence, decisions, handoffs, rework, and responsibility, while value-stream analysis identifies delay and non-value-adding effort. Effective process design requires clear ownership, reliable inputs, suitable controls, defined interfaces, risk awareness, and meaningful performance criteria. Process improvement should be evidence-based, cross-functional, and tested for system-wide effects. Digital tools, process mining, automation, and AI can strengthen visibility and control, but they require sound process design, data governance, cybersecurity, ethical safeguards, and accountable human oversight.

Key Terms

Process: Interrelated activities that transform inputs into intended outputs.

Process approach: Managing work as a system of connected processes focused on intended results.

Systems approach: Understanding processes, resources, and interactions as an integrated organizational whole.

Functional perspective: Organizing and analysing work according to specialized departments or disciplines.

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

SIPOC: A high-level model showing Suppliers, Inputs, Process, Outputs, and Customers.

Input: Requirement, resource, material, information, or condition required by a process.

Output: Result produced by a process for a recipient or subsequent process.

Interface: Point where information, material, responsibility, or decisions pass between entities.

Process map: Visual representation of activities, sequence, decisions, roles, and relationships.

Value stream: End-to-end flow of activities required to deliver value to a customer.

Control: Measure or condition used to prevent, detect, or correct undesired outcomes.

Acceptance criterion: Requirement used to judge whether an input or output is suitable.

Leading indicator: Measure that provides early information about likely future performance.

Lagging indicator: Measure of an outcome after an event or process result has occurred.

RACI: Responsibility matrix identifying Responsible, Accountable, Consulted, and Informed parties.

Process variation: Difference in process behaviour or results across cases or time.

Process mining: Analysis of digital event data to reconstruct and evaluate actual process flows.

System boundary: Deliberately defined limit of the elements and interactions included in analysis.

Review Questions

Short Answer Questions

1. What distinguishes a process from a functional department?

2. What is the purpose of a SIPOC diagram?

3. Why are interfaces frequent sources of quality problems?

4. Distinguish preventive, detective, and corrective controls.

5. What is the principal responsibility of a process owner?

Long Answer Questions

1. Explain how functional, process, and systems perspectives complement one another in quality management.

2. Describe the elements that should be included in a complete process description.

3. Explain how value-stream thinking can identify improvement opportunities without eliminating necessary controls.

4. Discuss how performance criteria should be selected for an end-to-end process.

5. Analyse the role of governance, ethics, and human accountability in digitally enabled process management.

Analytical / Application Questions

1. A customer-service process meets its average response-time target, but repeat contacts and complaints are increasing. Use process and systems thinking to identify possible causes, measures, and improvements.

2. Construct a SIPOC and describe key interfaces for a university examination-results process. Identify at least three risks and suitable controls.

3. A company automates an approval workflow but discovers that errors and delays have increased. Diagnose the likely process-design weaknesses and propose a controlled improvement approach.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a process perspective from a functional perspective?

A. The process perspective eliminates the need for specialized departments.

B. The process perspective follows end-to-end value across organizational boundaries.

C. The process perspective measures only employee productivity.

D. The process perspective assigns all decisions to the quality department.

Correct Answer: B. The process perspective follows end-to-end value across organizational boundaries.

Question 2

In a SIPOC model, a completed purchase order delivered to a requesting department is primarily an example of a(n):

A. Supplier

B. Input

C. Output

D. Control

Correct Answer: C. Output

Question 3

Which situation most clearly represents an interface failure?

A. An operator follows a validated work instruction.

B. A department achieves its internal target for document processing.

C. A production team receives a drawing without the current revision status.

D. A manager reviews a process dashboard each month.

Correct Answer: C. A production team receives a drawing without the current revision status.

Question 4

What is the most appropriate role of a process owner?

A. Perform every activity in the process personally

B. Approve only departmental budgets

C. Be accountable for end-to-end performance and improvement

D. Replace all functional managers involved in the process

Correct Answer: C. Be accountable for end-to-end performance and improvement

Question 5

Which is the strongest example of a preventive control?

A. Final inspection after production

B. A customer complaint report

C. A design review conducted before production release

D. A warranty-cost analysis

Correct Answer: C. A design review conducted before production release

Question 6

A process has low average cycle time but very high variation for urgent customers. What does this suggest?

A. The average measure is sufficient for judging quality.

B. The process should be assessed using distribution and customer-segment information.

C. Variation is irrelevant if the process meets its average target.

D. The process has no performance problem.

Correct Answer: B. The process should be assessed using distribution and customer-segment information.

Question 7

Why should a process map represent actual practice rather than only the documented procedure?

A. Actual practice always complies with requirements.

B. Informal workarounds and hidden risks may be absent from formal documents.

C. Documentation is never useful for process analysis.

D. Employees should be allowed to change controls without approval.

Correct Answer: B. Informal workarounds and hidden risks may be absent from formal documents.

Question 8

In the illustrative procurement case, which change primarily reduced duplicate work and input errors?

A. Removing all financial approvals

B. Increasing final inspection of deliveries

C. Introducing validated electronic forms and standardized identifiers

D. Assigning every task to the procurement department

Correct Answer: C. Introducing validated electronic forms and standardized identifiers

Question 9

Which statement best reflects systems thinking?

A. Improving one department always improves organizational performance.

B. A process can be evaluated independently of suppliers and customers.

C. Changes in one process may create consequences in other parts of the organization.

D. Only technical processes form part of a management system.

Correct Answer: C. Changes in one process may create consequences in other parts of the organization.

Question 10

When AI is used to support a high-consequence process decision, which practice is most appropriate?

A. Allow the algorithm to operate without review once deployed.

B. Ignore data quality because automation removes human bias.

C. Define accountability, monitor performance and bias, and retain appropriate human oversight.

D. Use the system’s output as an unquestionable acceptance criterion.

Correct Answer: C. Define accountability, monitor performance and bias, and retain appropriate human oversight.