Process Management and Quality Planning

Introduction

Total Quality Management (TQM) treats quality as the outcome of a managed system rather than the result of final inspection alone. A process converts inputs into outputs through people, methods, equipment, information, and controls. Process management therefore asks four connected questions: What is the process intended to achieve? How does work actually flow? Who owns its performance? How will conformity and improvement be demonstrated?

Process management is central to ISO 9001 because the standard requires an organization to determine, manage, monitor, and improve the processes needed for its quality management system (QMS). ISO 9001 does not prescribe one universal process map or organizational structure. It requires a risk-based, evidence-based system appropriate to the organization’s context, interested parties, products, and services. Quality planning translates strategic and customer requirements into operational objectives, responsibilities, resources, controls, and measurable acceptance criteria.

Learning Objectives

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

1. Explain process-based management and its relationship to TQM and ISO 9001.
2. Construct and critique SIPOC diagrams, flowcharts, and value-stream maps.
3. Define process ownership, interfaces, inputs, outputs, risks, and controls.
4. Develop a quality plan and control plan with measurable criteria.
5. Select useful process-performance indicators and distinguish leading from lagging measures.
6. Evaluate a process-management system through a realistic operational case.

1. Process Thinking in Quality Management

A process is a set of interrelated or interacting activities that transforms inputs into intended outputs. The transformation may be physical, informational, transactional, or service-based. A process is different from a department: departments are organizational units, whereas processes cross organizational boundaries to create value for a customer or other interested party.

A process-based view has several implications:

• The customer judges the output, not the internal organization chart.
• Poor quality frequently arises at interfaces, such as handoffs, approvals, or data transfers.
• Variation should be understood and controlled at its source.
• Process performance requires both local measures and end-to-end measures.
• Improvement must consider the system as a whole; optimizing one activity can damage total performance.

TQM adds a cultural and managerial dimension. It emphasizes customer focus, employee involvement, prevention, fact-based decision-making, supplier relationships, and continual improvement. ISO 9001 provides auditable requirements for a QMS, while TQM is a broader management philosophy. They are complementary but not identical: certification does not prove that an organization has achieved excellence, and a mature TQM organization may use practices beyond the minimum requirements of a standard.

A useful process model is the Plan–Do–Check–Act (PDCA) cycle:

• Plan: determine requirements, risks, objectives, methods, and resources.
• Do: perform the process under defined conditions.
• Check: measure results against criteria and review evidence.
• Act: correct problems, address causes, and improve the system.

The cycle is recursive. It applies to an entire QMS, a production line, a procurement process, or a single corrective action.

2. Process Architecture and Ownership

A process architecture is a structured view of how processes relate to one another. A typical architecture includes:

• Strategic or management processes: policy, strategy, risk management, and management review.
• Core or value-creating processes: marketing, design, production, delivery, and service.
• Support processes: human resources, information technology, maintenance, purchasing, and document control.
• Measurement and improvement processes: auditing, data analysis, corrective action, and improvement projects.

The hierarchy should be useful rather than excessively detailed. A practical hierarchy may include a value stream, major process, subprocess, activity, and task. The appropriate level depends on the decision being made. A senior executive may need an end-to-end map, while a technician may need a controlled work instruction.

Process ownership

A process owner is accountable for the capability and results of a process across departmental boundaries. Ownership is not necessarily the same as performing every task or being the line manager of every participant. The owner normally:

• defines the process purpose, scope, and interfaces;
• establishes performance objectives and acceptance criteria;
• ensures adequate people, competence, technology, and infrastructure;
• approves process documentation and controls;
• reviews risks, trends, incidents, and customer feedback;
• initiates corrective action and improvement;
• reports performance to appropriate governance forums.

A RACI matrix can clarify responsibilities. R means responsible for performing work, A means accountable for the result, C means consulted, and I means informed. Good governance normally requires one clearly accountable role for each major deliverable. Multiple “accountable” roles often create ambiguity; no accountable role creates neglect.

3. SIPOC: Establishing the Process Boundary

SIPOC stands for Suppliers, Inputs, Process, Outputs, and Customers. It is a high-level scoping tool, not a detailed operating procedure. It is particularly valuable at the beginning of improvement work because teams often disagree about where a process starts and ends.

