Advanced Operations Management

Chapter 15
Operations Governance and Performance Leadership

Advance Diploma in Operations management
Advanced Operations Management   •   Advance Diploma

Operations Governance and Performance Leadership

Introduction

Operations governance is the system through which an organisation directs, controls, monitors and improves the delivery of products and services. It connects strategy with daily decisions. Performance leadership is the human and managerial capability required to make that system effective: setting priorities, aligning teams, resolving trade-offs, holding people accountable and learning from results.

In advanced operations management, performance cannot be understood as cost or output alone. A process may achieve high productivity while creating safety risks, regulatory breaches, poor employee experience or unacceptable environmental damage. Effective governance therefore creates a balanced view of performance and establishes the policies, controls, information flows and behaviours that sustain it.

This chapter examines how managers design balanced performance systems; govern policies, compliance and accountability; lead cross-functional and operational change; respond to ethical dilemmas; manage stakeholder expectations; and conduct continuous strategic review.

Learning Objectives

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

  1. Explain the relationship between operations strategy, governance and performance leadership.
  2. Design a balanced performance-management system using financial, customer, process, people, risk and sustainability measures.
  3. Distinguish policies, procedures, controls, assurance and accountability.
  4. Apply governance frameworks to compliance, operational risk and ethical decision-making.
  5. Lead cross-functional teams and operational change.
  6. Interpret performance information and conduct strategic reviews.
  7. Evaluate the limitations and unintended consequences of performance metrics.

1. Governance as the Operating System of Management

Governance is not synonymous with administration or bureaucracy. It is the distribution of authority and responsibility by which decisions are made, challenged, implemented and reviewed. In operations, governance answers six questions:

  • What outcomes matter?
  • Who has authority to decide?
  • What standards and policies constrain decisions?
  • What evidence demonstrates that work is under control?
  • Who is accountable when performance deviates?
  • How are learning and corrective action built into the system?

Management is primarily concerned with planning and executing work. Governance establishes the direction, boundaries and assurance mechanisms within which management operates. Leadership influences whether people treat those mechanisms as meaningful aids to performance or as obstacles to be bypassed.

A mature governance system combines three elements:

ElementMain purposeTypical evidence
DirectionDefine strategic outcomes and prioritiesStrategy, objectives, policies
ControlKeep activities within acceptable boundariesProcedures, approvals, segregation of duties, risk controls
Assurance and learningTest whether the system works and improve itAudits, reviews, investigations, corrective actions

Governance must be proportionate. Excessive approvals slow decisions and encourage informal workarounds; weak governance permits inconsistent decisions, hidden risk and unclear accountability.

A governance architecture

Operations governance architecture Strategy and purposevalue, priorities, risk appetite Policiesprinciples and boundaries Controlsprevent, detect, correct Accountabilityroles and decisions Operational executionpeople, processes, technology Performance, assurance and learning review and improve
Operations governance architecture linking strategy, controls, execution and assurance
Figure: Operations governance architecture linking strategy, controls, execution and assurance

Figure: Governance translates strategic intent into controlled execution and continuous learning.

2. Designing a Balanced Performance System

A performance system is the connected set of objectives, measures, targets, review routines, responsibilities and improvement actions used to guide operations. It is more than a dashboard. A dashboard reports information; a performance system explains what matters, why it matters, how it will be measured and what decisions follow.

2.1 From strategy to measures

A useful design sequence is:

  1. Clarify the organisation’s purpose and strategic choices.
  2. Identify the operational capabilities required, such as dependable delivery, flexibility, quality, innovation or low cost.
  3. Define outcomes and the drivers that influence them.
  4. Select a limited number of valid measures.
  5. Set targets, thresholds and owners.
  6. Establish review frequency and escalation rules.
  7. Test whether the measures produce desirable behaviour.

The Balanced Scorecard, associated with Kaplan and Norton, groups strategic performance into financial, customer, internal process, and learning and growth perspectives. In operations, these perspectives should be extended where relevant to safety, resilience, compliance, employee wellbeing and environmental impact.

A strategy map can express causal logic: employee capability and technology enable better processes; better processes improve customer outcomes; customer outcomes support financial and social value. The links are hypotheses rather than automatic laws and should be tested with evidence.

