3. Customer, Stakeholder and Quality Requirement Analysis

Introduction and Context

Total Quality Management begins with a deceptively simple question: what does quality mean to the people who receive, use, regulate, finance, influence, or depend on an organization’s outputs? The answer cannot be assumed from internal specifications alone. A product may conform perfectly to its design and still disappoint customers; a service may be technically efficient yet inaccessible, confusing, or perceived as unfair. Quality therefore has both an internal dimension—conformance to requirements—and an external dimension—fitness for use and value as experienced by relevant stakeholders.

Customer, stakeholder and quality requirement analysis provides the bridge between expectations expressed in ordinary language and the measurable requirements used for design, delivery, control and improvement. It is especially important in improvement projects because resources are limited. Organizations must determine which needs matter most, to whom, under what circumstances, and with what consequences when they are not met.

This chapter develops an integrated approach to that task. It examines voice-of-customer evidence, stakeholder segmentation, customer journeys, Kano analysis, service-quality analysis, quality function deployment and requirements prioritization. The emphasis is not on using tools mechanically, but on interpreting evidence and translating it into critical-to-quality requirements that can guide managerial and operational decisions.

Learning Objectives

After studying this chapter, the learner should be able to:

1. Distinguish customers, users, stakeholders and other sources of quality requirements.

2. Collect and evaluate voice-of-customer and stakeholder evidence using appropriate methods.

3. Segment customers and stakeholders in ways that support meaningful analysis.

4. Use journey mapping, Kano analysis and service-quality dimensions to interpret experience.

5. Convert ambiguous expectations into measurable critical-to-quality requirements.

6. Apply QFD and prioritization methods to connect customer needs with organizational capabilities.

7. Recognize bias, ethical risks, data limitations and implementation challenges.

8. Construct a defensible requirements analysis for a continuous improvement project.

From Voice to Verifiable Requirement

The voice of the customer (VOC) refers to stated and unstated needs, preferences, perceptions and experiences obtained from customers or inferred from their behavior. It is broader than customer complaints. A complaint is a visible signal of dissatisfaction, whereas VOC may also be found in usage patterns, abandoned transactions, support contacts, interviews, reviews and observations of workarounds.

A customer is the recipient of an output, but the recipient may not be the only relevant party. The user operates or experiences the product or service. The purchaser authorizes payment. A regulator establishes mandatory conditions. Employees deliver the service and may experience requirements that affect reliability. Communities, suppliers and owners can also influence the quality system. These groups are stakeholders when they can affect, be affected by, or perceive themselves to be affected by an organization’s activities.

A useful analytical distinction is made among four levels:

• Need: a desired outcome, such as feeling safe or receiving a decision quickly.
• Requirement: a statement of what must be provided to satisfy the need.
• Specification: a precise technical or operational description of the requirement.
• Measure: an indicator used to assess achievement.

For example, “I want faster claims handling” is a need or expressed expectation. “The claim should be acknowledged promptly” is a requirement. “Acknowledgement shall be issued within four business hours of complete submission” is a specification. The percentage of complete claims acknowledged within four hours is a measure.

Quality requirements should be clear, measurable, relevant to a stakeholder, controllable or influenceable by the organization, and connected to an outcome. A strong critical-to-quality (CTQ) statement normally identifies the object, performance characteristic, target, tolerance, population or condition, and measurement method. “Reduce waiting time” is incomplete. “For online applicants submitting complete documentation, median time from submission to eligibility decision shall not exceed two working days, with no more than 5 percent exceeding five working days” is more suitable for improvement work.

Identifying and Segmenting Stakeholders

Requirements analysis becomes unreliable when an organization treats “the customer” as a single homogeneous group. Customers differ in purpose, risk tolerance, technical knowledge, urgency, purchasing power and service context. Segmentation divides a broad population into groups with sufficiently similar needs or behaviors to justify distinct analysis.

Common segmentation bases include demographic or firmographic characteristics, usage frequency, customer value, lifecycle stage, geography, channel, urgency, vulnerability and regulatory status. In a hospital, for example, patients, emergency patients, relatives, clinicians, insurers and regulators have different definitions of quality. In a business-to-business setting, the economic buyer, end user, procurement team and maintenance department may evaluate the same product differently.

