2. Customer Expectations, Perceptions and Behaviour

Introduction and Context

Quality is not judged only by what an organisation produces or delivers. It is judged by the customer’s interpretation of that experience. Two customers may receive the same service and form different evaluations because their expectations, emotional states, prior experiences, perceived effort and personal goals differ. Customer experience quality therefore depends on the relationship between organisational performance and customer meaning-making.

In Total Quality Management (TQM), this shifts attention from conformance alone to customer-defined value. A technically reliable service may still be perceived as poor if it is difficult to access, impersonal, uncertain or inconsistent with the promise communicated by the organisation. Conversely, a service with minor operational imperfections may be evaluated positively when recovery is rapid, communication is respectful and the customer feels understood.

This chapter examines how customers form expectations, interpret performance and behave before, during and after an interaction. It brings together expectation–confirmation theory, the Kano model, moments of truth, jobs-to-be-done, customer effort and behavioural economics. These perspectives are complementary rather than interchangeable. Together, they help managers identify what customers value, why satisfaction changes, how decisions are influenced and where quality improvement should be directed.

Learning Objectives

After studying this chapter, students should be able to:

1. Distinguish customer needs, expectations, perceptions, satisfaction, trust and loyalty.

2. Explain expectation–confirmation theory and apply it to service evaluation.

3. Use the Kano model to distinguish basic, performance and excitement attributes.

4. Analyse moments of truth and customer journeys across multiple touchpoints.

5. Apply jobs-to-be-done and customer-effort thinking to quality improvement.

6. Explain how emotions, cognitive biases and trust influence customer behaviour.

7. Evaluate managerial, ethical and digital implications of customer-behaviour analysis.

8. Design evidence-based interventions for improving customer experience.

From Needs to Behaviour: The Customer’s Internal Evaluation

A customer need is a condition or outcome considered important by the customer. Needs may be functional, emotional, social or symbolic. A patient may need accurate treatment, reassurance and dignity. A student may need learning, administrative simplicity and confidence about future employment. A business buyer may need cost control, operational continuity and reputational security.

An expectation is a belief about what will happen or what should happen. Expectations are formed from advertising, organisational promises, word of mouth, past experience, industry norms, price, urgency and personal circumstances. Expectations may be explicit, such as a promised delivery date, or implicit, such as an expectation of respectful treatment.

Perception is the customer’s interpretation of actual performance. It is not a complete objective record of events. It is selective and influenced by attention, emotion, context and memory. A delay explained proactively may be perceived differently from an unexplained delay of the same duration.

Satisfaction is an evaluative response arising from comparison between expected and perceived performance. It is usually transaction-specific, whereas loyalty reflects a broader behavioural relationship involving repeat purchase, preference, advocacy and switching resistance. Satisfaction does not automatically create loyalty: a customer may be satisfied with a convenient transaction while remaining willing to move to a competitor.

Trust is the willingness to accept vulnerability based on confidence in an organisation’s competence, integrity and benevolence. Trust becomes particularly important when customers cannot fully evaluate quality before purchase, as in healthcare, education, consulting, financial services and technology platforms. Trust reduces perceived risk, but it can be damaged disproportionately by concealment, inconsistent treatment or misuse of personal data.

Customer behaviour includes search, evaluation, purchase, use, complaint, adaptation, repurchase and recommendation. Behaviour is shaped not only by rational calculation but also by habit, social influence, emotions, framing and perceived effort.

Expectation–Confirmation Theory

Expectation–confirmation theory explains satisfaction as an outcome of comparing prior expectations with perceived performance. The basic logic is:

Satisfaction = f(perceived performance relative to expectation).

When performance exceeds expectations, positive disconfirmation occurs. When performance matches expectations, confirmation occurs. When performance falls below expectations, negative disconfirmation occurs. In simplified form:

• Positive disconfirmation: performance > expectation
• Confirmation: performance = expectation
• Negative disconfirmation: performance < expectation

The model is useful because it explains why the same performance can produce different reactions. A hotel room that is viewed as excellent by a budget traveller may be judged inadequate by a guest expecting luxury. It also explains why raising promises can create risk: a stronger promise may increase initial attraction but also raise the performance threshold required for satisfaction.

The theory should not be interpreted mechanically. Expectations can change during an interaction. A customer initially expecting a routine response may become more demanding after learning about a serious risk. Expectations can also be plural: customers may have minimum acceptable performance, desired performance and predicted performance. The gap between desired and minimum acceptable performance is sometimes described as a zone of tolerance. Performance within this zone may be accepted without enthusiasm; performance outside it can trigger delight or dissatisfaction.

