Customer, Stakeholder and Service Quality

Introduction

Quality is ultimately judged in use. An organization may conform to internal specifications yet fail if customers cannot obtain the service, do not trust the provider, or experience unnecessary effort. Total Quality Management (TQM) therefore treats customer and stakeholder value as central to operational design, measurement, improvement, and governance.

This chapter examines how organizations translate the voice of the customer (VOC) and stakeholder expectations into measurable requirements. It integrates Kano analysis, SERVQUAL, quality function deployment (QFD), customer-journey mapping, and complaint analysis. It also considers satisfaction, loyalty, customer experience, ethics, digital technologies, and the managerial challenge of reconciling the interests of multiple stakeholders.

The central principle is that customer requirements must be converted from language such as “fast,” “helpful,” or “secure” into operational definitions, performance targets, controls, and improvement priorities.

Learning Objectives

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

1. Distinguish customers, stakeholders, users, beneficiaries, and regulators.
2. Explain the relationships among perceived quality, satisfaction, loyalty, and experience.
3. Apply Kano analysis to classify customer requirements.
4. Use SERVQUAL critically to evaluate service-quality gaps.
5. Construct the logic of a QFD House of Quality.
6. Map customer journeys and identify moments of truth and failure demand.
7. Analyze complaints as data for corrective and preventive action.
8. Design a balanced system of customer, process, and outcome measures.
9. Evaluate ethical, technological, and governance issues in customer-quality management.

1. Customers, Stakeholders, and the Meaning of Quality

A customer is an individual or organization that receives, purchases, or is affected by an output. In a service system, the customer may be the payer, the user, or both. A hospital patient is a user, an insurer may be a payer, and a family member may be an important participant in the experience. A stakeholder is any person or group that can affect, or be affected by, organizational decisions and outcomes. Employees, suppliers, regulators, communities, owners, and professional bodies may therefore have legitimate quality interests.

Several distinctions are operationally important:

Customer quality has at least three dimensions. Conformance quality concerns whether a product or service meets stated requirements. Performance quality concerns how well it performs in use. Experience quality concerns the customer’s total cognitive, emotional, and behavioral response across interactions. These dimensions can conflict. A highly standardized online process may reduce cost and variation while creating exclusion for customers with limited digital access.

A TQM perspective treats quality as a system property. Customer requirements enter through research and listening processes; they are translated into specifications; processes deliver outputs; customers evaluate outcomes; and feedback drives learning. This is a closed-loop view rather than a one-time satisfaction survey.

2. From Expectations to Satisfaction, Loyalty, and Experience

Customer satisfaction is an evaluative judgment formed after comparing perceived performance with expectations, prior experience, and alternatives. A useful conceptual representation is:

Here, S is satisfaction, P is perceived performance, E is prior expectation, A represents available alternatives and comparison standards, and C represents customer characteristics and context. This is a conceptual model, not a universal predictive equation; the variables cannot be assumed to combine linearly.

When performance exceeds expectations, positive disconfirmation may occur; when it falls below expectations, negative disconfirmation may occur. However, satisfaction does not guarantee loyalty. A customer may be satisfied but switch because of price, convenience, a contract ending, or a more attractive competitor. Conversely, a customer may remain despite dissatisfaction because switching costs are high.

Loyalty may include repeat purchase, retention, advocacy, share of wallet, or reduced propensity to switch. Each behavior has different causes and should not be treated as interchangeable. Customer experience (CX) is broader than satisfaction: it includes the cumulative experience before, during, and after consumption, across physical, human, digital, and social touchpoints.

Useful measures include:

• satisfaction rating and top-box satisfaction;
• customer effort score;
• complaint rate and repeat-complaint rate;
• retention and churn;
• repeat purchase or renewal;
• first-contact resolution;
• on-time delivery and service recovery time;
• recommendation or advocacy indicators.

A proportion or rate should be defined precisely. For example, if 42 of 600 cases generate a complaint, the complaint rate is:

The denominator must be stated. Complaints per transaction, per customer, per delivery, and per service hour answer different questions. Rates should also be segmented by product, channel, location, customer type, and time period to avoid misleading averages.

3. Capturing the Voice of the Customer and Stakeholder

VOC is not simply what customers say in a questionnaire. It includes expressed needs, observed behavior, complaints, service records, search behavior, interviews, ethnographic observation, usage data, social feedback, and lost-customer analysis. Organizations should combine stated preferences with revealed preferences because customers may report that a feature is important without using it in practice.

A disciplined VOC process has six stages:

1. Identify stakeholder groups. Segment by use case, risk, vulnerability, profitability, geography, channel, and relationship.
2. Select listening methods. Use interviews, focus groups, surveys, observation, complaint coding, transaction data, and employee insight.
3. Elicit verbatim statements. Preserve the customer’s language before interpreting it.
4. Translate statements into needs. “I hate waiting” may imply a need for predictable and short elapsed time, not merely more staff.
5. Prioritize needs. Consider importance, dissatisfaction, feasibility, risk, strategic relevance, and equity.
6. Validate requirements. Test whether the translated requirement is understood, measurable, and relevant to the target segment.

A requirement should be operationalized with an object, metric, direction, target, population, and measurement method. “Fast response” is weak; “90% of priority chat requests receive a human response within 60 seconds, measured weekly by system timestamp” is actionable.

Stakeholder analysis is essential when requirements conflict. A hospital may need to balance patient privacy, clinician access, payer documentation, employee workload, and legal obligations. Quality management is not a search for the preference of the loudest group; it is a reasoned process for balancing value, risk, rights, and feasibility.

4. Kano Analysis: Different Types of Requirements

The Kano model distinguishes requirements according to how their presence or performance affects satisfaction. Five categories are commonly used:

The model is valuable because it prevents managers from assuming that every requirement has a linear payoff. Hygiene factors should be protected before attractive features are added. A sophisticated recommendation engine cannot compensate for unreliable billing.

A Kano questionnaire presents functional and dysfunctional forms of a feature. For example:

• Functional: “How would you feel if the service provided a live delivery map?”
• Dysfunctional: “How would you feel if the service did not provide a live delivery map?”

Respondents select categories such as “I like it,” “I expect it,” “I am neutral,” “I can live with it,” or “I dislike it.” Responses are classified using the Kano evaluation table. Because category assignment can vary by segment and time, Kano results should be treated as diagnostic evidence rather than permanent truth. Attractive features can become must-be requirements as competitors imitate them.

For prioritization, an organization may calculate the proportion of responses in each category. If 100 respondents classify a feature as 55 attractive, 25 one-dimensional, 15 indifferent, and 5 must-be, the feature appears to have strong delight potential. However, investment decisions should also consider implementation cost, reliability, accessibility, cybersecurity, and the consequences of failure.

5. SERVQUAL and the Measurement of Service Quality

SERVQUAL conceptualizes service quality as the gap between customer perceptions and expectations across five dimensions:

1. Reliability: performing the promised service dependably and accurately.
2. Responsiveness: willingness and speed in helping customers.
3. Assurance: competence, courtesy, credibility, and ability to create trust.
4. Empathy: individualized attention and understanding.
5. Tangibles: physical facilities, equipment, appearance, and communication materials.

A frequently used item-level gap score is:

where G_i is the gap for item i, P_i is the perception score, and E_i is the expectation score. A negative value indicates that perceived performance is below the measured expectation. If a respondent gives a perception score of 5 and an expectation score of 7 on a 1–7 scale, G_i = -2.

An unweighted dimension score may be calculated as:

where n_d is the number of items in dimension d. This average assumes that items are measured on the same scale and are being treated as equally weighted. A weighted version may be used when validated importance weights w_i are available:

SERVQUAL has limitations. Expectations can be unstable and may be influenced by the survey itself. Gap scores can obscure whether a low result arises from poor performance or unusually high expectations. The five dimensions may not fit every industry or culture, and averages may hide vulnerable groups. SERVQUAL should therefore be combined with objective indicators, qualitative evidence, and segment-level analysis.