2.2 Leading and lagging indicators

Lagging indicators describe results after they occur: unit cost, customer complaints, accident frequency or on-time delivery. Leading indicators concern conditions that influence future results: preventive-maintenance completion, training competence, supplier risk reviews or the proportion of corrective actions closed on time.

A balanced system uses both. Lagging measures show whether objectives were achieved; leading measures help managers intervene before failure. However, a leading indicator is not valuable merely because it occurs earlier. It must have a plausible and monitored relationship with the outcome.

2.3 Metric quality

A measure should be assessed for:

  • Validity: does it represent the intended concept?
  • Reliability: would consistent measurement produce comparable results?
  • Timeliness: is information available soon enough to act?
  • Controllability: can the accountable manager influence it?
  • Comparability: are definitions and measurement boundaries stable?
  • Cost: is the value of information greater than its collection cost?
  • Behavioural effect: could the measure encourage gaming or harmful trade-offs?

Measures should have an operational definition. For example, “on-time delivery” should specify the promised date, the delivery event, treatment of customer-requested changes and the relevant population.

2.4 Core operational measures

Some commonly used measures are quantitative, but they should be interpreted in context.

Productivity compares useful output with resources consumed:

Productivity = Useful output ÷ Input

Output and input must be defined in compatible units, such as completed orders per labour hour. Productivity may increase because of automation, effort, demand mix or quality deterioration; therefore it should not be interpreted alone.

First-pass yield measures the proportion of units that meet requirements without rework:

FPY = Good units produced without rework ÷ Total units entering the process × 100%

On-time delivery rate is:

OTD = Orders delivered on or before the agreed date ÷ Orders due × 100%

The denominator should exclude only cases covered by a documented and consistently applied rule.

Capacity utilisation is often expressed as:

Utilisation = Actual output or busy time ÷ Available capacity or available time × 100%

The numerator and denominator must use the same basis. A high utilisation rate is not always desirable because it can reduce flexibility and increase queueing and disruption sensitivity.

Weighted scorecards can combine standardised measures, but weights are managerial judgements, not objective truths:

Overall score = ∑(wᵢ × sᵢ), where ∑wᵢ = 1

Here, wᵢ is the weight assigned to measure i and sᵢ is its normalised score. Scores must be placed on a common scale, and compensating one critical failure with excellent performance elsewhere may be unacceptable. Safety, legal and ethical requirements should normally be treated as constraints or minimum gates rather than merely weighted attributes.

Worked example: interpreting a scorecard

An operations unit assigns four measures: quality 30%, delivery 30%, cost 20% and people capability 20%. Its normalised scores are 90, 80, 70 and 60 respectively.

Score = (0.30×90) + (0.30×80) + (0.20×70) + (0.20×60)
Score = 27 + 24 + 14 + 12 = 77

The overall score is 77 out of 100. This result does not prove that performance is satisfactory. Management should ask whether the people score indicates future risk, whether cost reductions damaged capability, and whether any safety or compliance threshold was breached. A weighted average supports discussion; it does not replace judgement.

3. Policies, Controls, Compliance and Accountability

A policy states an organisation’s principles, intentions and mandatory boundaries. A procedure describes an approved way of performing an activity. A control is a mechanism that reduces the likelihood or impact of an unwanted event or increases the likelihood of a desired result. A standard specifies an expected level or condition. These concepts should not be conflated.

3.1 Control types

Controls may be:

  • Preventive: access restrictions, competency requirements, design specifications and approval limits.
  • Detective: inspections, reconciliations, alarms, audits and exception reports.
  • Corrective: containment, recovery, root-cause action and system redesign.
  • Directive: policies, training and leadership communication that guide behaviour.

Controls can also be manual, automated, entity-level or process-level. A control is effective only if it is appropriately designed and operates in practice. A signed form is not evidence of control effectiveness if signatures are routinely applied without review.

The COSO internal-control perspective commonly frames control through the control environment, risk assessment, control activities, information and communication, and monitoring. ISO management-system standards similarly emphasise context, leadership, planning, support, operation, performance evaluation and improvement. These frameworks are complementary tools, not substitutes for understanding the actual operation.

