2. Product, Service and Operations System Design

Introduction and Context

Operations management begins before production or service delivery. It begins with decisions about what an organisation will offer, whom it will serve, how the offering will be created, and how resources will flow through the operating system. Product, service and operations system design therefore connects market needs with operational capability. A poorly designed product may be expensive to manufacture, difficult to transport, unreliable in use, or impossible to customise profitably. Similarly, a poorly designed service may create long queues, inconsistent experiences, excessive labour requirements, or avoidable logistics costs.

For logistics professionals, design decisions are especially significant because they determine packaging, inventory, handling, storage, transport, postponement, reverse logistics and service responsiveness. Product architecture influences the number of stock-keeping units (SKUs), warehouse space and order-picking complexity. Service design influences customer contact, information flows, capacity requirements and recovery procedures. The central managerial challenge is to create value for customers while designing an operating system that is feasible, efficient, resilient and responsible.

This chapter examines the principles and tools used to translate customer requirements into products, services and processes. It also considers the relationship between quality, cost, flexibility, sustainability and life-cycle performance.

Learning Objectives

After studying this chapter, students should be able to:

1. Distinguish among product design, service design and operations system design.

2. Explain voice of customer (VOC), quality function deployment (QFD) and value analysis.

3. Evaluate standardisation, modularity and mass customisation decisions.

4. Apply design for manufacturability and service blueprinting principles.

5. Analyse the implications of design choices for logistics and supply networks.

6. Use life-cycle thinking to assess economic, environmental and ethical consequences.

7. Identify implementation risks and recommend appropriate design practices.

From Customer Need to Operating System

A product is a tangible offering whose attributes can be specified, produced, stored and transferred. A service is primarily an experience, performance or outcome produced through interaction among the provider, customer, information and physical resources. Most contemporary offerings combine both. A parcel-delivery service, for example, includes transportation, tracking, customer communication and physical handling of a package. A medical device includes hardware, software, installation, maintenance and technical support.

Design has two linked dimensions. Offering design determines the features, performance, appearance, functionality and customer experience. Process and system design determines how the offering will be created and delivered. These decisions should not be made independently. A highly customised product may require flexible equipment, skilled labour and delayed configuration. A promise of same-day delivery may require distributed inventory, advanced planning systems and reliable last-mile capacity.

The design task involves trade-offs. Higher variety can improve market appeal but increase inventory and scheduling complexity. Greater standardisation can lower cost but reduce perceived uniqueness. Premium materials may improve durability but raise purchase price, handling requirements and environmental impact. The relevant question is not whether one attribute is universally desirable, but whether the complete system delivers value at an acceptable total cost and risk.

A useful design logic is:

Customer requirements → technical characteristics → process capabilities → resource and network configuration → performance outcomes.

This logic prevents organisations from treating design as merely an engineering or marketing exercise. It makes explicit the operational consequences of promises made to customers.

Understanding Customer Value: Voice of Customer

The voice of customer is the systematic collection and interpretation of customer expectations, problems, preferences and measures of satisfaction. VOC data may be obtained from interviews, observation, surveys, complaints, reviews, sales personnel, warranty records, usage data and social media. Effective VOC work distinguishes what customers say they want from the underlying outcome they seek. A customer who asks for a lighter package may actually be seeking easier handling, lower delivery charges or reduced environmental impact.

VOC information is commonly organised into:

• Explicit needs, which customers directly state.
• Implicit needs, which customers assume will be present, such as safety or basic reliability.
• Latent needs, which customers may value once they experience them, such as proactive delivery notifications.
• Dissatisfiers, whose absence causes strong dissatisfaction.
• Satisfiers, which improve satisfaction in proportion to performance.
• Exciters, unexpected features that create positive differentiation.

The quality of VOC depends on representativeness and interpretation. A small number of vocal customers may not represent the broader market. Complaints reveal failures but may understate the needs of silent customers. Business customers may value total cost and integration more than visible product features. Consequently, qualitative research should often be combined with operational data and market segmentation.

