Operations, Quality, Supply Networks and Projects

Introduction

Operations management concerns the design, coordination and improvement of processes that transform resources into products and services. It is therefore central to leadership: strategy becomes real through capacity decisions, work systems, quality standards, supplier relationships, inventory policies and projects. A leader may formulate an excellent strategy, but customers experience that strategy through delivery reliability, product quality, responsiveness, cost and service.

This chapter integrates four closely related domains. Operations manages transformation processes and capacity. Quality management seeks consistent conformity and value for customers. Supply-network management coordinates flows across organisational boundaries. Project management delivers a temporary, distinctive outcome under constraints of scope, time, cost and risk. Lean and Six Sigma provide improvement disciplines, while critical-path and agile methods support project delivery.

The central managerial challenge is not simply efficiency. It is the design of a system that is productive, resilient, ethical and capable of learning. Local optimisation can damage the whole system: reducing inventory may increase stockouts, maximising machine utilisation may lengthen queues, and pressuring suppliers may create hidden quality or labour risks.

Learning Objectives

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

1. Explain operations as a transformation system and distinguish process, capacity, productivity and service-delivery decisions.
2. Map processes and diagnose waste, bottlenecks, variability and control failures.
3. Apply Lean, Six Sigma and quality-management principles appropriately.
4. Analyse inventory, supplier relationships and supply-network risk.
5. Use critical-path and agile approaches to plan and govern projects.
6. Evaluate operational decisions using financial, customer, employee, ethical and sustainability criteria.

1. Operations as a Transformation System

An operation converts inputs into outputs through activities, information, technology and human effort. Inputs may include materials, labour, capital, data, energy and customer participation. Outputs may be physical goods, services, decisions or experiences. The transformation may be physical, locational, informational, physiological or psychological.

A hospital transforms clinical knowledge, facilities, medicines and patient information into improved health. A bank transforms financial information and funds into payment, lending and risk-management services. A manufacturer transforms components into finished goods. In each case, the process has customers, suppliers, resources, controls and performance objectives.

The classic operations performance objectives are:

• Quality: doing things correctly and meeting requirements.
• Speed: reducing the time between request and delivery.
• Dependability: delivering as promised.
• Flexibility: adapting volume, variety, timing or specification.
• Cost: using resources economically without transferring costs to customers, workers or society.

These objectives interact. Flexibility may require excess capacity; speed may require additional resources; low cost may conflict with resilience. Effective leaders make trade-offs explicit rather than assuming that one measure represents performance.

Process types and process design

Processes may be classified by volume and variety. A low-volume, high-variety project is usually customised and resource-intensive. A jobbing or professional process handles distinct cases. Batch processes produce groups of similar items. Repetitive or mass processes produce standardised outputs at higher volume. Continuous processes operate with highly standardised flows, often involving liquids, chemicals or energy.

Service processes also differ in customer contact. High-contact services require attention to customer experience, emotional labour and recovery from failure. Low-contact services can often be standardised and automated. The distinction is not absolute: digital services may be technically standardised but highly visible to customers.

A process map makes work visible. A useful map identifies the sequence of activities, decision points, responsible roles, information inputs, queues, handoffs, controls and outputs. SIPOC—Suppliers, Inputs, Process, Outputs and Customers—is useful for establishing boundaries. A detailed flowchart or value-stream map reveals waiting, rework and unnecessary movement.

A process should be mapped as it actually operates, not as policy documents claim it operates. Leaders should observe work, interview people who perform it and compare the designed process with the experienced process.

2. Capacity, Flow and Productivity

Capacity is the maximum sustainable output of a process under stated conditions. It depends on resources, operating time, product mix, skills, maintenance, quality losses and demand patterns. Design capacity is theoretical maximum capacity; effective capacity recognises planned constraints; actual output reflects real performance.

Two basic measures are:

Utilisation and efficiency are percentages. They should not be confused: a process may operate at 80% of design capacity but 95% of effective capacity if maintenance and breaks reduce practical availability.

Productivity compares output with resources used:

Partial productivity may be measured as units per labour hour or revenue per machine hour. Multifactor productivity relates output to a weighted combination of labour, capital, materials and energy. Monetary measures require consistent prices and should be interpreted cautiously because price changes can appear as productivity changes.

Worked example: capacity and productivity

A service centre has design capacity of 1,200 cases per month. Planned staffing, breaks and maintenance reduce effective capacity to 1,000 cases. It completes 900 cases using 300 labour hours.

