Product and Service Design

Introduction

Product and service design converts customer and organisational requirements into offerings that can be produced, delivered, supported and eventually retired. It is therefore more than industrial styling or service improvement. Design decisions determine much of an offering’s cost, quality, capacity requirement, environmental impact, reliability and customer experience before operations begin. In many industries, the majority of product cost is committed during design, even though expenditure occurs later during purchasing, manufacturing, distribution and after-sales service.

Operations managers must consequently work with marketing, engineering, procurement, finance, information technology, sustainability specialists and customers. The central challenge is to design an offering that creates customer value while remaining feasible, safe, economical, adaptable and responsible throughout its life cycle.

This chapter develops an integrated approach using design thinking, quality function deployment, value analysis, design for manufacturability, service blueprinting, modularity, mass customization, life-cycle thinking and concurrent engineering.

Learning Objectives

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

1. Explain the strategic role and stages of product and service design.
2. Apply design thinking to ambiguous operational problems.
3. Translate customer requirements into technical priorities using quality function deployment.
4. Use value analysis and design-for-manufacturability principles to improve value and reduce avoidable cost.
5. Construct and interpret a service blueprint.
6. Evaluate modularity and mass customization decisions.
7. Apply life-cycle thinking to economic, environmental and social impacts.
8. Explain how concurrent engineering improves cross-functional design decisions.
9. Evaluate design alternatives using quality, cost, risk, capacity and sustainability criteria.

1. The Strategic Role of Design

A design specifies what an organisation offers and how its operations will create and deliver it. A product design may define materials, dimensions, performance, reliability, safety features, packaging and repairability. A service design may define customer journeys, employee actions, information flows, facilities, technology and recovery procedures.

Design influences the five classic operations performance objectives:

• Quality: conformance, functionality, reliability and customer experience.
• Speed: processing time, waiting time and time to market.
• Dependability: consistency of delivery and performance.
• Flexibility: ability to offer variety or respond to changing demand.
• Cost: labour, materials, equipment, energy, waste, warranty and service costs.

These objectives can conflict. Greater variety may increase customer choice but also increase forecasting difficulty, inventory and training requirements. A highly customised service may improve experience but reduce speed and consistency. Effective design makes such trade-offs explicit rather than allowing them to emerge accidentally during implementation.

Product, service and experience design

Products and services increasingly form integrated systems. A medical device may be sold with installation, software, training and maintenance. A vehicle may include financing, digital connectivity and subscription services. Consequently, the design object is often a product-service system, not a physical item alone.

Important design decisions include:

1. Target customer and use context: Who uses the offering, where, when and under what constraints?
2. Value proposition: Which problem is solved, and why will customers prefer this solution?
3. Technical and operational requirements: What performance, capacity, safety and regulatory conditions apply?
4. Process architecture: How will the offering be produced or delivered?
5. Support system: How will installation, maintenance, complaints, returns and end-of-life handling be managed?

2. The Design Process and Design Thinking

A conventional design process often proceeds from requirements to concepts, detailed design, testing and launch. Design thinking complements this process by beginning with users and by treating early solutions as hypotheses to be tested. A commonly used cycle contains five overlapping activities:

1. Empathise: observe and engage with users to understand behaviour, context and latent needs.
2. Define: frame a specific problem based on evidence.
3. Ideate: generate several possible solutions rather than selecting the first idea.
4. Prototype: create a low-cost representation of the solution.
5. Test: obtain user feedback, learn and revise.

The cycle is iterative. Testing may reveal that the original problem definition was incomplete. Design thinking is especially useful where customer needs are uncertain, poorly articulated or changing rapidly. It does not replace engineering validation, financial analysis, regulatory approval or production planning. Rather, it improves the quality of the problem and concept before those activities require substantial commitment.

Example of design-thinking application

Suppose a university wants to reduce queues at its student service centre. Interviews may reveal that students do not merely dislike waiting; they are uncertain about which documents are required and whether their case is complete. A solution could therefore combine pre-visit guidance, online document checking, appointment scheduling and a redesigned counter process. The insight changes the problem from “serve students faster” to “remove uncertainty before and during service.”

Good practice and limitations

Useful design-thinking practice includes direct observation, inclusion of users with disabilities, rapid prototypes, evidence-based iteration and explicit documentation of assumptions. Limitations include small or unrepresentative user samples, difficulty converting qualitative insight into technical specifications, and the risk that attractive prototypes conceal operational or financial infeasibility. Cross-functional review is therefore essential.

3. Quality Function Deployment

