Operations Management & Design

Chapter 3
Product and Service Design

Post Graduate Program in Operations Management
Operations Management & Design • Post Graduate

Product and Service Design

Introduction and context

Product and service design determines what an organisation offers, how it creates value, and how reliably and economically that value can be delivered. It is therefore more than industrial styling or service scripting. Design decisions establish requirements for operations, supply networks, technology, capacity, quality, labour, maintenance, environmental performance and eventual disposal. A poorly designed offering may be expensive to produce, difficult to use, unsafe, environmentally damaging or impossible to deliver consistently. Conversely, a well-designed offering aligns customer value with operational capability and strategic intent.

Design is especially important because most lifecycle cost is committed during early concept development, when changes are relatively inexpensive. Later changes may require tooling modifications, supplier qualification, software revision, employee retraining or regulatory reapproval. Operations managers must therefore participate in design rather than merely receive a finished design for execution.

This chapter examines design thinking, customer-needs analysis, quality function deployment (QFD), value engineering, standardisation, modularity, mass customisation, service blueprinting, design for manufacture and assembly (DFMA), sustainability and lifecycle principles.

Learning objectives

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

Explain how product and service design affects operations strategy and competitive performance.
Apply design thinking and structured customer-needs analysis.
Construct and interpret a basic QFD house of quality.
Distinguish value engineering from cost cutting.
Evaluate standardisation, modularity and mass customisation decisions.
Use service blueprints to identify failure points and improvement opportunities.
Apply DFMA, sustainability and lifecycle thinking to design decisions.
Critically assess trade-offs among customer value, cost, flexibility, quality, risk and environmental impact.

1. Design as an operations decision

A design specifies the characteristics of an offering and the process requirements needed to create and deliver it. For a product, these may include dimensions, materials, tolerances, functions, interfaces, packaging and maintainability. For a service, they include the customer journey, employee actions, information flows, facilities, technology, service standards and recovery procedures.

A useful design objective is not simply minimum unit cost. It is the creation of superior lifecycle value. Relevant performance dimensions include:

Quality: conformance, reliability, durability, safety and perceived performance.
Speed and dependability: time required and consistency of delivery.
Flexibility: ability to accommodate variety, volume changes and special requirements.
Cost: development, production, delivery, use, maintenance and disposal cost.
Sustainability: resource consumption, emissions, circularity and social effects.
Experience: usability, accessibility, convenience, trust and emotional response.

These dimensions conflict. A premium material may improve durability but increase cost and embodied carbon. Greater variety may increase customer choice but create forecasting, scheduling and inventory complexity. Design is thus a cross-functional decision involving marketing, operations, engineering, procurement, finance, service personnel, information technology, customers and regulators.

2. Design thinking and customer-needs analysis

Design thinking is a human-centred approach to ambiguous problems. Its commonly used cycle consists of empathise, define, ideate, prototype and test. The sequence is not strictly linear: evidence from testing may redefine the problem or generate new ideas.

Empathise involves observing users, interviewing them, analysing complaints, studying workarounds and understanding context. Stated preferences are useful but may not reveal latent needs. A customer may request a faster checkout, while observation reveals that uncertainty about queue progress is the deeper problem.

Define converts observations into a focused problem statement. A strong statement identifies the user, context, unmet need and desired outcome without prematurely prescribing a solution. “How might we help patients feel informed while waiting?” is more useful than “How might we install another display?”

Ideate generates alternatives before selecting one. Cross-functional teams, analogy, morphological analysis and controlled brainstorming can expand the solution space. Ideas should initially be judged lightly so that unusual but valuable possibilities are not rejected too early.

Prototype makes an idea observable. Prototypes may be sketches, mock-ups, process rehearsals, role plays, clickable interfaces or pilot services. Their purpose is learning, not merely demonstration.

Test collects evidence from representative users and operating conditions. Testing should examine desirability, feasibility, viability, safety, accessibility and environmental consequences. A prototype that customers like but employees cannot deliver reliably is not a successful design.

Translating needs into requirements

Customer language is often vague. “Easy to use,” “fast” and “safe” must be translated into measurable requirements such as maximum setup time, response time, error rate or failure probability. Requirements should be:

traceable to a stakeholder need;
measurable or verifiable;
prioritised;
free from unnecessary solution assumptions;
compatible with legal, safety and operational constraints.

A useful distinction is among basic needs, whose absence causes dissatisfaction; performance needs, for which greater achievement increases satisfaction; and delighters, unexpected features that can create enthusiasm. This classification changes over time: a former delighter may become a basic expectation as competitors imitate it.