Managers can act on both sides of the comparison. They can improve actual performance, clarify or responsibly manage promises, and help customers understand what the service includes. Deliberately lowering expectations is not a quality strategy. Misleadingly modest promises may produce short-term confirmation but damage trust and perceived integrity.

The Kano Model: Not All Attributes Create Value in the Same Way

The Kano model classifies quality attributes according to their relationship with satisfaction.

Must-be attributes are basic requirements. Their presence may not generate appreciation because customers take them for granted, but their absence creates strong dissatisfaction. In a banking service, accurate account records and secure transactions are examples.

One-dimensional or performance attributes generate satisfaction roughly in proportion to their level of performance. Faster response, lower waiting time or better battery life may produce increasing value as performance improves.

Attractive or excitement attributes are not expected, but their presence can create disproportionate delight. Examples might include a thoughtful recovery gesture or an unexpectedly useful digital feature. Their absence does not normally cause dissatisfaction because customers did not anticipate them.

The model also recognises indifferent attributes, which have little effect on customer evaluation, and reverse attributes, where more of a feature can reduce satisfaction. A customer may dislike excessive notifications even when an organisation assumes that additional communication is beneficial.

Kano categories are not permanent. Excitement attributes can become performance attributes and eventually must-be attributes as competitors imitate them and customers become accustomed to them. Mobile tracking, once distinctive, may become a basic expectation in delivery services. Kano analysis should therefore be repeated as markets, technology and customer experience evolve.

Moments of Truth and the Customer Journey

A moment of truth is an interaction in which a customer forms or revises an impression of an organisation. It may occur before purchase, during service delivery or after the transaction. A search result, website form, call-centre greeting, payment process, product installation, complaint response or invoice can each become a moment of truth.

The customer journey perspective connects these moments. It examines the sequence of stages through which a customer moves, including awareness, consideration, purchase, onboarding, use, support, renewal and exit. Journey analysis should include the customer’s goal, actions, questions, emotions, barriers, channels and backstage organisational processes.

A common managerial error is to optimise individual touchpoints while ignoring the whole journey. A call centre may meet its handling-time target while transferring customers repeatedly. A website may be visually attractive while requiring information that the organisation already possesses. Local efficiency can therefore produce global customer effort.

Moments of truth differ in importance. A routine interaction may have limited consequences, whereas a failure during a high-risk or emotionally sensitive moment can dominate the customer’s overall evaluation. Managers should identify moments that are frequent, critical, irreversible, emotionally intense or highly visible in customer communication.

Jobs-to-be-Done: Understanding the Progress Customers Seek

Jobs-to-be-done (JTBD) theory asks what customers are trying to accomplish rather than merely what demographic category they belong to or what product they buy. Customers “hire” products, services or organisations to make progress in a situation.

A job may be functional, emotional or social. A commuter does not simply buy transport; the job may be to arrive predictably and begin the workday without stress. A university student may “hire” an online portal to resolve an administrative issue without needing to understand the institution’s internal structure. A customer selecting cloud software may seek not only technical functionality but also confidence that the organisation can scale safely.

A useful job statement identifies the situation, desired progress and constraints: “When submitting a time-sensitive claim, I want to know its status and next action so that I can plan financially without repeated calls.” Such statements are more actionable than broad descriptions such as “customers want convenience.”

JTBD complements segmentation. Demographic segments describe who customers are; jobs describe what they are trying to achieve. The same person may hire different solutions for different situations, and different demographic groups may share the same job. Research methods include interviews about recent decisions, observation, diary studies, complaint analysis and examination of workarounds.

Customer Effort and the Economics of Convenience

Customer effort is the physical, cognitive, emotional and temporal burden required to achieve a desired outcome. It includes searching for information, remembering credentials, repeating explanations, completing forms, navigating menus, waiting, correcting errors and managing uncertainty.

Reducing effort is not identical to reducing interaction. Some customers value human assistance, particularly where the decision is complex or risky. The objective is to remove unnecessary effort while preserving useful guidance and control. A self-service option that forces a customer to diagnose an unfamiliar technical problem may reduce organisational cost but increase customer effort.

Effort has several dimensions:

• Time effort: waiting, delays and repeated contacts.
• Cognitive effort: interpreting instructions or choosing among alternatives.
• Procedural effort: forms, authentication and documentation.
• Emotional effort: coping with anxiety, embarrassment or conflict.
• Physical effort: travel, accessibility barriers or manual tasks.

Organisations can reduce effort by using plain language, preserving context across channels, pre-filling known information, offering clear next steps, designing accessible interfaces and giving employees authority to resolve routine issues. Effort should be measured across the complete journey rather than at one contact point.