3.2 Lines of responsibility and assurance

A practical model separates:

  1. Operational ownership: the first line performs work and manages risks.
  2. Risk, compliance and quality support: the second line sets methods, advises and challenges.
  3. Independent assurance: the third line evaluates governance and control objectively.

The board or governing body retains oversight, while external regulators, auditors, customers and certification bodies may provide additional assurance. Independence should be sufficient to permit challenge; a manager should not be the sole assessor of controls for which that manager is responsible.

A RACI matrix can clarify whether a person or group is Responsible for doing work, Accountable for the outcome, Consulted before a decision or Informed afterwards. Each significant decision should have one clear accountable owner, even when responsibility is shared.

3.3 Compliance as operational capability

Compliance should be integrated into process design rather than added as an inspection at the end. Managers should maintain a register of applicable laws, licences, contractual commitments, internal policies and professional standards. Each requirement should have an owner, evidence source, review frequency and escalation route.

Compliance risk is not eliminated by documentation. It depends on competence, resources, supervision, data integrity, supplier behaviour and the organisation’s willingness to act when targets conflict with requirements. A healthy reporting culture encourages early escalation of near misses and control weaknesses.

4. Performance Leadership and Accountability

Performance leadership differs from target pressure. It creates clarity, capability and psychological conditions for responsible performance. Leaders must combine high standards with support, distinguish error from negligence, and ensure that accountability follows authority and available resources.

Effective performance conversations use evidence and inquiry:

  • What was expected and why?
  • What actually occurred?
  • What conditions influenced the result?
  • Which factors were controllable?
  • What immediate containment is required?
  • What system change will prevent recurrence?
  • Who owns the action and by when?

A just culture does not mean absence of accountability. It distinguishes human error, risky shortcuts, reckless conduct and deliberate misconduct. Human error normally calls for learning and system improvement; reckless or intentional violations may require disciplinary action. Applying these distinctions consistently is a leadership responsibility.

Avoiding dysfunctional measurement

Targets can produce gaming, data manipulation, local optimisation and concealment of bad news. For example, a warehouse rewarded solely for lines picked may dispatch incorrect orders or discourage reporting of equipment defects. Countermeasures include balanced measures, audit sampling, transparent definitions, team-based outcomes, quality gates and review of unintended effects.

A target should be challenging but credible, connected to controllable drivers and periodically revised when context changes. Benchmarking is useful only when processes, product mix, service definitions and resource conditions are sufficiently comparable.

5. Cross-Functional Teams and Operational Change

Operations are organised around flows, but organisations are often organised around functions. Procurement, production, logistics, sales, finance, information technology and human resources may each optimise their own objectives. Cross-functional leadership is therefore essential.

A high-performing cross-functional team requires:

  • a shared outcome and decision rights;
  • a common fact base and agreed definitions;
  • explicit interfaces, handoffs and service expectations;
  • psychological safety for raising risks;
  • conflict processes based on evidence and interests;
  • a cadence for decisions, actions and escalation.

The end-to-end process owner should have authority to coordinate across functional boundaries, while functional leaders retain professional and resource responsibilities. Governance forums should exist to decide, not merely exchange updates.

Leading change

Operational change may involve new technology, restructuring, outsourcing, revised standards, process redesign or changes in customer promise. A robust change approach includes:

  1. Define the problem and case for change using evidence.
  2. Identify stakeholders, affected roles, risks and dependencies.
  3. Design the future process and control environment.
  4. Assess capability, workload and training needs.
  5. Pilot or test where feasible.
  6. Communicate honestly, including uncertainty and trade-offs.
  7. Implement with transition controls and support.
  8. Measure adoption, outcomes and unintended consequences.
  9. Embed ownership and retire obsolete practices.

Change models such as Lewin’s unfreeze–change–refreeze or Kotter’s staged approach can provide useful prompts, but no model guarantees success. Change is political and contextual: people may resist because they lack capability, distrust leadership, face loss of status or identify genuine operational hazards.

6. Ethical Dilemmas and Stakeholder Expectations

Operations managers regularly face conflicts among cost, speed, quality, safety, privacy, employment conditions, environmental responsibility and customer promises. Ethical governance makes these conflicts visible rather than allowing them to be resolved informally through power or short-term incentives.