Customer research should combine qualitative and quantitative methods. Interviews and observation explain why a problem occurs; surveys and transaction data indicate prevalence and segment differences. Sampling bias, social desirability bias and poorly worded questions can mislead design teams. The voice of the customer must therefore be triangulated with operational data and direct observation.

3. Quality function deployment

QFD is a structured method for translating customer requirements into technical characteristics, process controls and, ultimately, production or service requirements. Its best-known tool is the house of quality.

A basic house contains:

customer requirements, or “whats”;
importance ratings for those requirements;
technical characteristics, or “hows”;
a relationship matrix connecting whats and hows;
competitive or perceptual benchmarking;
a roof showing correlations among technical characteristics;
target values and priorities for technical work.

The relationship matrix commonly uses qualitative weights such as 9 for strong, 3 for medium, 1 for weak and 0 for no relationship. These are conventions, not universal physical laws. The team must define them consistently and avoid false precision.

If customer requirement i has importance rating w_i and its relationship with technical characteristic j is r_ij, a basic technical priority is:

P_j = ∑_i=1ⁿ w_i r_ij

Here, P_j is the unnormalised priority of technical characteristic j, n is the number of customer requirements, w_i is the importance rating of requirement i, and r_ij is the relationship weight. The result has no physical unit because it is a prioritisation index. It is applicable when the ratings are comparable and the team accepts an additive approximation. It should not be interpreted as a probability, utility function or causal estimate.

Worked QFD example

Suppose a parcel service identifies three customer requirements:

Customer requirement	Importance w_i
Fast delivery	5
Easy tracking	4
Low damage	5

Technical characteristics are delivery-cycle time, tracking visibility and packaging robustness. Using relationship weights 9, 3, 1 and 0:

Requirement	Importance	Cycle time	Tracking visibility	Packaging robustness
Fast delivery	5	9	1	0
Easy tracking	4	1	9	0
Low damage	5	0	1	9
Priority		49	42	45

For cycle time, P₁ = 5×9 + 4×1 + 5×0 = 49. Packaging robustness has P₃ = 5×0 + 4×0 + 5×9 = 45. Cycle time receives the highest numerical priority, but the decision should also consider current performance, feasibility, cost and risk. QFD structures discussion; it does not replace managerial judgement.

QFD can be cascaded from product planning to component planning, process planning and production or service control. Its limitations include subjective ratings, dependence on the quality of customer research, difficulty representing interactions and the risk that teams optimise measurable characteristics while neglecting experience or equity.

4. Value engineering and target costing

Value engineering is a systematic effort to achieve required functions at the lowest total cost without reducing necessary performance, quality, safety or customer value. The central question is: “What function must this element perform, and what is the least resource-intensive way to perform it?”

Value is often represented conceptually as:

Value = \frac{Function\ delivered}{Cost\ incurred}

This is a comparative management concept, not a universal unit of measurement. “Function” may include performance, convenience, safety and emotional value; “cost” should include relevant lifecycle cost rather than only purchase price. The ratio is useful for comparing alternatives only when function and cost have been defined consistently.

Value engineering follows stages such as information gathering, functional analysis, creative generation, evaluation, development and implementation. Function analysis uses an active verb and measurable noun, for example “support load,” “protect contents” or “authenticate user.” Teams distinguish primary functions from secondary functions and identify cost drivers.

Value engineering differs from indiscriminate cost cutting. Removing a safety feature or weakening a component may lower initial cost while increasing failures, warranty claims and harm. Lifecycle costing should include acquisition, operation, maintenance, downtime, energy, compliance and end-of-life costs. A simple lifecycle cost model is:

LCC = C₀ + ∑_t=1^T \frac{C_t}{(1+d)^t} - \frac{S_T}{(1+d)^T}

Here, LCC is lifecycle cost in currency units, C₀ is initial cost, C_t is cost in period t, d is the discount rate per period, T is the evaluation horizon, and S_T is residual or salvage value at the end. The formula assumes costs occur at discrete period ends, a constant discount rate and a defined analysis horizon. If inflation is included, costs and the discount rate must be expressed consistently in nominal or real terms.

5. Standardisation, modularity and mass customisation

Standardisation reduces unnecessary variety by using common dimensions, components, interfaces, procedures or specifications. Benefits include economies of scale, simpler purchasing, lower inventory, easier training, improved interchangeability and more reliable quality. Excessive standardisation can suppress innovation, reduce fit with local needs or create dependence on a single design.