Quality function deployment (QFD) is a structured method for translating the voice of the customer into design and operational requirements. Its best-known representation is the House of Quality. The method helps a team determine which technical characteristics deserve attention and how the proposed design compares with competitors or existing alternatives.

Typical QFD stages are:

1. Identify customer requirements, often called “whats.”
2. Assign importance ratings to those requirements.
3. Identify measurable technical characteristics, or “hows.”
4. Record the strength of each relationship between customer requirements and technical characteristics.
5. Examine correlations among technical characteristics, including conflicts.
6. Set technical priorities and target values.
7. Use the results to guide subsequent design, process and control decisions.

A simplified priority calculation is:

where P_j is the unnormalised priority of technical characteristic j, I_i is the importance rating of customer requirement i, and R_ij is the relationship score between requirement i and characteristic j. The summation covers m customer requirements. Scores must be defined consistently, for example 0 = no relationship, 1 = weak, 3 = moderate and 9 = strong. The result is a prioritisation aid, not an objective truth. It assumes that ratings and relationship scores are sufficiently reliable and that additive scoring is an acceptable approximation.

If customer importance ratings are revised by competitive evaluation, a weighted form may be used:

where W_i is the chosen weighted importance of requirement i. If the weights are normalised so that ∑W_i = 1, priorities are comparable as relative scores. QFD does not determine the final design by itself; cost, risk, regulation, capacity and technical feasibility must also be considered.

Illustrative QFD calculation

A parcel-delivery company identifies three customer requirements: reliable arrival (importance 5), easy tracking (importance 4) and low damage (importance 4). Two technical characteristics are delivery process control and package protection. Relationship scores are:

The priorities are:

• Process control = (5 × 9) + (4 × 3) + (4 × 1) = 61.
• Package protection = (5 × 1) + (4 × 0) + (4 × 9) = 41.

Process control receives the higher calculated priority, although package protection remains important. Management should next examine the cost and feasibility of improving each characteristic.

QFD is valuable because it creates traceability from customer language to engineering and process decisions. Its weaknesses include subjective ratings, possible omission of unspoken needs, excessive complexity and a tendency to become a documentation exercise. Facilitated discussion and evidence from complaints, observation, experiments and market research improve its usefulness.

4. Value Analysis and Value Engineering

Value analysis examines an existing product or service; value engineering applies similar reasoning during new design. Both seek to achieve required functions at an appropriate total cost without reducing essential performance, safety or compliance.

A basic conceptual expression is:

The expression is a decision concept rather than a universal accounting measure. “Function” may be assessed qualitatively or through a defined performance index, while cost should preferably include relevant life-cycle cost rather than purchase price alone.

Functional analysis asks what a component or activity must do. Functions are often expressed with a verb and a noun, such as “support load,” “transfer information,” “protect contents” or “verify identity.” The team then asks whether the function can be delivered more simply, reliably or economically.

Relevant cost categories include material, labour, tooling, energy, maintenance, downtime, warranty, failure, disposal and customer support. Cost reduction that increases defects, risk or environmental harm is not genuine value improvement.

Value-analysis procedure

1. Select a significant cost, quality or performance opportunity.
2. Gather customer, technical, process and cost information.
3. Identify primary and secondary functions.
4. Generate alternative ways of delivering required functions.
5. Evaluate alternatives against performance, risk, cost and compliance.
6. Test and implement the preferred option.
7. Monitor realised benefits.

For example, replacing a metal bracket with a polymer component may reduce mass and material cost, but the team must verify strength, temperature resistance, fire behaviour, tooling cost, recyclability and supply risk. Value analysis therefore requires engineering judgement, not simply substitution of the cheapest material.

5. Design for Manufacturability and Assembly

Design for manufacturability (DFM) develops designs that can be produced consistently using available processes, equipment, materials and skills. Design for assembly (DFA) focuses on efficient joining, handling, orientation and inspection. Together, DFM/DFA reduce complexity and improve quality by preventing avoidable production difficulty.

Typical principles include:

• reduce the number of parts where this does not compromise repairability or safety;
• use standard, readily available components;
• design parts for easy orientation and handling;
• provide adequate access for tools and inspection;
• minimise unnecessary tolerances and special processes;
• design mistake-proof features that prevent incorrect assembly;
• avoid excessive variation in fasteners and materials;
• consider process capability before specifying tight tolerances;
• design for cleaning, maintenance and safe disassembly.

A tolerance is not automatically improved by making it narrower. Tight tolerances can increase machining, inspection and scrap costs. The correct tolerance is the widest range that still delivers required function and safety. Design teams should connect critical characteristics to process capability studies and control plans.