A SIPOC is usually created from left to right or from the central process outward, then validated with customers and suppliers. It should contain enough detail to establish scope but not so much detail that it becomes a flowchart. For each output, the team should identify the customer’s critical-to-quality (CTQ) requirements, such as accuracy, timeliness, completeness, safety, reliability, or regulatory conformity.

A common weakness is treating internal activity completion as quality. For example, “invoice entered” is an activity; “invoice paid accurately within agreed terms” is an output with customer significance. The distinction encourages teams to define quality in terms of results.

4. Flowcharts and Process Analysis

A flowchart represents the sequence and logic of activities. Standard symbols are useful, but consistency and clarity matter more than artistic precision. Typical symbols include rectangles for activities, diamonds for decisions, arrows for flow, and rounded shapes for start or end points.

A professional flowchart should show:

• process start and end conditions;
• activities and responsible roles;
• decisions and decision criteria;
• rework loops, queues, and escalation paths;
• information and physical flows where relevant;
• controls, records, and system transactions;
• customer and supplier interfaces.

Two maps may be needed: an as-is map, which reflects actual work including workarounds, and a to-be map, which represents the designed future state. Confusing the two hides problems and creates unrealistic procedures.

Process analysis should distinguish value-adding work from necessary but non-value-adding work and pure waste. In a hospital admission process, identity verification may not transform the patient physically, but it is necessary for safety and legal compliance. A simplistic “remove everything that does not add value” approach can therefore be unsafe. The correct question is whether an activity is required by customer value, risk control, law, or organizational necessity, and whether it can be performed more effectively.

5. Value-Stream Mapping

Value-stream mapping (VSM) examines the end-to-end flow of material and information, especially in lean operations. It identifies demand, inventories or queues, process times, information signals, and sources of delay. VSM is broader than a local flowchart because it exposes the relationship between work centers and the overall delivery system.

Important measures include:

• Cycle time: elapsed time required to complete a process step under defined conditions.
• Lead time: elapsed time from customer request to delivery or completion.
• Waiting time: time during which the item is not being actively transformed.
• Process time: time spent performing work, which may or may not be value-adding.
• First-pass yield: proportion completed correctly without rework.

A simple flow-efficiency measure is:

Value-adding time and total lead time must use the same units and the same process boundary. The measure is descriptive, not a universal quality target. A low result may indicate excessive waiting, batching, approvals, transport, or rework, but it does not by itself identify the cause.

Worked example

An order spends 18 minutes in active processing and 162 minutes waiting or being transported. Total lead time is therefore 180 minutes. Flow efficiency is:

The result suggests that delay reduction may offer greater benefit than increasing operator speed. However, the organization must first confirm that the time observations represent normal demand and that safety and compliance controls are not being improperly removed.

VSM also supports capacity analysis. If a process must complete 480 units during an eight-hour shift, the required takt time, assuming the full shift is available, is:

Thus, 28,800 seconds ÷ 480 units = 60 seconds/unit. Takt time is a demand-related planning rate, not the actual cycle time of every operation. It should not be used as a substitute for capacity, quality, or safety analysis.

6. Standardization and Documented Information

Standardization means defining the best currently known method for achieving intended results under specified conditions. It does not mean freezing the process forever. A standard should be reviewed when requirements, technology, risks, or performance change.

Useful forms of documented information include:

• process maps and procedures;
• work instructions and visual standards;
• forms, checklists, and electronic records;
• specifications and acceptance criteria;
• maintenance, calibration, and inspection records;
• training and competence evidence;
• audit and corrective-action records.

Documentation should be proportional to risk and complexity. Excessive documentation creates administrative burden and encourages copying without understanding. Insufficient documentation produces inconsistent practice and weak evidence. Effective controlled information has a clear owner, revision status, approval, access rule, retention requirement, and method for preventing unintended use of obsolete versions.

Standard work should define the sequence, critical parameters, expected output, abnormal conditions, escalation rules, and required records. It should also identify the competence needed. A document cannot compensate for inadequate training, unsuitable equipment, or unrealistic workload.

7. Quality Planning

Quality planning is the process of determining the objectives, methods, resources, responsibilities, and controls needed to achieve specified results. It applies to products, services, projects, operational processes, and changes.