Segmentation should serve a decision, not merely describe a population. A useful segment is one for which the organization can identify a distinctive requirement, experience pattern or intervention. Excessive segmentation creates analytical complexity and small samples; insufficient segmentation hides important differences. A practical approach is to begin with a broad stakeholder map, identify material differences, and then segment only where those differences affect quality decisions.

Stakeholder power and interest matrices can help determine engagement priorities, but power should not be confused with importance. Vulnerable users with limited influence may face the greatest quality risks. Ethical analysis requires that their needs not be excluded simply because they are less able to complain or purchase.

Gathering and Evaluating Evidence

No single VOC method is adequate for all requirements. Qualitative methods are valuable for discovering meanings, frustrations and unmet needs. Interviews, focus groups, contextual observation, complaint analysis and diary studies can reveal why a customer behaves in a particular way. Quantitative methods such as surveys, transaction analysis, repeat-contact rates, defect data and structured ratings help estimate prevalence and compare segments.

Directly stated preferences are useful but imperfect. Customers may not be able to articulate latent needs, may answer according to social expectations, or may evaluate a recent incident rather than the complete experience. Behavioral evidence can reveal what people actually do, but behavior also requires interpretation. For example, low use of a digital portal may indicate poor usability, lack of awareness, privacy concerns or an unsuitable customer segment.

Evidence should be triangulated. A requirement becomes more credible when it is supported by different sources—for example, interview comments, abandonment data and observed process delays. Contradictions should not be averaged away. They may indicate segment differences, changing expectations or a trade-off between requirements.

A disciplined VOC process generally involves:

1. Defining the decision and population of interest.

2. Mapping stakeholders and selecting relevant segments.

3. Choosing methods appropriate to the question and context.

4. Collecting verbatim statements, observations and behavioral data.

5. Coding evidence into themes without prematurely converting it into solutions.

6. Validating interpretations with representative stakeholders.

7. Translating themes into measurable requirements and testing their feasibility.

The distinction between a need and a solution is essential. “I need to know the status of my application” expresses an outcome. “Create a mobile application” is one possible solution. If the latter is accepted too early, better alternatives—such as automated messages, a call-back service or a clearer web page—may be overlooked.

Understanding Experience Through the Customer Journey

A customer journey represents the sequence of interactions and experiences through which a customer achieves a goal. It may include awareness, search, purchase, onboarding, use, support, renewal and exit. Journey mapping makes quality visible across organizational boundaries, whereas departmental measures often examine only isolated steps.

A useful journey map contains the customer’s goal, stages, touchpoints, channels, emotions, effort, failure points, backstage processes and relevant measures. The “moments of truth” are interactions that strongly influence trust or perceived value. A technically minor event, such as an unexplained status message, may become critical when the customer is anxious or time-constrained.

Journey analysis should examine both the frontstage experience and the enabling process. If customers wait six days for a response, the visible problem is delay, but the underlying causes may include incomplete information, multiple approvals, queue imbalance or poor system integration. The map therefore supports movement from experience evidence to process investigation without assuming that the customer’s perception identifies the root cause by itself.

Journey maps should be created for specific segments and scenarios. An average journey can conceal the experience of a first-time user, a person with a disability, or a customer requiring urgent assistance. The map should also distinguish customer effort from employee effort. A process that appears simple to the organization may require repeated contacts and manual work by the customer.

Kano Analysis: Different Types of Customer Need

The Kano model classifies quality attributes according to their relationship with satisfaction. Although the categories are not fixed psychological laws, the model is useful for prioritization and product or service design.

Must-be attributes are basic conditions. Their presence may not create strong satisfaction because customers take them for granted, but their absence causes severe dissatisfaction. Security, accurate billing and hygienic facilities often have this character. One-dimensional attributes produce satisfaction roughly in proportion to performance: shorter delivery time, lower cost or higher processing accuracy may improve satisfaction as performance improves. Attractive attributes are unexpected features that can create delight when present but generally do not cause dissatisfaction when absent. Indifferent attributes have little effect on the target customer, while reverse attributes may satisfy some users and annoy others.

Kano questionnaires commonly ask how respondents would feel if a feature were present and absent. Results should be interpreted cautiously because responses can be affected by wording, culture, familiarity and changing expectations. An attractive feature can become a must-be requirement as competitors and society normalize it. Kano analysis is therefore periodic, segment-specific and complementary to operational data.