A practical ethical decision process is:

  1. Define the decision and affected parties.
  2. Establish the facts and identify uncertainty.
  3. Identify legal, policy and professional obligations.
  4. Consider consequences, rights, fairness and organisational values.
  5. Generate alternatives, including delaying or escalating the decision.
  6. Test whether the decision could be publicly defended.
  7. Consult appropriate independent or specialist advisers.
  8. Decide, document reasons and monitor consequences.

Useful ethical lenses include consequence-based reasoning, rights and duties, justice and fairness, virtue ethics and care for relationships and vulnerability. No single lens is sufficient in every situation.

Stakeholder management is not the promise to satisfy every demand. It is the disciplined process of identifying stakeholders, understanding their interests and influence, defining legitimate commitments and communicating trade-offs. A stakeholder register should include customers, employees, suppliers, regulators, owners, communities and affected third parties.

Examples of governance risks include algorithmic scheduling that creates unsafe workloads, supplier selection based solely on price, surveillance without proportionality or environmental claims unsupported by evidence. AI systems may improve forecasting, inspection and decision support, but governance must address data quality, explainability, bias, privacy, cybersecurity, human oversight and accountability for automated recommendations. Responsibility cannot be transferred to a software vendor or algorithm.

7. Strategic Review and Continuous Improvement

Strategic review is a recurring examination of whether the operating model remains aligned with purpose, environment and risk. It is not simply a monthly report. It asks whether assumptions remain valid and whether capabilities are sufficient for future requirements.

A strategic review should examine:

  • changes in customer needs, technology, regulation and competitors;
  • demand and capacity assumptions;
  • process capability, resilience and bottlenecks;
  • financial, safety, quality and sustainability performance;
  • workforce capability and succession;
  • supplier and ecosystem dependence;
  • control failures, incidents and near misses;
  • progress of strategic initiatives;
  • emerging risks and opportunities.

The review cycle should connect operational review, risk review, financial planning and strategy refresh. A useful rhythm may include daily control of critical operations, weekly exception management, monthly performance review, quarterly strategic review and an annual policy and risk-appetite review. Frequency should reflect volatility and consequence, not habit.

Continuous improvement methods such as PDCA, Lean problem solving, Six Sigma and after-action review are most effective when supported by governance. The improvement loop is:

  • Plan: define the problem, baseline, hypothesis and measures.
  • Do: test the intervention at controlled scale.
  • Check: compare results, variation and unintended effects.
  • Act: standardise, adapt or abandon the change.

Root-cause analysis should avoid stopping at “operator error.” Five Whys, fault-tree analysis, process mapping and Pareto analysis can reveal design, training, workload, maintenance, supplier or governance causes. These methods support inquiry but do not remove the need for evidence and expert judgement.

Illustrative Case: Northstar Medical Distribution

Background

Northstar Medical Distribution supplies hospitals from three regional warehouses. Its strategy promises high product availability, reliable delivery and regulatory integrity. Senior management introduced a scorecard based on order fulfilment, warehouse productivity, transport cost and customer complaints.

Problem

Within six months, reported productivity improved by 14%, but customer complaints increased, two temperature excursions were discovered late, and staff turnover rose. Warehouse supervisors explained that the productivity target rewarded rapid picking and discouraged time spent on equipment checks and exception reporting. The scorecard had no explicit safety, compliance or employee-capability measures.

Analysis

A cross-functional review mapped the process from order release to hospital receipt. It found:

  • inconsistent definitions of a completed order;
  • no common owner for cold-chain exceptions;
  • preventive-maintenance actions reported as completed without evidence;
  • targets that were locally optimised rather than end-to-end;
  • weak escalation when staff believed targets were unsafe;
  • customer complaints analysed as isolated events rather than patterns.

The governance failure was not simply a bad metric. It involved unclear accountability, inadequate controls, weak information quality and leadership behaviour that treated missed targets as more serious than near misses.

Approach and solution

Northstar redesigned the system. Productivity remained a measure, but it was placed behind minimum gates for temperature compliance, order accuracy and safety reporting. New measures included first-pass order accuracy, verified preventive-maintenance completion, temperature-excursion response time, employee competency coverage and closure of corrective actions. A process owner received authority across warehouse and transport functions.