A customer requirement should eventually be expressed in measurable terms. “Fast delivery” may become a 95th-percentile delivery time below a stated threshold. “Easy returns” may become a return-authorisation process requiring no more than specified steps. Measurability allows design teams to compare alternatives and monitor performance.

Quality Function Deployment and the House of Quality

Quality Function Deployment translates customer requirements into technical and operational specifications. Its best-known tool is the House of Quality, a matrix that relates customer requirements, their importance, technical responses and relationships among technical responses.

A typical QFD sequence is:

1. Capture and group customer requirements.

2. Assign relative importance to each requirement.

3. Identify competitor performance or benchmark expectations.

4. Translate requirements into measurable technical characteristics.

5. Assess the strength of relationships between customer needs and technical characteristics.

6. Identify positive and negative correlations among technical characteristics.

7. Establish target values and improvement priorities.

8. Cascade the requirements into component, process and control planning.

For example, in designing a temperature-sensitive pharmaceutical delivery service, customers may require product integrity, visibility and dependable arrival time. Technical responses may include validated packaging, sensor accuracy, scanning frequency, route-control rules and contingency capacity. The “roof” of the House of Quality may reveal conflicts: thicker insulation may protect the product but increase package volume, transport cost and disposal burden.

QFD is not a mathematical substitute for managerial judgement. Its numerical ratings can create false precision if based on weak evidence. Its value lies in cross-functional discussion, traceability and prioritisation. Marketing, engineering, procurement, operations, logistics, finance and customer service should participate because each sees different consequences of a design choice.

Value Analysis and Target Costing

Value analysis examines whether a product or service function is being delivered at an appropriate total cost. Value can be represented conceptually as:

Value = Function or benefit / Cost.

The objective is not indiscriminate cost reduction. It is to eliminate unnecessary cost while preserving or improving functions that matter to customers and regulators. A function analysis asks what the offering must do, how it currently does it, and whether an alternative can provide the same function more economically.

Value engineering is generally applied during design, when changes are relatively inexpensive. Value analysis may also be applied to an existing product or process. A team might discover that a premium shipping carton includes decorative printing that customers do not value, while its internal protection is inadequate. Removing the decoration and improving internal cushioning may increase value rather than simply reduce cost.

Target costing begins with an acceptable market price and required margin, then derives the allowable cost:

Target cost = Expected market price − Required profit.

Design teams then seek to meet this cost through material selection, architecture, supplier collaboration, process simplification and logistics analysis. Total cost should include procurement, manufacturing, inventory, transport, handling, maintenance, returns, disposal and failure costs. A low purchase price can be misleading if it produces frequent damage, high energy consumption or difficult reverse logistics.

Standardisation, Modularity and Mass Customisation

Standardisation uses common specifications, components, procedures or interfaces. It reduces variety, simplifies training, supports purchasing economies and improves forecasting. In logistics, standard carton sizes, pallet dimensions, labels and data formats improve storage density, equipment utilisation and information exchange. However, excessive standardisation may restrict innovation or fail to address meaningful market differences.

Modularity divides an offering into relatively independent modules connected through defined interfaces. Modules may be designed, produced, stocked or upgraded separately. A modular product can offer variety without making every final configuration unique. In a distribution operation, a standard base product might be combined with region-specific packaging, documentation or accessories near the customer.

Mass customisation seeks to provide individualised offerings with near-standardised efficiency. It depends on postponement, flexible processes, digital configuration and modular architecture. The location of the customer order in the process is important. If differentiation occurs before demand is known, the organisation must forecast many finished variants. If differentiation is postponed, it can hold common components and configure them after receiving the order.

These approaches create a strategic choice rather than a universal hierarchy. Standardisation is valuable where demand is stable and customers accept uniformity. Modularity is useful where variety is significant but interfaces can be controlled. Mass customisation is attractive where customers value choice and information systems can coordinate late configuration. The costs of complexity must be measured in procurement, inventory, scheduling, quality control, transportation and customer support.