Emotion, Trust and Behavioural Economics

Customer decisions are partly affective. Anxiety can make uncertainty more salient; anger can narrow attention to perceived injustice; relief can strengthen positive memory. Emotional experience does not replace functional quality, but it changes how functional performance is interpreted and remembered.

Behavioural economics shows why customers do not always behave as the rational, fully informed decision-makers assumed in traditional models. Several principles are especially relevant to quality management.

Reference dependence means that customers evaluate outcomes relative to a reference point, such as a previous price, a promised date or a competitor’s service. A small fee may be accepted when clearly disclosed but resented when introduced after a customer has mentally committed to a total price.

Loss aversion suggests that losses often feel more significant than equivalent gains. Preventing a customer from losing access, money or time may therefore matter more than offering a comparable benefit.

Framing affects interpretation. “Ninety-five per cent available” and “five per cent unavailable” describe the same rate but may produce different reactions. Ethical framing clarifies consequences rather than exploiting misunderstanding.

Choice architecture concerns how options are presented. Defaults, ordering, labels and the number of alternatives influence decisions. Defaults can reduce effort, but they become ethically problematic when they obscure consent or favour the organisation at the customer’s expense.

Present bias leads people to overvalue immediate benefits and undervalue future costs. This matters in subscriptions, financing, preventive healthcare and privacy decisions.

Social proof occurs when customers infer quality from reviews, ratings or the behaviour of others. Organisations must distinguish genuine evidence from manipulated testimonials or fabricated reviews.

These effects imply that quality management must examine not only whether an option is objectively available but also whether customers can understand, compare and use it fairly.

A Framework for Analysing Customer Experience

A practical analysis can proceed through six linked questions:

1. What progress is the customer seeking? Define the functional, emotional and social job.

2. What does the customer expect? Identify promises, prior experiences, norms and minimum acceptable performance.

3. Where are the moments of truth? Map touchpoints and backstage dependencies.

4. What effort and uncertainty are present? Record time, cognitive, procedural, emotional and physical burdens.

5. How is performance interpreted? Examine confirmation or disconfirmation, emotions, trust and perceived fairness.

6. What intervention will improve the whole journey? Prioritise changes by customer importance, failure risk, feasibility and strategic value.

Evidence may include surveys, interviews, complaint records, digital analytics, contact reasons, transaction data, observation and employee insight. Quantitative scores should be interpreted with qualitative evidence. A high average satisfaction score can conceal severe problems for a vulnerable subgroup or at a critical moment.

Practical and Professional Applications

In healthcare, expectation management must never become a substitute for safe care. Patients need understandable information, privacy, dignity and reliable follow-up. In higher education, students evaluate not only teaching but also the coherence of admissions, registration, assessment and support processes. In manufacturing, industrial customers may value continuity, technical support and risk reduction more than product features alone. In hospitality, recovery quality and emotional recognition can strongly influence perceived service.

For quality leaders, customer analysis should connect to process ownership. If customers repeatedly repeat information, the issue may involve fragmented systems, incentive design or unclear accountability rather than employee attitude alone. Voice-of-customer data should therefore enter quality planning, root-cause analysis, service design, training, supplier management and performance review.

Digital channels create additional possibilities. Web and application analytics can reveal abandonment points, search failures and repeated visits. Speech and text analytics can identify complaint themes, sentiment and effort signals, although automated sentiment classification can misinterpret sarcasm, cultural language or distress. Artificial intelligence may personalise recommendations or support agents, but it must be governed for accuracy, explainability, privacy, bias and human escalation.

Illustrative Case: Redesigning a University Fee-Payment Journey

Background

A fictional university introduced an online fee-payment portal intended to reduce queues and administrative workload. The portal was technically operational, yet students reported frustration and contacted the finance office repeatedly.

Situation and Problem

Analytics showed that many students began payment but abandoned the process. Complaints referred to unclear charges, failed authentication and uncertainty about whether a payment had succeeded. Staff measured success primarily through portal availability and average transaction time, while students evaluated the entire journey from viewing the invoice to receiving confirmation.

Analysis

Using JTBD, the central job was defined as: “When a payment deadline is approaching, I want to understand exactly what I owe, complete payment securely and receive proof immediately so that I can remain enrolled without anxiety.”

Expectation–confirmation analysis showed negative disconfirmation. The university’s message implied a quick, simple process, but students encountered multiple screens and delayed confirmation. Kano analysis classified secure payment and accurate balances as must-be attributes, clarity and processing speed as performance attributes, and a downloadable personalised financial summary as a possible excitement attribute.