6. Quality Function Deployment: Translating Needs into Design

QFD provides a structured method for translating customer requirements (“whats”) into technical or operational characteristics (“hows”). Its central tool, the House of Quality, typically includes:

• customer requirements;
• importance ratings;
• competitive assessment;
• technical characteristics;
• relationship matrix;
• correlations among technical characteristics;
• target values;
• deployment priorities.

A relationship matrix commonly uses 9 for strong, 3 for medium, 1 for weak, and 0 for no relationship. A simple technical priority is:

Here, Priority_j is the priority of technical characteristic j, Importance_i is the importance of customer requirement i, and Relationship_ij is the selected relationship score between requirement i and characteristic j. The scale is ordinal and heuristic; multiplying and summing does not create a measurement with a physical unit. It supports structured judgment, not false precision.

Worked QFD example

Suppose customers identify three requirements for an online grocery service:

The priorities are:

• Delivery-slot accuracy = (5×9)+(4×1)+(5×0)=49
• App response time = (5×1)+(4×9)+(5×0)=41
• Packaging integrity = (5×0)+(4×1)+(5×9)=49

The result indicates equal high priority for delivery accuracy and packaging integrity, followed by app response time. Management must then set measurable targets, such as percentage of deliveries within the promised window, median screen response time, and damage incidents per 1,000 orders. The QFD result does not itself prove which investment has the highest financial return.

7. Customer-Journey Mapping and Moments of Truth

A customer-journey map represents the customer’s progression through stages such as awareness, search, purchase, onboarding, use, support, renewal, and exit. It should show customer goals, actions, questions, emotions, touchpoints, backstage processes, pain points, failure demand, and opportunities.

A useful map distinguishes:

• Frontstage interactions: visible to the customer;
• Backstage activities: invisible processes that enable delivery;
• Moments of truth: interactions that disproportionately influence trust or commitment;
• Failure demand: contacts or work generated because the system failed to do something correctly the first time;
• Handoffs: transfers among employees, departments, suppliers, or channels.

Mapping should be evidence-based. Workshops alone may reproduce internal assumptions. Combine observation, call recordings, digital analytics, process data, complaints, and interviews. The map should also account for accessibility, language, disability, low connectivity, and emotional vulnerability.

Journey mapping links experience to process improvement. If customers repeatedly contact support to ask where an order is, the problem may not be staff courtesy; it may be poor status visibility, inaccurate inventory, or an unreliable promise date. Improvement should target the causal process rather than merely training agents to apologize.

8. Complaint Analysis and Service Recovery

Complaints are both a signal of dissatisfaction and a source of process knowledge. They are not a complete measure of poor quality because complaint propensity varies with awareness, access, perceived retaliation, and the effort required to complain. A low complaint count can therefore mean excellent quality or a defective voice system.

A mature complaint process includes:

1. accessible intake through multiple channels;
2. acknowledgement and case identification;
3. triage by severity, safety, vulnerability, and urgency;
4. containment and immediate service recovery;
5. investigation of facts and contributing causes;
6. fair response and remedy;
7. root-cause analysis and corrective action;
8. verification of effectiveness;
9. trend reporting and organizational learning.

Complaint categories should be mutually understandable and sufficiently specific. Useful coding fields include product, channel, failure mode, customer segment, severity, time, location, cause, remedy, and recurrence. Pareto analysis can identify the categories contributing most to complaint volume, but frequency is not the same as risk. A rare privacy breach may deserve more attention than hundreds of minor delays.

Root-cause tools include the five whys, fishbone diagrams, fault-tree analysis, and process mapping. The five-whys method is not a mechanical requirement to ask “why” exactly five times. It is a way to move beyond individual blame toward system conditions, while verifying each causal link with evidence.