The managerial implication is that improvement effort should not focus only on delight. Failure to meet must-be requirements can destroy trust, while investment in attractive features is wasteful if basic reliability remains poor. Kano results should be combined with importance, performance, cost, risk and strategic fit.

Service-Quality Analysis

Services create particular difficulties for requirements analysis because they are often produced and consumed simultaneously, involve interaction, and are difficult to evaluate before use. Service quality is therefore shaped by both outcome and process. A technically correct decision may still be judged poor if communication is disrespectful or the process is opaque.

The SERVQUAL tradition identifies five commonly examined dimensions: tangibles, reliability, responsiveness, assurance and empathy. Tangibles concern physical facilities, equipment and visible materials. Reliability concerns performing the promised service dependably. Responsiveness concerns willingness and speed in helping customers. Assurance includes competence, courtesy, credibility and the ability to create confidence. Empathy concerns individualized attention and understanding of customer circumstances.

These dimensions are analytical lenses rather than universal measures. A financial service may emphasize security and accuracy; a public emergency service may prioritize availability and response time; an educational service may emphasize learning support, fairness and feedback. Researchers and managers should define dimensions in the language of the relevant segment and validate the measurement instrument.

A gap perspective can distinguish what customers expect, what management believes they expect, what is specified, what is actually delivered and what is communicated. Such gaps explain why improving employee effort alone may not improve perceived quality. A promise that exceeds operational capability can create dissatisfaction even when delivery is objectively acceptable.

Translating Needs into CTQs and QFD

Quality Function Deployment (QFD) is a structured method for translating the “voice of the customer” into design and operational characteristics. Its central instrument, the House of Quality, usually connects customer requirements (“whats”) with technical or process characteristics (“hows”). It may also display customer importance, competitive comparisons, relationships, technical correlations and target values.

A simplified QFD sequence is as follows. First, list customer needs in neutral language and remove duplicate statements. Second, assign importance ratings using evidence rather than managerial assumption. Third, identify measurable characteristics that influence each need. Fourth, score the strength of relationships between needs and characteristics. Fifth, examine correlations and conflicts among technical characteristics. Sixth, set target values, identify responsibilities and carry priorities into subsequent process or production planning.

Suppose customers of an outpatient clinic state that they want “a less stressful visit.” This may be decomposed into understandable directions, predictable waiting, privacy, clear instructions and confidence in clinical competence. Technical characteristics might include registration time, percentage of visits beginning within the promised window, readability of instructions, noise level and staff communication training. QFD does not prove causation; it makes assumptions explicit so that they can be discussed and tested.

QFD is most useful when it remains connected to evidence and action. A visually impressive matrix with arbitrary ratings creates false precision. Importance scores should be normalized, relationship scales defined, and disagreements documented. The final output should include CTQs, owners, targets, measurement plans and unresolved trade-offs.

Prioritizing Requirements for Improvement

Organizations rarely have the capacity to optimize every requirement simultaneously. Prioritization should therefore combine customer importance with current performance, risk, feasibility and strategic value. A high-importance attribute with poor performance is an obvious candidate, but a low-frequency safety failure may deserve priority over a frequent minor inconvenience.

Useful approaches include weighted scoring, Pareto analysis, risk priority assessment, analytic hierarchy processes, conjoint analysis and cost-of-quality analysis. A basic weighted score can be expressed as:

Priority score = importance × performance gap × consequence or risk × strategic relevance.

The numerical scale is less important than the logic, consistency and transparency of the scoring. Scores should not conceal ethical or regulatory thresholds. A legally required safety condition cannot be traded away simply because its customer rating is low. Similarly, a small but vulnerable population should not automatically lose priority to a larger population.

Prioritization should distinguish improvement targets from monitoring requirements. Some CTQs may already perform well but require continued control. Others may have uncertain evidence and should be investigated before major investment. A portfolio view is often better than a single ranking: immediate corrective action, targeted redesign, further research, routine control and deliberate innovation may each be appropriate responses.

Illustrative Case: Improving a University Digital Admissions Journey

Background