Journey mapping identified three critical moments of truth: interpreting the invoice, authenticating the payment and confirming completion. Customer-effort analysis revealed that students had to re-enter information already held by the university and contact staff when payment status was unclear. Emotional analysis showed that uncertainty near the deadline amplified frustration.

Approach and Solution

The university consolidated charges into a plain-language statement, displayed a single total with expandable detail, enabled secure sign-in continuity, added a visible payment-status tracker and issued immediate confirmation through the portal and email. A recovery path was added for failed transactions, and staff received authority to verify and resolve duplicate-payment concerns. The university also tested the revised design with students who had accessibility and language needs.

Outcome

The redesigned journey reduced unnecessary steps and made the customer’s desired outcome visible. More importantly, quality ownership shifted from “portal availability” to successful, trusted completion of the payment job. The case illustrates that digital self-service improves experience only when it reduces customer effort and uncertainty across the whole journey.

Learning Points

The case demonstrates that technical functionality is not equivalent to customer-perceived quality. It also shows why expectations, moments of truth, trust, emotion and process design must be analysed together. Measures should include completion, repeat contact, payment-status uncertainty and equitable usability, not merely system uptime.

Challenges, Risks and Limitations

Customer expectations are heterogeneous and sometimes contradictory. One customer requests speed while another wants detailed consultation. Over-customisation can increase complexity and operating cost. Survey responses may be affected by timing, wording, response bias and customers’ inability to articulate latent needs. Stated preferences may also differ from actual behaviour.

Models have boundaries. Expectation–confirmation theory can oversimplify dynamic experiences. Kano classifications depend on research design and change over time. JTBD interviews may be influenced by hindsight and rationalisation. Effort scores can overlook emotional or accessibility burdens. Behavioural insights can be misused to manipulate rather than assist customers.

Common mistakes include treating satisfaction as the only outcome, rewarding employees for speed at the expense of resolution, assuming digital is always easier, relying on averages, confusing novelty with value, making promises that operations cannot keep and interpreting complaints as individual weaknesses rather than process evidence.

Ethical, Governance and Professional Considerations

Customer analytics must respect privacy, purpose limitation, data minimisation, security, informed consent and applicable data-protection requirements. Sensitive attributes should not be used unfairly to exclude, overcharge or provide inferior service. Automated decisions require monitoring for discriminatory outcomes and routes for human review.

Transparency is essential when organisations use personalisation, predictive models, recordings or AI-generated responses. Customers should not be trapped by dark patterns, hidden defaults, confusing cancellation processes or deliberately difficult complaint channels. Professional quality management treats customer autonomy, accessibility, safety and dignity as quality requirements, not optional enhancements.

Current Developments and Best Practices

Emerging practice is moving from isolated satisfaction measurement to continuous journey intelligence. Organisations increasingly combine operational data, conversational analytics, process mining and direct customer research. Real-time signals can support proactive service recovery, but automation should not remove human judgement in high-impact situations.

Best practice involves:

• defining customer jobs and desired outcomes before designing features;
• mapping the entire journey, including backstage processes;
• separating basic requirements from differentiating attributes;
• managing promises honestly and consistently;
• measuring effort, trust, resolution and equity alongside satisfaction;
• segmenting evidence by need, context and vulnerability;
• closing the loop with customers and employees;
• testing changes experimentally and monitoring unintended effects; and
• treating privacy, accessibility and fairness as design requirements.

Chapter Summary

Customer experience quality emerges from the interaction between customer needs, expectations, perceived performance and behavioural context. Expectation–confirmation theory explains satisfaction through comparison between expectations and performance. The Kano model distinguishes basic, performance and excitement attributes, while moments-of-truth analysis reveals where impressions are formed across the customer journey. Jobs-to-be-done identifies the progress customers seek, and customer-effort analysis reveals the burdens that obstruct that progress. Emotions, trust and behavioural biases influence interpretation and decision-making. Effective TQM therefore requires more than measuring satisfaction: it requires designing reliable, understandable, ethical and low-effort journeys supported by evidence, technology and accountable processes.

Key Terms

Need: A condition or outcome that a customer considers important.

Expectation: A belief about what will or should occur.

Perception: The customer’s interpretation of actual performance.

Satisfaction: An evaluation arising from comparison between expectations and perceived performance.

Positive disconfirmation: A situation in which performance exceeds expectations.

Negative disconfirmation: A situation in which performance falls below expectations.

Zone of tolerance: The range between minimum acceptable and desired performance.

Trust: Willingness to accept vulnerability based on confidence in competence, integrity and benevolence.