Modularity divides an offering into semi-independent modules connected through defined interfaces. Modules can be combined into variants while preserving common platforms. Examples include configurable software, vehicle platforms, furniture systems and modular hospital services. Effective modularity requires stable interfaces, disciplined version control and careful management of technical dependencies.

Mass customisation seeks to provide variety close to the cost and speed of standardised production. Common strategies include:

postponement of final differentiation until demand is known;
configurable products with a common platform;
late-stage packaging or labelling;
digital configuration and make-to-order production;
modular service bundles.

The operational risk is variety proliferation. Each additional option can increase setup time, forecasting error, inventory and error opportunities. A useful design principle is to maximise external variety while minimising internal complexity.

6. Service design and blueprinting

Services are processes experienced over time, often with simultaneous production and consumption, customer participation and variable outcomes. Service design must therefore address both the visible experience and the hidden operating system.

A service blueprint maps customer actions, frontstage employee actions, backstage actions, support processes and physical or digital evidence. It normally includes:

the customer journey;
the line of interaction between customer and provider;
the line of visibility separating visible and invisible work;
the line of internal interaction among employees and support systems;
fail points, controls and recovery actions.

For an online university enrolment service, customer actions may be selecting a course, entering information and paying. Frontstage actions include interface prompts and confirmation messages. Backstage actions include eligibility checks, payment authorisation and record creation. Support processes include identity management, academic databases and help-desk escalation.

Blueprinting reveals handoff failures, duplicated data entry, unclear ownership and moments where the customer must compensate for internal complexity. It also supports service standards such as response time, first-contact resolution and accessibility. However, a blueprint is a model, not the service itself. It must be validated through observation, process data and customer feedback.

Service recovery should be designed rather than improvised. A recovery design may specify detection, employee authority, communication, remedy, escalation and learning. Ethical design requires that automation does not make complaints inaccessible or shift unreasonable work onto customers.

7. Design for manufacture and assembly

DFMA integrates product design with production capability. Design for manufacture reduces difficulty and cost of making components; design for assembly reduces the number, complexity and orientation difficulty of assembly steps. Important principles include:

reduce unnecessary part count;
use standard, readily available components;
design clear orientation and mistake-proofing features;
provide easy access for tools and inspection;
minimise difficult fasteners and adjustments;
design tolerances according to actual process capability;
consider repair, disassembly and recycling;
involve suppliers and operators early.

Part-count reduction can reduce purchasing, handling and assembly opportunities for error, but integration may make repair or replacement more difficult. Tight tolerances may improve performance but increase scrap and process cost. Therefore DFMA is a system decision, not a search for the fewest parts at any cost.

Design reviews should use prototypes, tolerance analysis, capability evidence, failure mode and effects analysis (FMEA), supplier input and pilot builds. FMEA asks how a design or process can fail, what effects may result, what causes are plausible, how controls detect the failure and what action reduces risk. Risk priority calculations, when used, should not be treated as objective truth; high-severity hazards may require action even when occurrence estimates are low.

8. Sustainability and lifecycle design

Sustainable design considers impacts from raw-material extraction through production, distribution, use and end-of-life. A lifecycle perspective avoids burden shifting—for example, reducing manufacturing energy while increasing customer energy consumption or hazardous disposal.

Key approaches include:

design for durability and repair: extend useful life;
design for disassembly: enable maintenance, reuse and material recovery;
material substitution: reduce toxicity, scarcity or embodied impact;
resource efficiency: reduce material, water and energy intensity;
circular strategies: reuse, remanufacture, refurbish, recycle or provide products as services;
inclusive design: accommodate diverse abilities, incomes, languages and contexts.

Lifecycle assessment (LCA) is a structured method for defining a goal and scope, compiling an inventory, assessing impacts and interpreting results. Results depend on system boundaries, functional unit, allocation rules, data quality and assumptions. LCA should support decisions, not be presented as an unquestionable single score.

Designers should distinguish absolute and relative improvements. A more efficient product may still increase total environmental impact if lower operating cost causes much greater usage—a rebound effect. Social sustainability includes labour conditions, privacy, safety, accessibility and effects on communities. Green claims must be substantiated and communicated precisely to avoid greenwashing.

9. Managing the design process

A robust design process uses stage gates or equivalent governance. Typical stages are opportunity identification, concept generation, feasibility, detailed design, pilot, launch and post-launch learning. At each gate, decision makers review customer evidence, technical performance, operational readiness, economics, regulatory compliance, sustainability and unresolved risks.