The company introduced daily exception huddles, weekly control reviews and a quarterly strategic review. Supervisors were trained in just-culture investigation and escalation. A sample of completed maintenance records was independently verified. The board received a concise dashboard showing trends, threshold breaches, unresolved high risks and management actions rather than a large volume of unprioritised data.

Outcome

After two quarters, order accuracy and timely exception response improved, while reported productivity returned closer to its previous level. Management judged this acceptable because rework, complaints and compliance exposure declined. Employee surveys indicated greater willingness to report hazards. The case demonstrates that apparent efficiency can be false economy when the performance system excludes quality, risk and capability.

Learning points

  1. Metrics shape behaviour; they do not merely describe it.
  2. Critical legal, safety and ethical conditions require minimum thresholds.
  3. End-to-end ownership is necessary where work crosses functions.
  4. Assurance must test evidence, not just collect declarations.
  5. Strategic review should examine whether the measurement system still supports the strategy.

Challenges and Limitations

Governance systems face several limitations. First, not everything important is easily measurable; trust, judgement and resilience may be visible only after a crisis. Second, data may be incomplete, delayed or politically influenced. Third, balanced scorecards can become overloaded and reduce attention rather than improve it. Fourth, compliance can become a box-ticking exercise if leaders reward output while privately tolerating exceptions. Fifth, accountability can become blame when managers ignore system conditions.

There are also tensions between standardisation and local adaptation, transparency and confidentiality, speed and control, central oversight and professional autonomy. Good governance does not eliminate these tensions. It makes them explicit, assigns decision rights and creates escalation routes.

Best-Practice Principles

  • Begin with purpose and stakeholder value, not available data.
  • Use a small, balanced set of outcome and driver measures.
  • Define measures precisely and maintain data ownership.
  • Treat safety, law, ethics and critical quality as constraints, not merely tradeable scores.
  • Match accountability with authority, competence and resources.
  • Separate operational ownership from independent assurance.
  • Encourage early reporting and investigate system causes.
  • Make cross-functional decisions through clear forums and decision rights.
  • Govern technology and AI through human oversight, data controls and documented accountability.
  • Review strategy, risk and performance together as conditions change.
  • Retire measures and controls that no longer create value.

Chapter Summary

Operations governance connects strategy with controlled execution. It establishes direction, decision rights, policies, controls, assurance and learning. Performance leadership makes the system effective by aligning people, resolving trade-offs, encouraging responsible escalation and maintaining accountability.

A balanced performance system combines financial, customer, process, people, risk and sustainability perspectives. It uses both leading and lagging indicators, but recognises that weighted scores are managerial judgements and cannot safely compensate for critical safety, legal or ethical failures. Policies define boundaries, procedures describe approved work, controls manage risk, and assurance tests whether arrangements operate in practice.

Cross-functional governance is essential because operational value flows rarely respect organisational boundaries. Change leadership requires evidence, stakeholder involvement, capability development, transition control and post-implementation review. Ethical governance requires attention to consequences, rights, fairness, duties and vulnerability. Strategic review must connect performance trends with changing assumptions, capability, risk and stakeholder expectations. Ultimately, governance is successful when it enables reliable performance, responsible decisions and continuous organisational learning.

Key Terms

Governance: The system by which authority, direction, control and accountability are exercised.

Performance system: Connected objectives, measures, targets, reviews and actions used to guide performance.

Balanced Scorecard: A framework linking performance to financial, customer, internal-process and learning perspectives.

Leading indicator: A measure of conditions likely to influence future results.

Lagging indicator: A measure of an outcome after it has occurred.

Productivity: Useful output divided by the resources consumed.

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

Policy: A statement of principles, intentions and mandatory boundaries.

Procedure: An approved method for carrying out an activity.

Control: A mechanism that prevents, detects or corrects unwanted events or supports desired outcomes.

Assurance: Independent or structured evaluation of governance, risk and control effectiveness.

Accountability: Obligation to answer for decisions, actions and results.

RACI: A responsibility model identifying Responsible, Accountable, Consulted and Informed parties.