Kano model: A framework classifying attributes by their effect on satisfaction.

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

Performance attribute: An attribute whose improvement generally increases satisfaction.

Excitement attribute: An unexpected feature capable of creating delight.

Moment of truth: An interaction that significantly shapes customer perception.

Customer journey: The sequence of stages and touchpoints through which a customer pursues an outcome.

Jobs-to-be-done: The progress a customer seeks in a particular situation.

Customer effort: The physical, cognitive, emotional and temporal burden of achieving an outcome.

Reference point: The comparison standard against which an outcome is evaluated.

Loss aversion: The tendency for perceived losses to weigh more heavily than equivalent gains.

Choice architecture: The design of how options and decisions are presented.

Dark pattern: A design practice that manipulates users into choices contrary to their interests.

Review Questions

Short Answer Questions

1. Distinguish customer expectations from customer perceptions.

2. What is negative disconfirmation?

3. Define a must-be attribute in the Kano model.

4. What is meant by a moment of truth?

5. Identify four dimensions of customer effort.

Long Answer Questions

1. Explain expectation–confirmation theory and discuss its managerial implications.

2. Describe the Kano model and explain why quality attributes can change categories over time.

3. Explain how jobs-to-be-done differs from demographic segmentation.

4. Discuss the influence of emotion and trust on perceived quality.

5. Explain how behavioural economics contributes to customer experience management.

Analytical / Application Questions

1. A telecom provider has reliable network coverage but receives complaints about confusing billing and repeated transfers. Analyse the problem using customer journey, effort and expectation–confirmation concepts.

2. Design a research approach to classify the attributes of an online banking service using the Kano model.

3. An organisation wants to use AI to predict customer churn from complaints and interaction data. Evaluate the potential benefits, risks and governance requirements.

22. Multiple Choice Questions with Answers

Question 1

A customer expected a response within one hour and received it after thirty minutes. Which concept best describes this evaluation?

A. Positive disconfirmation

B. Negative disconfirmation

C. Reverse quality

D. Indifferent quality

Correct Answer: A. Positive disconfirmation

Question 2

In the Kano model, secure payment in an online banking service is most likely a:

A. Performance attribute

B. Must-be attribute

C. Excitement attribute

D. Reverse attribute

Correct Answer: B. Must-be attribute

Question 3

Which statement best represents a jobs-to-be-done perspective?

A. Customers aged 18–25 prefer mobile applications

B. Customers buy features listed in a product brochure

C. A commuter hires transport to arrive predictably and without stress

D. High-income customers always prefer premium services

Correct Answer: C. A commuter hires transport to arrive predictably and without stress

Question 4

Which example represents cognitive customer effort?

A. Travelling to a branch

B. Waiting for a technician

C. Repeating an emotional complaint

D. Interpreting a complex set of instructions

Correct Answer: D. Interpreting a complex set of instructions

Question 5

A service feature once considered exciting becomes expected by nearly all customers. This illustrates that Kano categories:

A. Are fixed permanently

B. Can change over time

C. Apply only to physical products

D. Measure employee satisfaction

Correct Answer: B. Can change over time

Question 6

Why can a technically functional self-service system still create poor customer experience?

A. Customers never value technology

B. Functionality may coexist with high effort and uncertainty

C. Technical systems cannot be measured

D. Automation always reduces trust

Correct Answer: B. Functionality may coexist with high effort and uncertainty

Question 7

A customer dislikes a subscription because cancellation is deliberately difficult. This is most closely associated with:

A. Positive framing

B. A dark pattern

C. An excitement attribute

D. Confirmation

Correct Answer: B. A dark pattern

Question 8

Which managerial action best addresses expectation–confirmation risk?

A. Make promises stronger than operational capability

B. Hide delays until the customer complains

C. Align communications with deliverable performance

D. Lower quality while lowering stated expectations

Correct Answer: C. Align communications with deliverable performance

Question 9

A company analyses touchpoints but ignores transfers between departments. What weakness does this reveal?

A. It is optimising isolated interactions rather than the whole journey

B. It is applying loss aversion correctly

C. It is measuring too much emotional data

D. It is using the Kano model excessively

Correct Answer: A. It is optimising isolated interactions rather than the whole journey

Question 10

Which practice is most ethically appropriate when using AI for customer experience analytics?

A. Use personal data without disclosure if predictions improve

B. Remove human review from high-impact decisions

C. Monitor privacy, bias, explainability and escalation requirements

D. Use defaults that conceal commercially beneficial choices

Correct Answer: C. Monitor privacy, bias, explainability and escalation requirements