Utilisation is 900 ÷ 1,200 = 75%. Efficiency is 900 ÷ 1,000 = 90%. Labour productivity is 900 ÷ 300 = 3 cases per labour hour. These measures tell different stories: the centre has unused theoretical capacity, performs efficiently against practical capacity, and produces three cases per labour hour.

Bottlenecks and flow

A bottleneck is a resource whose capacity constrains total system output. Increasing capacity away from the bottleneck may have no benefit. The Theory of Constraints proposes five focusing steps: identify the constraint; exploit it; subordinate other activities to it; elevate its capacity; and repeat when the constraint moves.

Little’s Law links average inventory, throughput and flow time in a stable system:

Here, L is average work-in-process or items in the system, λ is average throughput rate, and W is average flow time. Units must be consistent—for example, cases, cases per day and days. The relationship applies when the system is stable over the period considered and items entering and leaving are appropriately comparable.

If a claims process completes 40 claims per day and the average claim remains in the system for 3 days, average work-in-process is 40 × 3 = 120 claims. Reducing work-in-process without reducing throughput generally requires reducing flow time; merely moving work to an unseen queue does not improve the system.

3. Lean Operations and Process Improvement

Lean is a management philosophy focused on customer value, smooth flow, pull, respect for people and continuous improvement. It does not mean indiscriminate cost cutting. Lean distinguishes value-adding work from necessary but non-value-adding work and avoidable waste.

Common forms of waste include defects, overproduction, waiting, unused talent, transportation, inventory, motion and over-processing. The categories are diagnostic prompts rather than a licence to remove controls. A regulatory inspection may be non-value-adding from the customer’s immediate perspective but necessary for safety.

Important Lean practices include:

• 5S: sort, set in order, shine, standardise and sustain.
• Standard work: the current best-known method, sequence and expected time.
• Visual management: making status and abnormalities visible.
• Kanban: a signal that authorises replenishment or movement in a pull system.
• Poka-yoke: mistake-proofing that prevents or detects errors.
• Kaizen: continuous, participative improvement.
• Value-stream mapping: analysis of material and information flow across a complete value stream.

Lean implementation fails when leaders treat tools as substitutes for capability, learning and psychological safety. Employees must be able to report problems without retaliation. Otherwise, visual systems merely expose problems that people learn to conceal.

4. Quality Management and Six Sigma

Quality has both conformance and fitness-for-use dimensions. Conformance asks whether output meets specified requirements; fitness for use asks whether it solves the customer’s problem reliably and safely. Quality is therefore designed into processes rather than inspected only at the end.

The Plan–Do–Check–Act (PDCA) cycle supports iterative learning. Plan the change and measures; implement it on an appropriate scale; check results against evidence; and act by standardising, adapting or abandoning the change. Six Sigma commonly uses DMAIC—Define, Measure, Analyse, Improve and Control—for improving an existing process. DMADV or related design-for-Six-Sigma approaches are more appropriate when designing a new process.

Variation and capability

Variation may arise from common causes inherent in a system or special causes associated with unusual events. A control chart distinguishes routine variation from signals requiring investigation. Managers should not tamper with a stable process in response to random fluctuation, nor ignore genuine special-cause signals.

For a process with lower and upper specification limits, LSL and USL, mean μ and standard deviation σ, the capability indices are:

These indices assume a stable, approximately normally distributed process and meaningful specification limits. C_p measures potential capability if centred; C_pk also considers displacement from the target. A high capability index cannot legitimise an unstable process or poorly chosen specifications.

Cost of quality

The cost of quality includes prevention costs, appraisal costs, internal failure costs and external failure costs. Investing in training, robust design and supplier development may increase prevention cost while reducing warranty, rework, complaint and reputational costs. Leaders should avoid the false choice between quality and productivity: well-designed quality often improves both.

Quality systems such as ISO 9001 emphasise a process approach, documented requirements, risk-based thinking, competence, monitoring, corrective action and continual improvement. Certification is not proof that every output is excellent; it indicates that an organisation has an assessed management system. Governance requires evidence, accountability and periodic review.

5. Inventory and Service Delivery

Inventory can buffer demand and supply uncertainty, decouple process stages, support economies of scale and protect customer service. It also creates holding cost, obsolescence, damage, theft, working-capital requirements and the risk that defects remain hidden. The managerial question is not whether inventory is good or bad, but what uncertainty it is buying protection against and at what cost.

The economic order quantity model illustrates the trade-off between ordering and holding costs:

Q* is the optimal order quantity, D is annual demand in units, S is ordering cost per order, and H is annual holding cost per unit. The basic model assumes known and constant demand, constant lead time, instantaneous replenishment, no quantity discounts and no stockouts. It is a benchmark, not a complete policy.