Just culture: An approach that distinguishes human error, risky behaviour and intentional misconduct.

Stakeholder: A party that affects, is affected by or has an interest in organisational activity.

Strategic review: A structured reassessment of strategy, performance, assumptions, capability and risk.

Psychological safety: A climate in which people can raise concerns and admit mistakes without unreasonable fear.

Operational resilience: The capability to prepare for, respond to and recover from disruption.

Continuous improvement: Systematic, ongoing enhancement of processes, performance and capability.

Review Questions

Short Answer Questions

  1. Distinguish governance from operational management.
  2. What is the difference between a leading indicator and a lagging indicator?
  3. Define a preventive control and give one example.
  4. Why should safety and legal requirements not normally be treated only as weighted scorecard measures?
  5. What is the purpose of a RACI matrix?

Long Answer Questions

  1. Explain how a Balanced Scorecard can be adapted for advanced operations management.
  2. Discuss the relationship among policy, procedure, control, assurance and accountability.
  3. Analyse how poorly designed targets can create dysfunctional operational behaviour.
  4. Explain the main requirements for leading cross-functional operational change.
  5. Evaluate the role of strategic review in maintaining alignment between operations and organisational purpose.

Analytical / Application Questions

  1. A service centre improves average handling time by 20%, but customer rework and employee absence increase. Design a balanced set of measures and explain the governance actions you would recommend.
  2. A supplier offers a major cost reduction but cannot demonstrate compliance with required labour and environmental standards. Apply the ethical decision process and identify an appropriate governance response.
  3. An automated scheduling system repeatedly assigns workloads that breach internal fatigue limits. Analyse the control failure, allocate accountability and propose immediate and longer-term corrective actions.

Multiple Choice Questions with Answers

Question 1

Which statement best describes operations governance?

A. The exclusive measurement of labour productivity

B. The system of direction, control, accountability and assurance for operations

C. The daily scheduling of individual employees

D. The replacement of management by external auditors

Correct Answer: B. The system of direction, control, accountability and assurance for operations

Question 2

Which is a leading indicator of future maintenance reliability?

A. Last quarter’s equipment downtime

B. Annual repair expenditure

C. Verified completion of preventive-maintenance actions

D. Number of customer complaints received last month

Correct Answer: C. Verified completion of preventive-maintenance actions

Question 3

An operation produces 950 acceptable units without rework from 1,000 units entering the process. What is its first-pass yield?

A. 5%

B. 50%

C. 95%

D. 105%

Correct Answer: C. 95%

Question 4

Which control is primarily detective?

A. Role-based access restriction

B. Pre-approval of purchases

C. A post-process audit of transaction records

D. Training before an employee begins work

Correct Answer: C. A post-process audit of transaction records

Question 5

In a RACI matrix, which designation identifies the person answerable for the outcome?

A. Responsible

B. Accountable

C. Consulted

D. Informed

Correct Answer: B. Accountable

Question 6

Why should a weighted scorecard be interpreted cautiously?

A. Weights can never be changed

B. A high overall score may conceal a critical safety or compliance failure

C. It cannot include non-financial measures

D. It measures only historical performance

Correct Answer: B. A high overall score may conceal a critical safety or compliance failure

Question 7

Which response is most consistent with a just culture after an unintentional human error?

A. Automatic dismissal

B. Ignoring the event

C. Learning-focused investigation and system improvement

D. Rewarding the employee for concealing it

Correct Answer: C. Learning-focused investigation and system improvement

Question 8

What is the principal purpose of an independent assurance function?

A. To perform every operational task

B. To set all customer prices

C. To evaluate governance, risk and controls objectively

D. To replace process owners

Correct Answer: C. To evaluate governance, risk and controls objectively

Question 9

Which practice best supports cross-functional performance?

A. Separate targets with no shared outcome

B. A process owner with clear decision rights across interfaces

C. Removing all escalation procedures

D. Allowing each function to define performance differently

Correct Answer: B. A process owner with clear decision rights across interfaces

Question 10

A process has 80 on-time deliveries from 100 orders due. What is its on-time delivery rate?

A. 20%

B. 80%

C. 100%

D. 125%

Correct Answer: B. 80%

Advanced Operations Management
Chapter 15 of 15