A robust quality plan answers the following:

1. What requirements must be met?
2. What outputs and CTQs demonstrate conformity?
3. Which process steps influence those requirements?
4. What risks could cause failure?
5. Who performs, verifies, approves, and escalates work?
6. What resources and competence are required?
7. What evidence will be retained?
8. How will performance be measured and improved?

Quality objectives

Objectives should be consistent with policy and customer requirements, measurable where practicable, communicated, monitored, and updated. A useful objective identifies the metric, baseline, target, time period, owner, data source, and response to deviation.

For example, “improve delivery” is weak. “Increase on-time delivery from 91% to at least 97% by the end of Q4, measured weekly against confirmed customer dates, with the logistics manager accountable” is operationally useful. The definition of “on time” must specify the reference date, treatment of partial deliveries, exclusions, and data source.

Common performance indicators include:

Indicators must be operationally defined. For example:

The numerator and denominator must refer to the same population and period. If units are re-inspected after rework and counted as accepted, the measure no longer represents first-pass yield.

A balanced measurement system combines outcome measures, such as complaints and defects, with process and leading measures, such as preventive-maintenance completion, error-proofing effectiveness, or training completion. Too many indicators diffuse attention; too few create blind spots.

8. Risk-Based Control Plans

A control plan links process steps, risks, controls, measurement methods, responsibilities, and reaction plans. It is more operational than a high-level quality plan. A typical control-plan row contains:

Controls may be preventive, detective, or corrective. Prevention includes design reviews, supplier qualification, poka-yoke, validated software, and controlled specifications. Detection includes inspection, testing, audits, and automated alerts. Corrective action addresses the cause after a failure. Prevention is generally preferable, but a layered system is often necessary for significant risks.

Failure Mode and Effects Analysis (FMEA) can support prioritization by examining failure modes, effects, causes, and existing controls. Traditional risk priority numbers multiply severity, occurrence, and detection ratings, but such products can obscure important differences and create misleading precision. Organizations should define rating scales, involve knowledgeable personnel, consider legal and safety consequences separately, and use the analysis to drive action rather than merely calculate a score.

Reaction plans are essential. “Monitor” is not a reaction plan. A useful plan states how to stop or contain the process, identify affected outputs, notify decision-makers, restore conformity, document the event, and determine whether corrective action or customer notification is required.

9. Process Performance and Statistical Thinking

A process measure should be interpreted with an understanding of variation. Common-cause variation is inherent in the current system; special-cause variation arises from unusual, identifiable conditions. A control chart can help distinguish these patterns when data are collected in time order and the chart is appropriate to the data type.

Process capability indices are useful only under suitable conditions, including a stable process, a meaningful specification, and an appropriate distributional assumption or validated alternative method. For a normally distributed, stable process with lower and upper specification limits LSL and USL, process capability is commonly summarized as:

where σ is the within-process standard deviation. This describes potential capability if the process is centered. Centering is reflected by:

where μ is the process mean. These indices are not percentages of conforming output, do not replace control charts, and should not be calculated from unstable data without qualification. Specification limits come from requirements; control limits are calculated from process data. Confusing these concepts is a frequent analytical error.

10. Integrated Applied Case: Reducing Order-Entry Errors

This is an illustrative case. A medium-sized industrial distributor receives orders through email, a web portal, and telephone calls. Customers complain about incorrect quantities and late confirmations. The company initially proposes training the order-entry team, but the quality manager recommends an end-to-end investigation.

Background and problem

The process begins when a customer submits an order and ends when an accurate confirmation is issued. A SIPOC exercise reveals that sales staff, customers, product master-data administrators, warehouse planners, and the enterprise system all influence the output. The customer’s CTQs are correct product, quantity, price, and confirmation within two hours.

Analysis

An as-is flowchart identifies manual transcription from email, ambiguous product descriptions, an approval queue for unusual discounts, and re-entry of data between systems. A two-week observation shows 120 orders with 15 requiring correction before confirmation. The first-pass yield is therefore:

The map shows that active entry takes about 12 minutes per order, but average lead time is 95 minutes because orders wait in queues. Interviews reveal that staff use personal spreadsheets to compensate for incomplete product data. This is a system-design problem, not simply an employee-carelessness problem.