The following is an illustrative case. A university notices that qualified applicants are abandoning its postgraduate admissions process. Overall application numbers remain stable, but the conversion from started application to completed submission has declined. Complaints mention confusing requirements, slow responses and uncertainty about payment status.

Situation and Analysis

The improvement team maps stakeholders: applicants, academic departments, admissions staff, finance staff, international support staff and regulatory authorities. Applicants are segmented into domestic and international candidates, first-time and returning users, and applicants requiring accessibility support. Interviews reveal that “simple application” means different things across segments. International applicants need document guidance and predictable status information; first-time applicants need explanations of academic terminology; returning users want fewer repeated data fields.

Journey mapping identifies a critical period between document upload and confirmation of payment. Applicants cannot see whether a document has been accepted, rejected or merely received. Contact-centre data show repeated enquiries about status, while system logs show that applications with payment exceptions remain in a manual queue. Observation also reveals that the form uses technical terms not understood by many applicants.

Kano analysis suggests that secure payment and confirmation are must-be attributes. Shorter completion time is one-dimensional. A personalized checklist is attractive for some segments but cannot compensate for missing confirmation. Service-quality analysis identifies weaknesses in reliability, responsiveness and assurance.

Requirements and QFD Translation

The team converts evidence into CTQs:

• The system shall display receipt status for each uploaded document immediately after successful upload.
• Applicants shall receive a payment confirmation or an actionable failure message within five minutes of a transaction.
• At least 95 percent of complete applications shall receive an eligibility-status update within two working days.
• Instructions for required documents shall be understandable to a first-time applicant and available in an accessible digital format.
• Applicants shall be able to obtain assistance through a response channel within one working day.

QFD links these requirements to document-status integration, payment gateway reconciliation, queue capacity, plain-language redesign, accessibility testing and service-level monitoring. Relationship analysis reveals a trade-off: more manual document review may increase assurance but worsen response time. The team therefore proposes risk-based review, reserving detailed manual checks for high-risk cases.

Approach and Outcome

The university pilots the redesigned journey with two applicant segments. It introduces real-time receipt messages, automated payment reconciliation, plain-language guidance and a visible status timeline. Measures include completion rate, repeat contacts, payment exceptions, response-time compliance, accessibility defects and applicant confidence ratings.

The pilot shows fewer status enquiries and faster resolution of payment exceptions. The team does not attribute all improvement to one feature; the pilot design and segmented measures allow comparison of changes across stages. Governance review confirms that automated decisions will not reject applications without human review and that applicants can correct inaccurate records.

Learning Points

The case demonstrates that VOC must be connected to process evidence. “Make the application easier” becomes useful only after the journey is decomposed into observable requirements. It also shows why segment analysis matters: a solution valuable to international applicants may be unnecessary for returning users. Finally, CTQs must include targets, conditions and measurement methods so that improvement can be verified.

Risks, Limitations and Professional Considerations

Several errors commonly weaken requirements analysis. Asking only existing, vocal customers excludes silent users and people who have abandoned the process. Treating satisfaction scores as complete evidence overlooks latent needs and operational causes. Combining all segments into one average can hide inequity. Converting every complaint directly into a requirement may overreact to unusual events, while dismissing complaints as anecdotal can conceal systemic failure.

Sampling bias, leading questions, recall error, non-response and poor translation affect VOC quality. Survey scales may produce culturally different response patterns. Importance ratings may be inflated when respondents are asked about every attribute independently. QFD ratings may create an illusion of mathematical accuracy. These limitations require method triangulation, transparent assumptions and periodic validation.

Ethical and governance issues are central. Customer data should be collected for a legitimate purpose, minimized, protected and retained appropriately. Participants should understand how feedback will be used. Sensitive groups require accessible participation methods and careful interpretation. Algorithms used to segment customers or prioritize service may reproduce historical discrimination. Organizations should test for disparate impacts, preserve human accountability and provide appeal or correction mechanisms where decisions affect rights, access or safety.

Requirements also involve trade-offs. Faster service may increase error risk; personalization may increase privacy exposure; lower cost may reduce resilience; standardization may conflict with legitimate individual needs. These conflicts should be made visible to decision-makers rather than hidden within an aggregate score.

Digital Tools and Emerging Practice