The reorder point under variable demand and constant lead time is often represented as:

where d is average demand per time period, L is lead time in the same time unit, and SS is safety stock. If demand during lead time is approximately normal and lead-time variation is ignored:

σ_L is the standard deviation of demand during lead time and z is the standard-normal service-factor associated with the desired cycle-service probability. This formula should not be used uncritically when demand is intermittent, lead time is highly variable or the cost of stockout is asymmetric.

Service operations

Service quality is shaped by reliability, responsiveness, assurance, empathy and tangible evidence. Because services are often produced and consumed simultaneously, customers may participate in the process and judge both outcome and experience. Service recovery—acknowledging failure, explaining it, correcting it and learning from it—is part of operations, not merely public relations.

Queue performance depends on arrival variability, service-time variability, number of servers and utilisation. High utilisation can be attractive financially but causes disproportionately long waits as the system approaches full capacity. Capacity planning should therefore examine peak demand, not only average demand.

6. Supply Networks

A supply network includes upstream suppliers, focal operations, logistics providers, distributors, customers and supporting information and financial flows. The term network is more realistic than “chain” because organisations commonly have multiple suppliers, shared suppliers and reciprocal relationships.

Key decisions include sourcing, make-or-buy, supplier selection, postponement, transport mode, facility location, inventory positioning and information sharing. Supplier evaluation should include quality, cost, delivery, innovation, financial health, cybersecurity, labour standards, environmental impact and business continuity.

The bullwhip effect occurs when order variability becomes greater upstream than customer-demand variability. Causes include forecast updating, order batching, price promotions, rationing and shortage gaming. Mitigations include sharing consumption data, reducing lead times, stabilising pricing, ordering in smaller lots and aligning incentives.

Resilience requires visibility, alternatives and recovery capability. A low-cost single-source network may be efficient in stable conditions but fragile under geopolitical disruption, natural disasters, cyberattacks or supplier insolvency. Leaders should assess probability, impact, detectability and recovery time, then decide whether to diversify, hold strategic inventory, redesign products, develop suppliers or accept the risk.

Ethical supply-network governance includes preventing forced labour, unsafe conditions, discrimination, corruption and misleading environmental claims. A supplier code of conduct is insufficient without risk-based due diligence, worker voice, credible audits, remediation and executive accountability. Purchasing targets must not encourage suppliers to violate standards.

7. Project Management

A project is a temporary endeavour undertaken to create a unique product, service or result. Operations are generally repetitive and ongoing; projects create or change the operating system. The distinction is useful but incomplete: projects eventually become operations, and operational data should inform projects.

Project governance establishes the business case, sponsor, decision rights, scope, benefits, risks, resources and escalation routes. A work breakdown structure decomposes deliverables into manageable work packages. A schedule identifies activities, dependencies, estimates and milestones. A risk register records probability, impact, response owner and status.

Critical-path analysis

In a precedence network, the critical path is the longest-duration path through the project. It determines the earliest possible completion under the stated relationships and estimates. Activities on the critical path have zero total float in the basic schedule.

For activity-on-node scheduling, the forward pass calculates:

ES is earliest start and EF is earliest finish. For an activity with predecessors, ES is the greatest predecessor earliest finish. A backward pass calculates latest times:

LF is latest finish and LS is latest start. Total float is:

These calculations assume deterministic activity durations and clearly defined precedence relationships. If duration or dependencies change, the critical path may change. Managers should monitor near-critical paths rather than focusing only on the original critical path.

Agile delivery

Agile methods are valuable when requirements are uncertain, learning is possible and stakeholders can provide frequent feedback. Work is organised into prioritised backlogs, short iterations, reviews and retrospectives. A product owner prioritises value; a delivery team creates the increment; and facilitation protects the improvement process. Agile is not the absence of planning or governance. It replaces excessive up-front certainty with incremental planning and evidence.

Agile is less suitable where requirements are fixed by law, physical construction dependencies are rigid, or late change is extremely costly—although agile practices may still support design, procurement or commissioning. Hybrid approaches combine predictive planning for fixed infrastructure with iterative development for uncertain components.

8. Integrated Performance and Technology

Operational dashboards should combine leading and lagging indicators. Examples include first-pass yield, on-time delivery, cycle time, forecast accuracy, inventory turns, schedule variance, incident rates, customer effort and employee suggestions implemented. Measures should have defined formulas, owners, data sources and review frequency.