Approach and solution

The process owner establishes a cross-functional team. The team standardizes product identifiers, introduces mandatory fields and validation rules in the portal, creates an exception path for genuinely unusual orders, and removes duplicate re-entry. A controlled work instruction defines the acceptance criteria and escalation rules. A dashboard reports first-pass yield, median confirmation time, exception volume, and customer complaints.

The control plan specifies automated validation for product and quantity, daily review of exceptions, weekly master-data checks, and monthly review by the process owner. Training is provided, but training is treated as one control among several rather than the entire solution.

Outcome and learning points

After implementation, the organization should verify results using the same definitions and comparable demand conditions. Suppose a subsequent sample contains 160 orders, of which 12 require correction. First-pass yield is (160 − 12) ÷ 160 × 100% = 92.5%. This improvement is encouraging but does not prove that the process is permanently capable. The team must examine stability, customer outcomes, unintended effects, and whether staff bypass controls during peak demand.

The case demonstrates five principles: define the end-to-end boundary; map actual work; address system causes; assign ownership; and connect controls to customer requirements and evidence.

11. Governance, Ethics, and Digital Technologies

Process governance should protect customers, employees, suppliers, and other interested parties. Quality data must not be manipulated to meet targets. Incentives based solely on speed can encourage concealment of defects or unsafe shortcuts. Organizations should preserve traceability, protect personal and commercially sensitive information, and define access rights and retention periods.

Digital workflow, sensors, process mining, robotic automation, and AI can improve visibility and prediction. Process mining can reconstruct actual process paths from event logs and identify loops, delays, and variants. AI may classify complaints, detect anomalies, or suggest likely causes. However, automated recommendations require validated data, monitoring for bias and drift, human oversight for consequential decisions, cybersecurity controls, and clear accountability. A dashboard is not a control unless data definitions, ownership, response thresholds, and escalation are established.

Contemporary process management increasingly integrates sustainability, resilience, and supply-chain risk. Quality planning may therefore include energy use, waste, worker safety, ethical sourcing, continuity scenarios, and climate-related disruptions where these affect requirements or organizational context.

Challenges and Limitations

Process management can fail when maps describe an idealized system rather than reality, when ownership is assigned without authority, or when metrics reward local optimization. Excessive standardization can suppress professional judgment, while insufficient standardization produces avoidable variation. Capability indices can be misused, risk scores can create false precision, and customer satisfaction measures can be distorted by low response rates. Improvement projects also fail when leaders do not provide time, resources, or consistent reinforcement.

The remedy is disciplined inquiry: observe work directly, involve process users and customers, validate definitions, test changes, examine unintended consequences, and review performance over time. Quality planning is not a one-time document; it is a management practice embedded in governance and learning.

Chapter Summary

Process management organizes work around end-to-end value creation rather than departmental activity. SIPOC establishes scope and stakeholders; flowcharts show sequence, decisions, interfaces, and rework; value-stream mapping exposes delay and information-flow problems. Process ownership assigns accountability across boundaries, while standardization converts reliable methods into controlled, reviewable practice.

Quality planning translates requirements into objectives, responsibilities, resources, measures, acceptance criteria, records, and reaction plans. Control plans connect risks to preventive and detective controls. Performance indicators must be clearly defined and interpreted with attention to variation, stability, and data integrity. ISO 9001 provides a process-based, risk-oriented framework, while TQM contributes a broader philosophy of customer focus, participation, prevention, and continual improvement. Effective systems combine documentation with competence, governance, ethical measurement, and evidence-based learning.

Key Terms

Process: Interrelated activities that transform inputs into outputs.

Process approach: Managing activities as a connected system of processes.

Process owner: Person accountable for the performance and improvement of a process.

SIPOC: High-level map of Suppliers, Inputs, Process, Outputs, and Customers.

Critical-to-quality (CTQ): Requirement or characteristic that strongly affects customer or stakeholder acceptance.

Flowchart: Diagram showing sequence, decisions, and process paths.

Value-stream mapping: End-to-end analysis of material and information flow.

Lead time: Elapsed time from process request or start to completion.

Cycle time: Time required to complete a defined process step.