DFM also applies to digital and service operations. A software interface should reduce unnecessary data entry and error opportunities. A service form should request only information needed for a decision. In both cases, design simplicity can reduce processing time and defects.

6. Service Design and Service Blueprinting

Services are often produced and consumed simultaneously, involve customer participation and contain substantial variability. A service blueprint makes the service process visible by mapping customer actions, employee actions, support processes and physical or digital evidence.

A typical blueprint contains:

• Customer actions: steps taken by the customer.
• Frontstage actions: employee or system activities visible to the customer.
• Backstage actions: activities hidden from the customer but required for delivery.
• Support processes: information, suppliers, technology and administration.
• Physical evidence: facilities, documents, websites, messages or receipts experienced by the customer.
• Lines of interaction and visibility: boundaries showing contact and what remains unseen.

Figure: A simplified service blueprint showing visible and hidden activities.

Blueprinting helps identify failure points, handoff delays, duplicated data entry and unclear ownership. A bank, for instance, may discover that a customer sees a fast online application while backstage verification remains manual and slow. Improvement may require redesigning the backstage process rather than adding more front-office staff.

7. Modularity and Mass Customization

A modular design divides an offering into relatively independent modules with defined interfaces. Modules may be combined in different configurations while sharing common components, processes or platforms. Examples include configurable software packages, vehicle platforms, furniture systems and standardised hospital-room layouts.

Modularity can provide:

• product variety without designing every product from zero;
• economies of scale for common components;
• easier maintenance and upgrading;
• shorter development time;
• simpler training and inventory management.

However, modules require stable interfaces and may impose performance, aesthetic or size compromises. Excessive modularity can increase connectors, duplication and coordination effort.

Mass customization seeks to provide meaningful individual choice with near mass-production efficiency. It depends on disciplined postponement, configurable architectures, digital customer input, flexible processes and accurate information. A common approach is to produce a generic platform or semi-finished module and delay final differentiation until demand information is available.

Managers should distinguish genuine customer value from unlimited variety. Variety has operational costs, including more stock-keeping units, forecasting error, setup time, quality risk and customer decision difficulty. A useful design question is: “Which attributes should be customisable, and which should remain standardised?”

8. Life-Cycle Thinking and Sustainability

Life-cycle thinking considers impacts from raw-material extraction through manufacture, distribution, use, maintenance and end-of-life. It prevents improvement in one stage from simply shifting burden to another. For example, a lighter product may reduce transport emissions but require a difficult-to-recycle composite material.

A simplified life-cycle cost model is:

where LCC is life-cycle cost, C₀ is initial cost, C_t is cost incurred in period t, r is the discount rate per period, T is the analysis horizon and S_T is residual or salvage value at the end. Costs must be measured in consistent currency and time units. The model assumes a chosen discount rate and reasonably estimable future costs; uncertainty should be tested through sensitivity analysis.

Environmental assessment may consider energy, greenhouse-gas emissions, water, materials, toxicity and waste. Social considerations include worker safety, human rights, accessibility and effects on communities. Design decisions should comply with applicable product-safety, consumer-protection, data-protection, accessibility and environmental regulations.

Life-cycle thinking supports design for durability, repair, upgrade, reuse, remanufacture and recycling. Claims such as “green” or “carbon neutral” should be evidence-based, clearly bounded and not misleading. Governance should assign responsibility for data quality, supplier verification and trade-off approval.

9. Concurrent Engineering

Sequential development passes work from marketing to engineering to operations and then to service. Although simple to manage, this approach can discover feasibility problems late, when changes are expensive. Concurrent engineering brings relevant functions together early so that product, process, supply chain, quality and service requirements are considered simultaneously.

A concurrent engineering team may include customers, product designers, manufacturing engineers, procurement, quality, logistics, finance, maintenance, service personnel and compliance specialists. Useful practices include cross-functional design reviews, shared digital models, early supplier involvement, failure-mode analysis, prototype testing and clearly defined decision rights.

Concurrent engineering does not mean that every person attends every meeting. It means that dependencies are identified early and information is exchanged at the point where decisions are made. Effective teams use stage gates: concept approval, design freeze, pilot approval and launch review. A stage gate should permit continuation, revision or cancellation based on evidence.

Risks include conflict between functional goals, unclear accountability, excessive meetings and premature commitment to a consensus solution. Strong leadership, common measures, documented assumptions and disciplined escalation reduce these risks.

10. Integrated Design Evaluation

A design should be evaluated against a balanced set of criteria rather than a single cost estimate. A practical evaluation matrix may include:

No matrix removes judgement. Its purpose is to make assumptions visible and prevent one attractive feature from dominating the decision.

Applied Case: Illustrative Smart Medication Dispenser

Background

A fictional healthcare-equipment company, MedAssist, plans a home medication dispenser for older adults who take several prescriptions. The product must remind users, release the correct dose, notify a caregiver when a dose is missed and remain simple to refill.

Problem

Early market research shows that users value reliability and ease of use more than a large number of digital features. Engineers initially propose a complex touchscreen, but service staff warn that setup and troubleshooting would be difficult. Procurement also reports that a specialised dispensing mechanism would create supplier dependence.

Analysis

A design-thinking team observes users, caregivers and pharmacists. It identifies three major needs: clear confirmation of the next dose, prevention of incorrect dispensing and rapid support when an exception occurs. QFD translates these into technical characteristics such as dose accuracy, alarm audibility, interface simplicity, battery backup and remote diagnostic capability.

Value analysis identifies the touchscreen as a weak contributor to core function for many users. A simpler physical interface with optional mobile access is considered. DFM/DFA review reduces the number of fasteners and makes the refill cassette keyed so it cannot be inserted incorrectly. Modularity separates the dispensing mechanism, communication module and power unit, allowing future upgrades without replacing the entire product.

A service blueprint reveals that a missed dose requires coordination among the device, caregiver notification platform, call centre and pharmacy. The company defines escalation rules and a clear ownership point rather than assuming that the device alone delivers the service.

Concurrent engineering brings regulatory, manufacturing, software, procurement and after-sales teams into the prototype reviews. Life-cycle analysis considers battery replacement, electronic waste and repair access.

Approach and outcome

MedAssist pilots two prototypes with users and caregivers. The simpler interface produces fewer interaction errors, while modular construction reduces repair time. The company retains remote diagnostics but postpones optional analytics until reliability data are available. The final design is approved subject to safety testing, cybersecurity controls, usability validation and a service-readiness review.

The case demonstrates that successful design is not the maximisation of features. It is the disciplined integration of user value, technical performance, operational capability, risk, support and life-cycle responsibility.

Challenges, Ethics and Contemporary Developments

Design teams face uncertain demand, compressed development schedules, supplier disruption, cybersecurity threats, intellectual-property constraints and pressure to launch quickly. Digital twins, additive manufacturing, cloud platforms, generative design and artificial intelligence can accelerate concept generation and simulation. However, AI-generated designs require human verification for safety, bias, explainability, intellectual property and manufacturability. Training data may reproduce existing exclusions, particularly where users with disabilities or minority needs are underrepresented.

Data-rich services also create privacy obligations. Organisations should collect only necessary data, obtain appropriate consent, control access, protect data throughout its life and explain automated decisions. Product connectivity expands the attack surface; secure update mechanisms and vulnerability response must be designed from the beginning.

Best practice is therefore to combine customer research with engineering evidence, involve operations early, test realistic use conditions, document trade-offs, design for repair and recovery, and monitor actual performance after launch. Post-launch learning should feed the next design cycle through complaints, warranty data, usage analytics, employee observations and sustainability indicators.

Chapter Summary

Product and service design is a strategic operations activity because it determines customer value, process requirements, cost, quality, flexibility, risk and life-cycle impact. Design thinking helps teams understand users and test uncertain assumptions. QFD translates customer requirements into technical priorities, while value analysis and value engineering examine whether required functions can be delivered more effectively. DFM and DFA make designs easier to produce, assemble, inspect and maintain. Service blueprinting exposes visible and hidden activities and clarifies service failure points. Modularity and mass customization balance variety with operational efficiency. Life-cycle thinking evaluates economic, environmental and social consequences beyond the point of sale. Concurrent engineering integrates functions early and reduces late design changes. Effective design decisions require evidence, cross-functional collaboration, ethical governance, regulatory compliance and continuous learning after launch.

Key Terms

Concurrent engineering: Cross-functional development in which product, process, supply and service decisions are considered together.

Design for assembly: Designing components and interfaces to simplify joining, handling, orientation and inspection.

Design for manufacturability: Designing an offering so it can be produced consistently and economically with available processes.

Design thinking: A user-centred, iterative approach involving empathy, problem definition, ideation, prototyping and testing.

House of Quality: A QFD matrix linking customer requirements to technical characteristics.

Life-cycle cost: The discounted total cost incurred over an offering’s relevant life.

Life-cycle thinking: Consideration of impacts from material extraction through use and end-of-life.

Mass customization: Providing meaningful variety with processes approaching the efficiency of mass production.