Technology can improve operations through enterprise systems, Internet-of-Things sensors, digital twins, robotic process automation, advanced planning, predictive maintenance and AI-assisted forecasting. However, automation can reproduce biased decisions, create cybersecurity exposure and reduce human discretion inappropriately. AI outputs should be governed through data-quality controls, validation, explainability appropriate to the risk, access controls, monitoring and human accountability.

A useful principle is “automate after stabilising.” Automating a poorly understood process may accelerate defects. Leaders should first clarify the purpose, simplify work, establish controls and test whether technology improves outcomes for customers and employees.

Applied Case: Meridian Medical Supplies (Illustrative)

Background

Meridian Medical Supplies distributes sterile procedure kits to regional hospitals. Demand is seasonal, hospitals require high availability, and kits have expiry dates. The company experienced stockouts in peak months, excess inventory in slow months and repeated picking errors.

Problem and analysis

A process map showed that orders were entered manually, inventory data were updated in batches, and quality checks occurred only after picking. The packing area was the bottleneck. A value-stream review found long queues between picking and inspection. Supplier lead times varied substantially, but the replenishment policy used average lead time only. Procurement also placed large monthly orders to obtain discounts, increasing obsolescence.

The leadership team separated symptoms from causes. A Pareto analysis showed that a small number of kit types generated most stockouts. A control chart indicated that picking errors were associated with temporary staff and unclear location labels rather than random fluctuation.

Approach and solution

Meridian introduced barcode scanning at picking, standard work for temporary staff and mistake-proofed location labels. It moved quality checks closer to the point of picking and cross-trained employees for the packing bottleneck. For critical kits, reorder points were recalculated using demand during lead time plus safety stock. Suppliers received weekly consumption data rather than irregular large orders.

A cross-functional team established a DMAIC project. The project schedule used critical-path analysis for warehouse-system integration, while two-week iterations were used to test scanner workflows with warehouse employees. The team monitored first-pass accuracy, stockout frequency, expiry write-offs, order-cycle time and employee workload.

Outcome

After three months, picking accuracy improved, queues declined and stockouts of priority kits decreased. Inventory value did not fall immediately because safety stock was deliberately increased for highly uncertain items; later, better visibility allowed reductions in slow-moving stock. The project demonstrated that resilience and efficiency can improve together when decisions are based on process evidence rather than blanket inventory reduction.

Learning points

1. A bottleneck should be analysed in relation to the whole flow.
2. Inventory policy must reflect demand, lead-time variability and item criticality.
3. Quality at the source is more effective than discovering errors at the end.
4. Lean, Six Sigma, predictive scheduling and agile experimentation can complement one another.
5. Outcomes should include service, risk, cost and employee effects—not a single metric.

Challenges, Limitations and Managerial Judgement

Operations models simplify reality. EOQ ignores many commercial conditions; capability indices require stable distributions; critical paths depend on estimates; and productivity ratios can encourage harmful labour intensification. Leaders should therefore triangulate quantitative measures with observation, customer evidence and professional judgement.

Common implementation failures include imposing targets without capacity analysis, treating certification as performance, launching technology before process redesign, ignoring informal work, transferring risk to suppliers and confusing activity with value. Improvement also creates distributional effects: a faster process may increase workload, automation may displace roles, and lean staffing may reduce resilience. Ethical leadership requires consultation, fair transition support and attention to safety and dignity.

Best-Practice Principles

• Start with customer and stakeholder value, including safety and sustainability.
• Map the real process and identify the system constraint.
• Use a balanced set of operational, financial, people and risk measures.
• Stabilise and standardise before automating.
• Distinguish common-cause variation from special causes.
• Build quality into design and supplier relationships.
• Treat inventory as a risk-and-service decision, not merely a cost.
• Share information while protecting privacy and cybersecurity.
• Govern projects through clear benefits, scope, authority and escalation.
• Match predictive, agile or hybrid methods to uncertainty and reversibility.
• Create psychological safety so that problems become learning opportunities.

Chapter Summary

Operations management converts resources into products and services through processes whose performance depends on capacity, flow, quality, flexibility, dependability and cost. Process mapping, bottleneck analysis and Little’s Law help leaders understand flow, while utilisation, efficiency and productivity provide complementary measures.

Lean identifies waste and promotes pull, standard work, visual management and continuous improvement. Six Sigma and quality systems address variation, capability, prevention and corrective action. Inventory decisions balance service and uncertainty against holding and obsolescence costs. Supply-network leadership requires visibility, resilience, ethical due diligence and alignment across organisational boundaries.

Projects differ from ongoing operations but ultimately create or change them. Critical-path analysis supports schedule logic, while agile methods support iterative learning under uncertainty. Technology and AI can strengthen planning and control only when data, governance, human accountability and process design are sound. Effective leaders optimise the whole system rather than isolated metrics.