Design for Manufacturability and Supply-Chain Compatibility

Design for manufacturability (DFM) aims to make products easier, safer and more economical to produce. Related principles include design for assembly, design for logistics, design for serviceability, design for reliability and design for disassembly. The broader idea is design for the complete operating system.

DFM commonly encourages fewer parts, common fasteners, simple assembly sequences, accessible components, tolerance control, mistake-proofing and appropriate material choices. Early supplier involvement can identify tooling, lead-time, quality and transport constraints before the design is frozen. Digital simulation and prototypes allow teams to test assembly, packaging, ergonomics and damage risks.

For logistics, design should consider cube, weight, stackability, handling points, package strength, labelling, pallet fit and returnability. A product that fits poorly into standard transport equipment may incur disproportionate cost throughout its life. Packaging should protect the product without creating unnecessary material, volume or disposal burden. Design teams should also consider how damaged, obsolete or returned products will be inspected, repaired, recycled or disposed of.

Design reviews should therefore include questions such as:

• Can suppliers produce the required tolerances consistently?
• Can the product be packed and handled safely?
• Does its physical form support efficient storage and transport?
• Can defects be detected early and traced to their source?
• Can the product be repaired, upgraded or disassembled?
• Are critical materials subject to supply, regulatory or ethical risk?

Service Design and Service Blueprinting

Services differ from manufactured goods because production and consumption may occur together, customer participation is often substantial, and capacity that is not used cannot generally be stored. Service design must therefore address both the customer experience and the operating process that makes it possible.

A service blueprint maps the service from the customer’s perspective while showing the organisational activities behind it. Its common elements are:

1. Customer actions, such as placing an order or presenting a return.

2. Frontstage or visible employee actions, such as confirmation and advice.

3. Backstage actions, such as allocation, picking or exception handling.

4. Support processes, including IT, suppliers and payment systems.

5. Physical or digital evidence, such as packaging, messages, receipts and tracking screens.

6. Lines of interaction, visibility and internal interaction, which show where handoffs and failures may occur.

Consider a home-delivery return. The customer requests a return online, receives instructions, hands over the item, obtains confirmation and receives a refund. Behind these actions are eligibility rules, transport scheduling, scanning, inspection, inventory disposition and financial reconciliation. A blueprint can reveal failure points such as unclear instructions, duplicate data entry, missing scans or delays between inspection and refund.

Service design should define standards for reliability, responsiveness, assurance, empathy and recovery. It should also identify fail points, poka-yoke controls and alternative paths for exceptional cases. A service promise is credible only when capacity, employee authority and information systems support it.

Life-Cycle Thinking and Sustainability

Life-cycle thinking evaluates impacts from resource extraction through production, distribution, use, recovery and final disposal. It prevents a narrow focus on the factory gate. A product may use less material but require more energy during use; a reusable package may reduce waste but increase reverse transport; a repairable product may require more initial design effort but extend useful life.

Life-cycle assessment can be conducted in detail according to defined boundaries and impact categories, or used qualitatively during early design. Relevant considerations include carbon emissions, energy, water, hazardous substances, material scarcity, labour conditions, packaging waste and end-of-life options. Life-cycle costing similarly includes acquisition, operation, maintenance, downtime, returns and disposal.

Circular design seeks to retain product, component and material value through durability, repair, refurbishment, remanufacturing, reuse and recycling. Logistics has a central role in these loops, but reverse flows are often more uncertain than forward flows. Collection points, grading standards, information visibility and economically viable disposition routes must be designed rather than assumed.

Ethical design also requires attention to accessibility, worker safety, privacy, truthful claims and responsible sourcing. Sustainability claims should be evidence-based and transparent about boundaries. A design that reduces transport emissions by shifting burdens to unsafe suppliers is not responsible system design.

Digital Tools, Analytics and Emerging Practice