Service recovery should be timely, proportionate, consistent, and empowering. Typical remedies include explanation, apology, correction, replacement, refund, expedited service, or prevention of recurrence. Recovery paradox—the possibility that an excellent recovery produces higher satisfaction than an error-free encounter—should not be used to justify avoidable failure. Recovery consumes resources and may not restore trust after serious harm.

9. Designing a Balanced Quality Measurement System

A customer-quality dashboard should connect leading indicators, process measures, and outcomes. A balanced structure may include:

Measures require operational definitions, data owners, sampling rules, reporting frequency, and action thresholds. Managers should avoid target fixation. If call-center agents are rewarded only for short handling time, they may rush customers and increase repeat contacts. If complaint reduction is rewarded without checking access, staff may discourage complaints.

A strong measurement system triangulates three forms of evidence:

• subjective evidence: what customers report;
• behavioral evidence: what customers do;
• operational evidence: what the process records.

Differences among these sources are informative. High satisfaction alongside high repeat-contact rates may indicate politeness without resolution, survey bias, or a customer segment with limited alternatives.

10. Illustrative Case: Improving a University Digital-Enrollment Service

Background

This fictional case concerns Northbridge University, which moved most graduate enrollment activities to a digital portal. Students could submit documents, pay fees, select modules, and request support online.

Problem

The university’s overall satisfaction score was 78%, apparently acceptable. However, complaints about “missing documents,” payment uncertainty, and delayed responses were increasing. International students and students with disabilities reported greater difficulty than the overall average.

Analysis

The improvement team conducted interviews, reviewed 420 complaints, observed ten enrollment journeys, analyzed portal logs, and surveyed 310 students. Kano analysis identified secure payment and confirmation receipts as must-be requirements, transparent status tracking as a one-dimensional requirement, and personalized deadline reminders as an attractive requirement. A journey map showed three major handoffs: admissions to finance, finance to registry, and registry to academic departments.

Complaint coding found that 38% of cases involved unclear status, 27% involved duplicate document requests, 18% involved payment confirmation, and the remainder involved access, policy, or exceptional cases. The portal recorded submission but not successful internal validation, causing students to resubmit documents. A SERVQUAL-style survey found the largest gap in responsiveness, but qualitative evidence showed that the underlying cause was fragmented ownership rather than individual unwillingness to help.

Approach and solution

The university created a single case identifier across departments, introduced status states with plain-language explanations, provided accessible document formats, and generated immediate payment receipts. QFD translated “I want to know what is happening” into technical characteristics: timestamped status updates, ownership visibility, maximum queue age, and notification reliability. A complaint triage rule escalated potential enrollment-loss cases within one working day.

The university also changed measurement. Instead of relying on overall satisfaction, it tracked first-time-right document validation, repeat contacts per case, median resolution time, accessibility-related failure, and outcomes by student group. Staff were trained to resolve cases across departmental boundaries rather than merely redirecting students.

Outcome

After one enrollment cycle, repeat contacts per case declined, duplicate submissions fell, and the gap in reported effort between domestic and international students narrowed. Overall satisfaction increased modestly. The most important result was not the score increase but improved visibility of failure causes and clearer accountability for the end-to-end journey.

Learning points

1. Aggregate satisfaction can conceal severe problems for particular segments.
2. Complaints often reveal process and ownership failures rather than isolated employee behavior.
3. Kano analysis helps sequence investments: basic trust and reliability precede delight features.
4. QFD makes vague experience needs actionable but does not replace managerial judgment.
5. Accessibility and fairness are quality requirements, not optional additions.

11. Critical Issues, Ethics, and Governance

Customer analytics can improve service, but it can also create surveillance, manipulation, exclusion, and unfair personalization. Organizations should collect only data necessary for a legitimate purpose, explain how it is used, protect confidentiality, control access, and retain it only as long as justified. Consent, where required, should be meaningful rather than buried in complex terms.

Segmentation and AI-based prediction require bias testing. A model trained on historical complaints may learn that some groups complain less because they face language or access barriers; interpreting low complaint frequency as low need would be dangerous. Automated service decisions should provide human review for consequential cases, such as denial of benefits, cancellation, or safety-related escalation.