Customer relationship management systems, journey analytics, text mining, speech analytics and process mining can expand the evidence base. Natural-language processing can classify large volumes of complaints and reviews, while sentiment analysis can identify themes for investigation. Process mining can connect customer-reported delays with actual event logs. Digital experimentation can compare alternative messages or workflow designs.

These tools do not replace interpretation. Automated sentiment labels may misunderstand sarcasm, multilingual language or culturally specific expressions. Data from digital channels overrepresent digitally active users. Predictive models may optimize response speed while overlooking fairness or emotional reassurance. Human review, data-quality controls, explainability and governance are therefore essential.

Emerging practice is moving toward continuous listening rather than annual surveys, integrated operational and experience dashboards, accessibility-by-design, real-time journey monitoring and co-design with customers. The strongest systems treat requirements as living hypotheses: they are measured, reviewed after process changes, and revised as contexts and expectations evolve.

Best-Practice Guidance

A mature requirements analysis should:

• begin with a clearly defined improvement decision;
• include customers, users, employees, regulators and vulnerable stakeholders where relevant;
• use both qualitative insight and quantitative evidence;
• analyze meaningful segments and specific journeys;
• separate needs from proposed solutions;
• translate expectations into observable CTQs with targets and tolerances;
• use Kano, service-quality and QFD tools as complementary lenses;
• document assumptions, trade-offs and evidence strength;
• prioritize according to importance, performance, risk, equity and feasibility;
• assign ownership and measurement responsibility; and
• revisit requirements after implementation and environmental change.

Chapter Summary

Customer and stakeholder analysis translates diverse experiences and expectations into requirements that an organization can design, deliver and improve. Effective analysis distinguishes needs, requirements, specifications and measures; identifies relevant stakeholder segments; and combines interviews, observation, surveys, complaints and behavioral data. Customer journey mapping reveals quality across touchpoints and organizational boundaries. Kano analysis distinguishes basic, performance and attractive attributes, while service-quality analysis examines reliability, responsiveness, assurance, empathy and related dimensions. QFD connects customer needs to technical and process characteristics, and prioritization combines importance with performance gaps, risk, strategic value and feasibility. Reliable CTQs are measurable, segment-sensitive and ethically governed. Digital tools can strengthen continuous listening, but they require human interpretation, privacy protection and fairness controls.

Key Terms

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

Stakeholder: A party that can affect, be affected by, or perceive itself affected by organizational activity.

Customer Segment: A group of customers with sufficiently similar needs or behaviors for analytical purposes.

Need: A desired outcome or condition sought by a customer or stakeholder.

Requirement: A statement of what must be provided to satisfy a need.

Specification: A precise description of required performance or characteristics.

Critical-to-Quality (CTQ): A measurable characteristic that is essential to stakeholder-perceived or regulated quality.

Customer Journey: The sequence of stages and interactions through which a customer pursues a goal.

Moment of Truth: An interaction that strongly influences a customer’s trust or quality perception.

Kano Model: A framework classifying attributes according to their effect on satisfaction and dissatisfaction.

Must-Be Attribute: A basic attribute whose absence causes strong dissatisfaction.

One-Dimensional Attribute: An attribute for which higher performance generally produces higher satisfaction.

Attractive Attribute: An unexpected attribute that can create delight when present.

Service Quality: The perceived quality of both service outcome and service delivery process.

SERVQUAL Dimensions: Analytical dimensions commonly including tangibles, reliability, responsiveness, assurance and empathy.

Quality Function Deployment: A structured method for translating customer requirements into technical and process characteristics.

House of Quality: A QFD matrix linking customer requirements with organizational or technical responses.

Triangulation: The use of multiple evidence sources or methods to strengthen interpretation.

Requirements Prioritization: The systematic ranking of requirements according to importance, gaps, risk and other decision criteria.

Voice-of-Process Evidence: Operational data showing how a process performs in relation to customer outcomes.

Review Questions

Short Answer Questions

1. Distinguish a customer need, a requirement, a specification and a measure.

2. Why is stakeholder segmentation important in quality requirement analysis?

3. What is the purpose of a customer journey map?

4. Explain the difference between a must-be and an attractive Kano attribute.

5. What makes a requirement a useful CTQ statement?

Long Answer Questions