Digital technologies increasingly support design decisions. Product-lifecycle-management systems maintain versions, specifications and approvals. Computer-aided design and simulation test fit, stress, packaging and assembly. Configuration engines support mass customisation. Digital twins can represent products, facilities or logistics processes and allow alternative scenarios to be tested.

Analytics can combine customer feedback, warranty data, returns, sensor information and operational performance. Text analytics may identify recurring complaints; predictive models may reveal failure patterns; optimisation tools may compare network, inventory or postponement options. Artificial intelligence can assist concept generation, demand interpretation and design-for-cost analysis, but its outputs require human validation. Data may be biased, confidential or incomplete, and automated recommendations can obscure accountability.

The growing use of connected products also creates cybersecurity and privacy obligations. Designers must consider access control, software updates, data minimisation and failure modes when connectivity is unavailable. Digital convenience should not create unacceptable dependence on insecure systems.

An Integrated Design Process

An effective design process is iterative rather than strictly linear. A practical sequence is to identify the customer and strategic purpose, gather VOC evidence, define measurable requirements, generate alternatives, evaluate technical and economic feasibility, prototype and test, design the operating process, pilot the system, and establish control and learning mechanisms.

Cross-functional governance is essential. Design decisions should have named owners, documented assumptions, approval criteria and change-control procedures. Key measures may include customer-perceived value, first-pass yield, total landed cost, order fulfilment time, defect and return rates, inventory complexity, transport cube utilisation, carbon intensity and recovery rate. Measures should be balanced: improving delivery speed by excessive inventory may simply transfer cost and risk.

Illustrative Case: Designing a Customised Spare-Parts Fulfilment Service

Background

The following fictional case concerns AeroMaintain, a regional aircraft-maintenance supplier serving repair stations and airline engineering teams. Customers required rapid access to thousands of parts, but demand was intermittent and product configurations varied by aircraft type.

Situation and Problem

AeroMaintain stocked many finished kits because customers requested “complete maintenance packs.” The approach produced high inventory, frequent obsolescence and difficult picking. Customers also complained that urgent orders were not visible in transit and that returns were slow to process. Management initially proposed expanding warehouse capacity.

Analysis

VOC interviews showed that customers valued three outcomes: correct part compatibility, dependable delivery commitment and rapid documentation. They did not necessarily require every kit to be physically preassembled. QFD translated these needs into compatibility accuracy, order-confirmation time, delivery reliability, documentation completeness and return-cycle time. Value analysis found that several printed inserts and duplicated protective containers added cost without improving the critical functions.

The design team considered three options: continue stocking complete kits, stock individual parts only, or use a modular system. The third option offered a better balance. Common components would be held in regional inventory, while customer-specific documentation and final kit assembly would occur after order receipt. This postponed differentiation and reduced the number of finished configurations.

Approach and Solution

AeroMaintain created standard modules with controlled interfaces and introduced barcode verification at picking and final assembly. A service blueprint mapped order entry, compatibility validation, warehouse activities, carrier handoff, tracking communication and returns inspection. A digital dashboard linked order status to customer notifications. Packaging was redesigned around standard reusable containers, with a defined reverse-logistics route for their recovery.

The pilot was limited to one product family. Performance was reviewed using order accuracy, fulfilment time, inventory value, obsolete stock, container return rate and customer-reported reliability. Exception procedures were established for unavailable parts and urgent aircraft-on-ground orders.

Outcome

The pilot demonstrated that the organisation could provide configuration variety without stocking every finished kit. Warehouse capacity expansion was deferred, and the process became easier to audit. The case does not claim universal numerical results; its significance lies in the design logic: VOC identified the real service outcomes, QFD made them measurable, modularity enabled variety, postponement reduced risk, and blueprinting exposed handoff failures.

Learning Points

First, customer requests should be interpreted as desired outcomes rather than accepted literally. Second, product architecture and service process design must be considered together. Third, postponement is effective only when modules, information and final-configuration controls are reliable. Finally, a pilot with explicit measures is safer than a large irreversible investment.