Useful metrics include first-pass yield, defect opportunities, development lead time, design-change frequency, time to volume, customer effort, service failure rate, warranty cost, carbon footprint and lifecycle cost. Metrics should be balanced: a team rewarded only for launch speed may conceal defects; a team rewarded only for feature count may create complexity.

Digital tools such as computer-aided design, simulation, digital twins, configuration systems and generative AI can accelerate exploration. AI-generated concepts require human review for manufacturability, bias, intellectual-property risk, safety, explainability and data provenance. Automation should not remove accountability for design decisions.

Illustrative case: modular cold-chain delivery box

Background. A regional healthcare distributor used single-use insulated boxes for temperature-sensitive medicines. Customers valued reliability, but the boxes generated waste, had inconsistent internal temperature, and required several sizes.

Problem. The organisation needed to reduce damage and environmental impact without increasing delivery cost or compromising regulatory temperature limits.

Analysis. Interviews and route observation identified three needs: dependable temperature control, easy unpacking and evidence that the shipment remained within limits. QFD gave high priority to insulation performance, sensor visibility and secure but rapid opening. Value analysis showed that several internal inserts performed overlapping functions. A lifecycle review found that disposal impacts were significant, while reusable designs could create reverse-logistics emissions.

Approach. The team developed a reusable outer shell with standard interfaces and interchangeable insulation and payload modules. A temperature sensor was placed where it represented the product’s thermal exposure rather than merely ambient air. Postponing the selection of internal modules reduced the number of complete box designs. DFMA reduced fasteners and introduced keyed assembly to prevent incorrect orientation. A pilot blueprint mapped ordering, packing, dispatch, delivery, return and cleaning. Cleaning validation and tamper evidence were treated as safety requirements, not optional features.

Outcome. The pilot reduced packaging variants and packing errors. Return feasibility varied by route, so reusable boxes were used where backhaul existed and recyclable alternatives were retained for remote routes. The result was not a universally reusable solution; it was a segmented design based on lifecycle evidence and operational conditions.

Learning points. Customer value, technical performance and sustainability must be evaluated together. Modularity can reduce internal complexity while preserving customer choice. A lifecycle perspective prevents attractive but inefficient reuse schemes. Pilot evidence is essential because design assumptions about reverse logistics and user behaviour are often wrong.

Challenges, ethics and limitations

Design teams face uncertain demand, conflicting stakeholders, incomplete data, path dependence and pressure to launch quickly. Customer preferences may conflict with employee wellbeing or public interest. Personalisation may improve convenience while increasing surveillance and discriminatory algorithmic outcomes. Connected products create cybersecurity, privacy and update obligations. Safety-critical designs require formal compliance, traceability and independent review.

Design governance should identify accountable decision owners, document assumptions, protect confidential data, include affected communities and provide mechanisms for challenge and redress. Accessibility should be designed in from the beginning rather than added after testing. Sustainable design should consider the distribution of benefits and burdens, not only aggregate environmental indicators.

Best-practice checklist

Start with verified user and stakeholder needs.
Translate needs into measurable, traceable requirements.
Involve operations, suppliers, service employees and users early.
Use prototypes and pilots to expose assumptions.
Apply QFD to connect customer value with technical priorities.
Use value engineering to protect function while reducing lifecycle cost.
Control variety through platforms, standardisation and modularity.
Blueprint services across visible and invisible work.
Design for manufacture, assembly, repair, safety and end-of-life.
Evaluate sustainability using explicit boundaries, evidence and trade-offs.
Govern AI, data, privacy, accessibility and regulatory risk.
Continue learning after launch through performance and customer data.

Chapter Summary

Product and service design is a strategic operations activity because it determines the requirements, complexity, risk and lifecycle consequences of delivery. Design thinking provides a human-centred process of inquiry, definition, experimentation and learning. Customer-needs analysis converts observations into prioritised and measurable requirements. QFD links those requirements to technical characteristics, while recognising that its numerical priorities are structured judgements rather than objective truths.

Value engineering seeks required function at minimum lifecycle cost, not indiscriminate cost reduction. Standardisation and modularity reduce internal complexity and can enable mass customisation through platforms and postponement. Service blueprinting makes customer actions, frontstage and backstage work, support systems and failure points visible. DFMA connects design with process capability, assembly simplicity, quality and repairability. Sustainability requires lifecycle and circular thinking, attention to rebound effects, social impacts and credible evidence. Effective design governance combines cross-functional participation, prototyping, risk assessment, regulatory compliance, ethical oversight and post-launch learning.

Key Terms