1. Explain how qualitative and quantitative VOC methods can be combined to produce reliable requirements.

2. Discuss the major stages of QFD and the role of the House of Quality in continuous improvement.

3. Explain how service-quality dimensions can be adapted to different industries and customer contexts.

4. Analyze the benefits and limitations of Kano analysis as a requirements-prioritization tool.

5. Describe the ethical, data-quality and governance risks associated with customer segmentation and digital feedback analysis.

Analytical / Application Questions

1. A bank receives complaints that its loan process is “too difficult.” Design a stakeholder segmentation, journey-analysis approach and at least five measurable CTQs.

2. A hospital has excellent clinical outcomes but poor patient satisfaction because of waiting, communication and uncertainty. Use Kano analysis, service-quality dimensions and QFD to propose an improvement portfolio.

3. An organization must choose between reducing response time and increasing the depth of manual review. Construct a prioritization analysis that considers customer value, safety, equity, risk and operational feasibility.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a specification from a customer need?

A. A specification expresses a broad emotional expectation.

B. A specification precisely defines required performance or characteristics.

C. A specification is always obtained only through surveys.

D. A specification describes a stakeholder’s organizational power.

Correct Answer: B. A specification precisely defines required performance or characteristics.

Question 2

Why should an improvement team avoid treating all customers as one homogeneous group?

A. Different segments may have materially different quality requirements and experiences.

B. Segmentation eliminates the need for quantitative evidence.

C. All customers usually value exactly the same attributes.

D. Segmentation guarantees that improvement costs will decrease.

Correct Answer: A. Different segments may have materially different quality requirements and experiences.

Question 3

Which example is most clearly a measurable CTQ?

A. Customers want a friendlier service.

B. The process should be improved significantly.

C. Ninety-five percent of complete applications receive a decision within two working days.

D. Employees should care more about customers.

Correct Answer: C. Ninety-five percent of complete applications receive a decision within two working days.

Question 4

In the Kano model, failure to provide a must-be attribute generally causes:

A. Strong dissatisfaction.

B. No change in customer perception.

C. Delight among all customers.

D. Higher tolerance for other defects.

Correct Answer: A. Strong dissatisfaction.

Question 5

What is a principal benefit of customer journey mapping?

A. It replaces process-performance measurement.

B. It limits analysis to a single department.

C. It reveals quality across interactions and organizational boundaries.

D. It ensures that every customer has the same experience.

Correct Answer: C. It reveals quality across interactions and organizational boundaries.

Question 6

Which QFD activity connects customer requirements with technical or process responses?

A. Removing all customer importance ratings.

B. Assessing the relationship between the “whats” and the “hows.”

C. Ranking employees by personal preference.

D. Measuring only financial performance.

Correct Answer: B. Assessing the relationship between the “whats” and the “hows.”

Question 7

A survey shows that customers rate a feature as highly important, but complaints and usage data show little evidence that it affects outcomes. What is the best response?

A. Accept the survey score as conclusive.

B. Discard all survey data immediately.

C. Triangulate the evidence and investigate segment or measurement differences.

D. Implement the most expensive solution available.

Correct Answer: C. Triangulate the evidence and investigate segment or measurement differences.

Question 8

Which situation illustrates a service-quality reliability problem?

A. A facility has modern furnishings but gives inconsistent information.

B. A staff member uses a customer’s preferred name.

C. A customer receives the promised service accurately and consistently.

D. A website uses accessible color contrast.

Correct Answer: A. A facility has modern furnishings but gives inconsistent information.

Question 9

Why should a low-frequency safety failure sometimes receive higher priority than a frequent minor inconvenience?

A. Frequency is the only valid prioritization criterion.

B. Safety consequences and risk may outweigh occurrence frequency.

C. Minor inconveniences are never relevant to quality.

D. Safety requirements cannot be measured.

Correct Answer: B. Safety consequences and risk may outweigh occurrence frequency.

Question 10

What is an important governance safeguard when AI is used to analyze customer feedback?

A. Allow the algorithm to make all decisions without review.

B. Ignore underrepresented groups because their data are limited.

C. Use human oversight, data-quality controls and fairness checks.

D. Collect unlimited personal data for better prediction.

Correct Answer: C. Use human oversight, data-quality controls and fairness checks.