Challenges, Risks and Common Mistakes

Design projects commonly fail when customer research is superficial, technical specifications are ambiguous, or functions work in isolation. Other risks include excessive SKU proliferation, uncontrolled engineering changes, inadequate supplier participation, underestimating reverse logistics and treating prototype success as proof of scalable operations.

Common mistakes include reducing cost by removing a feature that prevents failures; designing for average demand while ignoring peaks; assuming standardisation is always superior; measuring service quality only through internal efficiency; and adopting AI or digital tools without data governance. Another mistake is delaying sustainability assessment until the end, when major material and architecture decisions are difficult to change.

Managers should also distinguish variation from complexity. A range of customer choices may be commercially valuable, but every additional option can create forecasting, purchasing, quality and support consequences. Complexity should be made visible through total-cost and process-capacity analysis.

Best-Practice Principles

Sound product, service and operations system design generally follows these principles:

• Begin with evidence about customer outcomes and convert it into measurable requirements.
• Involve operations, logistics, suppliers, service personnel and customers early.
• Evaluate total life-cycle cost, risk and impact rather than purchase price alone.
• Use standard platforms and modular interfaces where they preserve meaningful choice.
• Postpone differentiation when demand variety is high and final configuration is feasible.
• Design packaging, information and reverse flows alongside the forward process.
• Prototype critical interactions and test exceptional as well as normal conditions.
• Use QFD, value analysis and blueprinting as collaborative decision tools, not mechanical scoring exercises.
• Establish traceability, change control, ethical review and performance feedback.

Chapter Summary

Product, service and operations system design translates customer needs into feasible offerings and operating processes. VOC provides evidence about desired outcomes; QFD connects those outcomes with technical characteristics and priorities; value analysis and target costing examine function relative to total cost. Standardisation reduces unnecessary variety, while modularity and postponement can support mass customisation without excessive inventory and process complexity. Design for manufacturability and logistics improves production, handling, transport, serviceability and recovery. Service blueprinting makes customer actions, visible work, backstage processes and support systems visible. Life-cycle thinking extends design responsibility across use, returns and end of life. Digital tools, analytics and AI can improve design decisions, but require validation, governance and cybersecurity. Effective design is cross-functional, iterative, measurable and attentive to economic, operational, environmental and ethical consequences.

Key Terms

Voice of Customer: Systematic collection and interpretation of customer needs, expectations and problems.

Quality Function Deployment: A method for translating customer requirements into technical and operational specifications.

House of Quality: A QFD matrix showing relationships among customer needs and technical characteristics.

Value Analysis: Examination of an existing offering to improve function relative to total cost.

Value Engineering: Function-oriented cost and design improvement conducted primarily before production.

Target Costing: Derivation of allowable cost from expected market price and required profit.

Standardisation: Use of common specifications, components, procedures or interfaces.

Modularity: Division of an offering into separable units connected through defined interfaces.

Mass Customisation: Delivery of individualised offerings with processes approaching standardised efficiency.

Postponement: Delaying product differentiation until demand or customer information is known.

Design for Manufacturability: Designing products to simplify and improve economical production.

Design for Logistics: Designing products and packaging for efficient storage, handling and transport.

Service Blueprint: A visual representation of customer actions and the activities supporting service delivery.

Frontstage Activities: Service actions visible to the customer.

Backstage Activities: Internal activities that support a service but are not normally visible.

Life-Cycle Thinking: Assessment of impacts and costs across an offering’s complete life.

Reverse Logistics: Planning and control of flows from the customer back to recovery, reuse or disposal.

Total Cost of Ownership: All significant costs incurred during acquisition, use, maintenance and disposal.

Poka-Yoke: Mistake-proofing methods that prevent or detect errors.

Digital Twin: A digital representation used to monitor, simulate or analyse a physical product or process.

Review Questions

Short Answer Questions