Key Terms

Agile: An iterative approach that delivers increments and adapts through feedback.

Bottleneck: A resource or activity that constrains total system output.

Capacity: The maximum sustainable output under specified conditions.

Capability index: A statistical comparison between process variation and specification limits.

Critical path: The longest-duration path determining minimum project duration.

DMAIC: Define, Measure, Analyse, Improve and Control improvement cycle.

Inventory: Materials, work-in-process or finished goods held in a system.

Kanban: A visual or electronic signal authorising replenishment or movement.

Lean: A philosophy focused on value, flow, pull, waste reduction and respect for people.

Little’s Law: Relationship between average inventory, throughput and flow time.

PDCA: Plan, Do, Check and Act cycle for learning and improvement.

Productivity: Output relative to input.

Quality: Conformance and fitness for intended use.

Safety stock: Inventory held to protect against uncertainty.

Supply network: Interconnected organisations and flows supporting delivery to customers.

Utilisation: Actual output as a proportion of design capacity.

Value-stream map: Representation of material and information flow across a value stream.

Work breakdown structure: Hierarchical decomposition of project deliverables and work.

Review Questions

5 Short Answer Questions

1. Distinguish design capacity, effective capacity and actual output.
2. What is the difference between a bottleneck and a queue?
3. Name the five Lean performance objectives or common forms of waste.
4. Why is safety stock used in inventory management?
5. What does the critical path indicate in a project schedule?

5 Long Answer Questions

1. Explain how process mapping, Lean and Six Sigma can be integrated in an improvement programme.
2. Discuss the advantages and limitations of using productivity as a management measure.
3. Explain how quality should be designed into operations rather than inspected only at the end.
4. Evaluate the major sources of supply-network risk and appropriate resilience responses.
5. Compare predictive, agile and hybrid project-management approaches.

3 Analytical / Application Questions

1. A service unit has design capacity of 2,000 cases per month, effective capacity of 1,600 and actual output of 1,440. Calculate utilisation and efficiency, then interpret the results.
2. A warehouse completes 50 orders per day and average order flow time is 2.5 days. Use Little’s Law to estimate average orders in the system. Identify one operational action that could reduce flow time.
3. Design an improvement plan for a hospital supply process experiencing stockouts, expiry losses and picking errors. Specify process measures, quality methods, inventory actions, project method and ethical risks.

Multiple Choice Questions with Answers

Question 1

Which measure compares actual output with effective capacity?

A. Utilisation

B. Efficiency

C. Productivity

D. Throughput time

Correct Answer: B. Efficiency

Question 2

A process completes 30 cases per day and the average case remains in the system for 4 days. Using Little’s Law, average work-in-process is:

A. 7.5 cases

B. 26 cases

C. 120 cases

D. 240 cases

Correct Answer: C. 120 cases

Question 3

Which Lean practice authorises replenishment through a signal?

A. Kanban

B. Pareto analysis

C. Benchmarking

D. Appraisal

Correct Answer: A. Kanban

Question 4

What does Cpk consider that Cp does not?

A. Annual demand

B. Process-centre displacement

C. Project duration

D. Supplier count

Correct Answer: B. Process-centre displacement

Question 5

In DMAIC, which phase investigates likely causes of performance problems?

A. Define

B. Measure

C. Analyse

D. Control

Correct Answer: C. Analyse

Question 6

The bullwhip effect refers to:

A. Lower customer demand caused by inflation

B. Increasing demand variability upstream in a supply network

C. A reduction in supplier lead time

D. A project schedule with no float

Correct Answer: B. Increasing demand variability upstream in a supply network

Question 7

If an activity has ES = 6 days and duration = 5 days, its earliest finish is:

A. 1 day

B. 5 days

C. 11 days

D. 30 days

Correct Answer: C. 11 days

Question 8

Which inventory formula is based on annual demand, ordering cost and holding cost?

A. ROP

B. EOQ

C. Cpk

D. PDCA

Correct Answer: B. EOQ

Question 9

Agile methods are especially useful when:

A. Requirements are uncertain and feedback is available

B. All requirements are legally fixed and immutable

C. No stakeholder can review outputs

D. The project has no deliverable

Correct Answer: A. Requirements are uncertain and feedback is available

Question 10

Which is an ethical supply-network practice?

A. Ignoring labour conditions below tier-one suppliers

B. Using price pressure regardless of safety consequences

C. Conducting risk-based due diligence and remediation

D. Treating certification as proof that no risk exists

Correct Answer: C. Conducting risk-based due diligence and remediation