Takt time: Available production time divided by customer demand.

Standard work: Documented best-known method for performing work under defined conditions.

Quality objective: Intended, measurable quality result established by the organization.

Control plan: Document linking process risks, controls, measures, owners, and reactions.

First-pass yield: Percentage completed correctly without rework.

Common-cause variation: Variation inherent in the existing process system.

Special-cause variation: Variation attributable to an unusual, identifiable condition.

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

Corrective action: Action to eliminate the cause of a nonconformity and prevent recurrence.

Documented information: Information an organization controls and maintains as evidence or operational guidance.

RACI: Responsibility matrix identifying responsible, accountable, consulted, and informed roles.

Review Questions

Short Answer Questions

1. What is the difference between a process owner and a department manager?
2. What is the primary purpose of a SIPOC diagram?
3. Distinguish lead time from cycle time.
4. Why must control limits not be confused with specification limits?
5. Name two characteristics of a useful quality objective.

Long Answer Questions

1. Explain how TQM and ISO 9001 complement but do not replace one another.
2. Describe how an organization should construct and validate an as-is process map.
3. Explain the elements of an effective control plan and reaction plan.
4. Discuss the benefits and limitations of value-stream mapping in a service process.
5. Critically evaluate the use of process capability indices in quality planning.

Analytical / Application Questions

1. A process has 240 completed orders, 18 of which required rework. Calculate first-pass yield and explain what additional evidence is needed before concluding that the process improved.
2. Design a SIPOC for a university course-registration process, including at least two CTQs and one likely interface risk.
3. A manager proposes measuring only employee training completion to control a high-risk process. Evaluate the proposal and recommend a balanced set of leading and lagging measures.

Multiple Choice Questions with Answers

Question 1

Which tool is primarily used to establish the high-level boundary of a process?

A. SIPOC

B. Control chart

C. RACI matrix

D. Fishbone diagram

Correct Answer: A. SIPOC

Question 2

In process governance, who is accountable for end-to-end process performance?

A. Every person performing a task

B. The process owner

C. The external auditor

D. The customer only

Correct Answer: B. The process owner

Question 3

A process has 18 minutes of value-adding time and 162 minutes of waiting or transport. What is its flow efficiency?

A. 5%

B. 10%

C. 18%

D. 90%

Correct Answer: B. 10%

Question 4

Which statement correctly distinguishes takt time from cycle time?

A. Takt time is based on customer demand; cycle time is the time required for a process step.

B. Takt time is always shorter than cycle time.

C. Cycle time is calculated only from customer complaints.

D. They are alternative names for specification limits.

Correct Answer: A. Takt time is based on customer demand; cycle time is the time required for a process step.

Question 5

Which measure counts units accepted without rework relative to all units entering the process?

A. Overall equipment effectiveness

B. First-pass yield

C. Lead-time efficiency

D. Supplier on-time delivery

Correct Answer: B. First-pass yield

Question 6

Which is the best example of a process output stated from the customer’s perspective?

A. Invoice entered into the system

B. Operator completed a checklist

C. Accurate invoice issued within agreed terms

D. Employee attended training

Correct Answer: C. Accurate invoice issued within agreed terms

Question 7

What is a necessary condition for meaningful use of process capability indices?

A. The process must be stable and specifications must be defined.

B. The process must have no customer requirements.

C. The data must be collected without time order.

D. Control limits and specification limits must be identical.

Correct Answer: A. The process must be stable and specifications must be defined.

Question 8

Which control is primarily preventive?

A. Sorting defective units after shipment

B. Customer complaint review

C. Automated validation that blocks an invalid product code

D. Corrective action after a failure

Correct Answer: C. Automated validation that blocks an invalid product code

Question 9

What is the main danger of using only departmental measures?

A. They always require statistical software.

B. They can optimize local activity while harming end-to-end performance.

C. They cannot be displayed in a dashboard.

D. They eliminate process ownership.

Correct Answer: B. They can optimize local activity while harming end-to-end performance.

Question 10

In a RACI matrix, the letter A denotes the person who is:

A. Assisting with the task

B. Auditing the task

C. Accountable for the result

D. Automatically informed by software

Correct Answer: C. Accountable for the result