1. Why should product design and operations system design be considered together?

2. Distinguish between explicit, implicit and latent customer needs.

3. What is the purpose of the House of Quality?

4. Explain the difference between standardisation and modularity.

5. Identify four elements commonly included in a service blueprint.

Long Answer Questions

1. Explain how VOC and QFD can be used to design a logistics service.

2. Discuss the operational benefits and risks of mass customisation.

3. Explain value analysis and target costing, using a suitable example.

4. Describe how design for manufacturability and design for logistics influence supply-chain performance.

5. Discuss the role of life-cycle thinking in responsible product and service design.

Analytical / Application Questions

1. A retailer offers 40 product variants, but most sales come from five common configurations. Analyse whether modularity and postponement could reduce complexity without reducing customer value.

2. A parcel firm promises same-day delivery but experiences missed deliveries and high overtime. Use service blueprinting to identify likely failure points and recommend design changes.

3. A reusable transport package reduces packaging waste but requires empty returns over long distances. Evaluate the decision using total-cost and life-cycle perspectives.

22. Multiple Choice Questions with Answers

Question 1

A logistics company translates the customer requirement “reliable delivery” into a 95th-percentile delivery-time target. Which design activity has occurred?

A. Conversion of a customer need into a measurable technical requirement

B. Elimination of customer involvement from service design

C. Replacement of QFD with financial accounting

D. Standardisation of all customer orders

Correct Answer: A. Conversion of a customer need into a measurable technical requirement

Question 2

What is the principal purpose of the House of Quality?

A. To calculate warehouse rent

B. To connect customer requirements with technical characteristics

C. To schedule employee holidays

D. To determine tax liabilities

Correct Answer: B. To connect customer requirements with technical characteristics

Question 3

A firm stocks common components and performs final configuration only after receiving an order. This is primarily an example of:

A. Vertical integration

B. Postponement

C. Overproduction

D. Demand smoothing

Correct Answer: B. Postponement

Question 4

Which decision best illustrates value analysis?

A. Adding every feature requested by a single customer

B. Removing decorative packaging while improving product protection

C. Increasing finished-goods inventory without examining functions

D. Selecting the supplier with the lowest quoted price only

Correct Answer: B. Removing decorative packaging while improving product protection

Question 5

In a service blueprint, warehouse picking performed out of the customer’s view is classified as:

A. Customer action

B. Physical evidence

C. Backstage activity

D. Market segmentation

Correct Answer: C. Backstage activity

Question 6

Which outcome is most directly associated with modular product architecture?

A. More configuration variety using controlled interfaces

B. Guaranteed elimination of all inventory

C. No need for quality control

D. Complete removal of supplier relationships

Correct Answer: A. More configuration variety using controlled interfaces

Question 7

Why should logistics considerations be included during product design?

A. Product design has no effect on transport or storage

B. Physical form can influence handling, cube utilisation and packaging cost

C. Logistics costs are determined only after product disposal

D. Logistics decisions are unrelated to customer value

Correct Answer: B. Physical form can influence handling, cube utilisation and packaging cost

Question 8

A target cost is normally derived by:

A. Adding required profit to the market price

B. Subtracting required profit from expected market price

C. Dividing market price by warehouse capacity

D. Ignoring expected customer willingness to pay

Correct Answer: B. Subtracting required profit from expected market price

Question 9

Which situation best reflects life-cycle thinking?

A. Choosing materials solely on purchase price

B. Assessing production, use, returns and end-of-life consequences

C. Measuring only factory labour productivity

D. Evaluating a package only at the point of sale

Correct Answer: B. Assessing production, use, returns and end-of-life consequences

Question 10

What is a major governance concern when AI is used in design analytics?

A. AI makes all human review unnecessary

B. Data bias, confidentiality and accountability may affect recommendations

C. AI automatically guarantees regulatory compliance

D. AI prevents the need for change control

Correct Answer: B. Data bias, confidentiality and accountability may affect recommendations