Design thinking: Human-centred approach involving empathising, defining, ideating, prototyping and testing.

Voice of the customer: Structured evidence about customer needs, expectations and experiences.

Requirement: A stated and verifiable condition that a design must satisfy.

Quality function deployment: Method for translating customer requirements into technical and process priorities.

House of quality: Matrix-based QFD tool linking customer requirements with technical characteristics.

Technical characteristic: Measurable design or process variable used to address a customer requirement.

Value engineering: Systematic analysis of functions to achieve required value at lower lifecycle cost.

Lifecycle cost: Present-value cost of acquisition, operation, maintenance, failure and end-of-life.

Standardisation: Reduction of unnecessary variety through common specifications, parts or procedures.

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

Mass customisation: Delivery of substantial variety with near-standardised efficiency.

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

Service blueprint: Map of customer actions, visible service work, hidden work and support processes.

DFMA: Design for manufacture and assembly, integrating design with production and assembly capability.

FMEA: Structured analysis of potential failure modes, effects, causes and controls.

Lifecycle assessment: Evaluation of environmental impacts across a defined product or service system.

Circular economy: Approach emphasising reuse, repair, remanufacture, recycling and reduced resource extraction.

Design governance: Accountability, review and control mechanisms for design decisions and risks.

Review Questions

Short Answer Questions

Why should operations managers participate in product and service design?
What are the five commonly cited activities in design thinking?
What is the purpose of the relationship matrix in QFD?
Distinguish standardisation from modularity.
What information does a service blueprint make visible?

Long Answer Questions

Explain how customer-needs analysis can be converted into measurable design requirements. Discuss the limitations of relying only on surveys.
Describe the house of quality and explain how QFD supports cross-functional decision-making.
Compare value engineering, standardisation and modularity as methods of controlling lifecycle cost and complexity.
Explain how DFMA affects quality, flexibility, maintainability and supplier relationships.
Discuss why sustainability requires lifecycle thinking rather than attention only to manufacturing impacts.

Analytical / Application Questions

A bank receives complaints about slow branch service. Develop a brief design-thinking plan and identify the likely elements of a service blueprint.
Construct a small QFD matrix for a meal-delivery service using three customer requirements and three technical characteristics. Explain how you would prioritise improvement.
A firm is considering a reusable package for an irregular rural delivery route. Analyse the decision using modularity, lifecycle cost, reverse logistics, customer value and environmental risk.

Multiple Choice Questions with Answers

Question 1

Which activity in design thinking primarily converts observations into a focused problem statement?

A. Empathise

B. Define

C. Prototype

D. Test

Correct Answer: B. Define

Question 2

In a basic QFD calculation, if a customer requirement has importance 4 and a strong relationship weight of 9, what contribution does it make to the technical priority?

A. 13

B. 36

C. 45

D. 49

Correct Answer: B. 36

Question 3

What is the principal purpose of the roof in a house of quality?

A. To list customer requirements

B. To show correlations among technical characteristics

C. To calculate lifecycle cost

D. To display employee responsibilities

Correct Answer: B. To show correlations among technical characteristics

Question 4

Which statement best describes value engineering?

A. Reducing purchase price regardless of performance

B. Increasing product variety regardless of complexity

C. Achieving required functions at the lowest appropriate lifecycle cost

D. Replacing all human work with automation

Correct Answer: C. Achieving required functions at the lowest appropriate lifecycle cost

Question 5

Which design approach delays final product differentiation until demand is known?

A. Postponement

B. Overdesign

C. Inspection

D. Vertical integration

Correct Answer: A. Postponement

Question 6

Which element separates visible employee actions from backstage service activities in a service blueprint?

A. Line of interaction

B. Line of visibility

C. Demand boundary

D. Quality gate

Correct Answer: B. Line of visibility

Question 7

Which is a typical DFMA objective?

A. Increase unnecessary part variety

B. Make component orientation and assembly more difficult

C. Reduce avoidable part count and assembly complexity

D. Eliminate all tolerance specifications

Correct Answer: C. Reduce avoidable part count and assembly complexity

Question 8

Why can a lifecycle assessment produce different results for the same product?

A. Physical laws change between studies

B. System boundaries, functional units and data assumptions may differ

C. Customer preferences are never relevant

D. Manufacturing is always excluded

Correct Answer: B. System boundaries, functional units and data assumptions may differ

Question 9

A QFD matrix has one requirement with importance 5 and relationship weight 9, and another with importance 3 and relationship weight 3. What is the combined priority contribution?

A. 24