Customer experience design must not exploit behavioral vulnerabilities through dark patterns, hidden charges, difficult cancellation, artificial urgency, or consent fatigue. Quality includes truthful communication and the customer’s ability to make an informed choice. Governance should assign accountability for data quality, model monitoring, complaint escalation, accessibility, and remedy.

12. Contemporary Developments and Best Practice

Digital channels, conversational agents, predictive service, remote monitoring, and real-time journey analytics are changing VOC management. These technologies can detect friction earlier and personalize support, but they introduce risks of inaccurate automation, opaque decisions, cybersecurity incidents, and loss of human contact.

Best practice includes:

• combine qualitative and quantitative VOC evidence;
• segment results and test for unequal experience;
• translate needs into measurable operational requirements;
• prioritize reliability, safety, and fairness before novelty;
• connect customer measures to process causes;
• close the complaint loop with customers and employees;
• validate surveys for comprehension and cultural relevance;
• distinguish correlation from causation in experience analytics;
• review requirements periodically as expectations and technology change;
• govern automated decisions with transparency, human oversight, and appeal.

Chapter Summary

Customer and stakeholder quality is the disciplined translation of expectations, needs, risks, and experiences into processes and measurable requirements. Customers include users, payers, beneficiaries, and internal recipients; stakeholders also include employees, suppliers, regulators, owners, and communities. Satisfaction reflects perceived performance in context, while loyalty and experience are related but distinct outcomes.

Kano analysis differentiates must-be, one-dimensional, attractive, indifferent, and reverse requirements. SERVQUAL offers a structured way to examine gaps across reliability, responsiveness, assurance, empathy, and tangibles, but should be combined with objective and qualitative evidence. QFD converts customer requirements into technical characteristics and priorities. Journey mapping reveals touchpoints, handoffs, moments of truth, and failure demand. Complaint analysis turns dissatisfaction into corrective and preventive learning.

Effective systems use clearly defined indicators, segment results, and triangulate perceptions, behavior, and process data. Ethical quality management requires accessibility, fairness, privacy, transparency, responsible analytics, and meaningful human remedy. The managerial objective is not simply to maximize a survey score; it is to design a reliable, equitable, and continuously improving system that creates legitimate value for customers and stakeholders.

Key Terms

Voice of the customer: Evidence about customer needs, expectations, experiences, and problems.

Stakeholder: A person or group that affects or is affected by organizational decisions.

Customer experience: The cumulative cognitive, emotional, and behavioral response across interactions.

Customer satisfaction: An evaluation of perceived performance relative to expectations and alternatives.

Loyalty: Behavioral or attitudinal commitment reflected in retention, repeat use, or advocacy.

Conformance quality: The degree to which output meets specified requirements.

Moment of truth: An interaction that strongly influences customer trust or commitment.

Kano model: A framework classifying requirements by their relationship to satisfaction.

Must-be requirement: A basic requirement whose absence causes strong dissatisfaction.

One-dimensional requirement: A requirement for which improved performance generally increases satisfaction.

Attractive requirement: An unexpected feature that can create disproportionate delight.

SERVQUAL: A service-quality framework based on perceived-expectation gaps.

Reliability: Dependable and accurate performance of a promised service.

Quality function deployment: A method for translating customer needs into technical and operational characteristics.

House of Quality: The matrix used in the first stage of QFD.

Customer journey map: A representation of customer stages, interactions, emotions, and supporting processes.

Failure demand: Work created because a service did not meet a need correctly the first time.

Service recovery: Actions taken to correct a failure and restore value or trust.

Complaint analysis: Systematic classification and investigation of dissatisfaction data.

Dark pattern: A design practice that manipulates users into choices they may not otherwise make.

Review Questions

Short Answer Questions