Modularity: Division of an offering into components with defined interfaces that can be combined or replaced.

Postponement: Delaying final differentiation until better demand or customer information is available.

Quality function deployment: A structured method for translating customer needs into design and process requirements.

Service blueprint: A visual map of customer actions, frontstage activity, backstage activity, support processes and evidence.

Stage gate: A formal decision point at which evidence is reviewed before development continues.

Value analysis: Systematic examination of an existing offering’s functions and costs to improve value.

Value engineering: Application of value-improvement methods during new design.

Voice of the customer: Customer needs, expectations and problems gathered through research and interaction.

Design interface: A defined connection or rule that enables modules or systems to interact.

Product-service system: An integrated offering combining physical products with services, information or support.

Review Questions

Short Answer Questions

1. Why do design decisions have a major influence on operations cost and quality?
2. What are the five activities commonly associated with design thinking?
3. What is the purpose of the House of Quality?
4. Distinguish design for manufacturability from design for assembly.
5. Identify four layers or elements commonly included in a service blueprint.

Long Answer Questions

1. Explain how QFD translates customer requirements into technical and operational priorities. Include its benefits and limitations.
2. Discuss how modularity can support mass customization, and explain the operational costs of excessive variety.
3. Explain how life-cycle thinking changes the evaluation of a product design compared with a purchase-price approach.
4. Compare sequential design with concurrent engineering and identify conditions required for successful cross-functional development.
5. Discuss how value analysis, DFM/DFA and service blueprinting can be combined in the design of a product-service system.

Analytical / Application Questions

1. A retailer receives complaints about late deliveries and damaged packages. Construct three customer requirements and three technical characteristics that could form the basis of a QFD study. Explain the likely relationships.
2. A manufacturer is considering a cheaper material for a component. Analyse the decision using function, life-cycle cost, quality, safety, supply risk and end-of-life criteria.
3. Design a brief service blueprint for an online university enrolment process. Identify one likely failure point in each of the customer, frontstage, backstage and support layers, and recommend an improvement for each.

Multiple Choice Questions with Answers

Question 1

Which activity in design thinking focuses primarily on understanding users and their context?

A. Empathise

B. Ideate

C. Prototype

D. Launch

Correct Answer: A. Empathise

Question 2

In QFD, a relationship score of 9 most commonly represents which relationship?

A. No relationship

B. Weak relationship

C. Moderate relationship

D. Strong relationship

Correct Answer: D. Strong relationship

Question 3

Using P = ∑IᵢRᵢⱼ, what is the priority for a technical characteristic with relationships 9, 3 and 1 and importance ratings 5, 4 and 4?

A. 41

B. 49

C. 61

D. 72

Correct Answer: C. 61

Question 4

Which activity is most directly associated with design for assembly?

A. Increasing the number of unique fasteners

B. Designing parts for easy orientation and joining

C. Delaying all inspection until final delivery

D. Maximising the number of product variants

Correct Answer: B. Designing parts for easy orientation and joining

Question 5

Which element of a service blueprint represents activities hidden from the customer?

A. Physical evidence

B. Customer actions

C. Backstage actions

D. Frontstage actions

Correct Answer: C. Backstage actions

Question 6

What is a principal operational advantage of modularity?

A. It eliminates all interfaces

B. It permits variety using common platforms or components

C. It guarantees zero inventory

D. It removes the need for testing

Correct Answer: B. It permits variety using common platforms or components

Question 7

What does postponement mean in mass customization?

A. Producing every variant completely before demand occurs

B. Delaying final differentiation until better demand information is available

C. Eliminating customer choice

D. Replacing standard components with unique components

Correct Answer: B. Delaying final differentiation until better demand information is available

Question 8

In the life-cycle cost equation, why are future costs discounted?

A. To convert future costs into comparable present-value terms

B. To make all future costs equal to zero

C. To remove maintenance costs from the analysis

D. To guarantee that salvage value is negative

Correct Answer: A. To convert future costs into comparable present-value terms

Question 9

Which statement best describes concurrent engineering?

A. Each function works independently and sequentially

B. Only the design department makes decisions

C. Relevant functions consider product and process issues early and together

D. Production begins before design requirements are defined

Correct Answer: C. Relevant functions consider product and process issues early and together

Question 10

Why can an apparently cheaper material fail a value-analysis review?

A. Because purchase price is never relevant

B. Because it may increase life-cycle cost, risk, defects or environmental impact

C. Because all material substitutions are prohibited

D. Because value analysis considers only aesthetics

Correct Answer: B. Because it may increase life-cycle cost, risk, defects or environmental impact