1. Distinguish a payer, user, beneficiary, and stakeholder using a service example.
2. What is the difference between a must-be and an attractive Kano requirement?
3. State the five SERVQUAL dimensions.
4. What is failure demand, and why is it useful in journey analysis?
5. Why should customer satisfaction not be treated as equivalent to loyalty?

Long Answer Questions

1. Explain how an organization can move from raw VOC statements to measurable operational requirements.
2. Critically evaluate the usefulness and limitations of SERVQUAL in a digital service.
3. Describe the components of a House of Quality and explain how QFD supports cross-functional decisions.
4. Discuss how complaint management can become a source of organizational learning rather than merely a customer-service activity.
5. Explain the ethical risks associated with customer analytics and AI-enabled personalization.

Analytical / Application Questions

1. A bank receives complaints that customers are “kept in the dark” during loan applications. Design a VOC study, journey map evidence plan, and three measurable requirements.
2. A service has perception scores of 5, 6, and 4 and expectation scores of 6, 6, and 5 for three items. Calculate the three gap scores and interpret the pattern. What additional evidence would you collect before prioritizing improvement?
3. Using Kano analysis and QFD, explain how you would prioritize secure payment, rapid response, personalized recommendations, and accessible human support for an online retail service.

Multiple Choice Questions with Answers

Question 1

Which requirement is most likely classified as a must-be requirement in the Kano model?

A. A novel feature customers did not request

B. A basic safety control whose absence causes strong dissatisfaction

C. A feature that has no effect on satisfaction

D. A feature that some customers actively dislike when present

Correct Answer: B. A basic safety control whose absence causes strong dissatisfaction

Question 2

In SERVQUAL, reliability primarily refers to:

A. Physical appearance of facilities

B. Individualized attention

C. Dependable and accurate performance of the promised service

D. Willingness to provide discounts

Correct Answer: C. Dependable and accurate performance of the promised service

Question 3

If perceived service performance is 5 and expectation is 7 on the same scale, the SERVQUAL gap is:

A. −2

B. 2

C. 12

D. 35

Correct Answer: A. −2

Question 4

What is the principal purpose of QFD?

A. To replace all customer research with financial data

B. To translate customer requirements into technical characteristics

C. To calculate employee absenteeism

D. To classify complaints by legal severity only

Correct Answer: B. To translate customer requirements into technical characteristics

Question 5

Which is an example of failure demand?

A. A customer contacting support because an order-status message was unclear

B. A customer purchasing an optional premium service

C. A manager conducting a scheduled audit

D. A supplier submitting a routine invoice

Correct Answer: A. A customer contacting support because an order-status message was unclear

Question 6

Why should complaint counts be interpreted cautiously?

A. Every complaint is necessarily invalid

B. Complaint propensity and access to complaint channels vary among customers

C. Complaints cannot be categorized

D. Complaint data never contain process information

Correct Answer: B. Complaint propensity and access to complaint channels vary among customers

Question 7

Which statement best distinguishes customer experience from satisfaction?

A. Experience concerns only the final transaction price

B. Satisfaction is always behavioral, whereas experience is always financial

C. Experience covers the broader cumulative response across multiple touchpoints

D. There is no meaningful distinction between them

Correct Answer: C. Experience covers the broader cumulative response across multiple touchpoints

Question 8

In the illustrative QFD example, what was the calculated priority for packaging integrity?

A. 25

B. 41

C. 45

D. 49

Correct Answer: D. 49

Question 9

Which practice creates a significant ethical risk in customer analytics?

A. Segmenting results to identify unequal outcomes

B. Providing a human appeal route for automated decisions

C. Using opaque personalization that exploits customer vulnerability

D. Defining data-retention responsibilities

Correct Answer: C. Using opaque personalization that exploits customer vulnerability

Question 10

Which combination provides the strongest triangulation of customer quality?

A. One annual satisfaction score only

B. Customer perceptions, observed behavior, and operational process data

C. Employee opinions without customer evidence

D. Complaint volume without a denominator

Correct Answer: B. Customer perceptions, observed behavior, and operational process data