Product, Service and Process Design

Introduction

Operations performance is largely determined before production or service delivery begins. A product’s materials, features, tolerances, and assembly method influence cost and quality. A service’s customer journey, information requirements, employee roles, and recovery procedures influence satisfaction and reliability. Process design converts these product or service requirements into a coordinated system of activities, resources, technologies, controls, and responsibilities.

For total quality management (TQM), design is a preventive activity. It seeks to build quality into products and processes rather than relying primarily on inspection or correction after failure. Effective design balances customer value, technical feasibility, operating cost, speed, flexibility, safety, environmental responsibility, and regulatory compliance.

This chapter examines design thinking, quality function deployment, value analysis, standardization, modularity, service blueprinting, design for manufacturability and sustainability, and the product–process matrix. These approaches are complementary: design thinking explores needs, QFD translates them, value analysis improves the value proposition, standardization and modularity support consistent operations, and process-design tools ensure that delivery is feasible and sustainable.

Learning Objectives

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

1. Explain the relationship between product, service, and process design.
2. Apply the stages of design thinking to an operations problem.
3. Use quality function deployment to translate customer requirements into technical priorities.
4. Apply value analysis and value engineering to improve value without compromising essential performance.
5. Explain how standardization and modularity affect quality, cost, variety, and flexibility.
6. Construct and interpret a service blueprint.
7. Apply principles of design for manufacturability, assembly, serviceability, and sustainability.
8. Use the product–process matrix to assess strategic fit and operating risk.
9. Evaluate design decisions ethically, environmentally, and operationally.

1. Design as an Operations Decision

A product is a tangible output, such as a pump, food package, or medical device. A service is an experience or performance delivered to a customer, such as banking, education, transport, or healthcare. Many contemporary offerings combine both: a smartphone includes hardware, software, warranty, and digital support; an airline sells transportation together with information, booking, and service recovery.

Process design specifies how inputs are transformed into outputs. Inputs may include materials, information, labour, equipment, energy, and customer participation. Outputs include physical goods, services, information, and outcomes. Design decisions determine:

• what the customer receives;
• how much variety is offered;
• the sequence of activities;
• required capacity and technology;
• quality standards and control points;
• labour skills and job responsibilities;
• environmental impacts and legal controls; and
• how failures will be prevented or recovered.

A useful design principle is that requirements should be clear, measurable, and traceable. For example, “easy to use” is a customer requirement, but it must be translated into observable criteria such as a maximum number of setup steps, training time, error rate, or accessibility requirement.

Design quality and conformance quality

Design quality concerns whether the intended features and performance satisfy customer and stakeholder needs. Conformance quality concerns whether the delivered product or service matches the approved design. A perfect production process cannot compensate for a design that misunderstands customer needs. Conversely, an excellent design will fail if the process cannot reproduce it consistently.

The design–operations interface

Designers and operations personnel must collaborate early. A design that appears attractive to marketing may require unusual materials, unstable suppliers, excessive manual work, or tolerances that are difficult to control. Early cross-functional review reduces late engineering changes, launch delays, warranty costs, and customer dissatisfaction.

A practical review team may include representatives from customers, marketing, design engineering, purchasing, production, quality, maintenance, logistics, finance, service, and sustainability. Suppliers and regulators should be included when their knowledge or approval is essential.

2. Design Thinking for Operations Improvement

Design thinking is a human-centred and iterative approach to solving poorly defined problems. It is particularly useful when users cannot fully articulate their needs or when existing assumptions are causing poor service or product experiences. A common model contains five overlapping activities:

1. Empathize: observe users, interview them, examine complaints, and understand their context.
2. Define: frame a specific problem based on evidence rather than assumptions.
3. Ideate: generate several possible solutions before selecting one.
4. Prototype: create a low-cost representation of the proposed product, service, or process.
5. Test: obtain user feedback, measure performance, and revise the design.

The stages are not strictly linear. Testing may reveal that the original problem was defined incorrectly, requiring a return to observation or problem framing.

Tools for design thinking

Ethnographic observation identifies what users actually do rather than what they claim to do. Personas represent important user groups, while journey maps show experiences across time. “How might we?” questions convert problems into opportunities. Prototypes may be sketches, mock-ups, role plays, digital simulations, sample layouts, or pilot procedures.

A prototype should answer a learning question. For example, a service team might test whether a self-service check-in screen reduces confusion. The prototype need not contain the final technology; it must be sufficient to test usability and process logic.

Critical evaluation

Design thinking encourages creativity and user involvement, but it is not a substitute for technical, financial, or regulatory analysis. User preferences may conflict, prototypes may be evaluated by unrepresentative participants, and attractive concepts may be operationally infeasible. Therefore, design thinking should be followed by structured feasibility, risk, cost, and quality evaluation.

3. Quality Function Deployment

Quality function deployment (QFD) is a structured method for translating the voice of the customer into technical and process requirements. Its best-known tool is the House of Quality. QFD supports cross-functional communication and creates traceability from customer expectations to design characteristics, process controls, and performance measures.

Main elements of a House of Quality

A typical House of Quality contains:

• customer requirements, often called “what” requirements;
• importance ratings for each requirement;
• technical characteristics, or “how” requirements;
• a relationship matrix connecting customer requirements to technical characteristics;
• a correlation roof showing relationships among technical characteristics;
• competitive or benchmark information; and
• calculated priorities for technical characteristics.

Relationships are often scored using 9 for strong, 3 for moderate, 1 for weak, and 0 for no relationship. These values are ordinal decision-support weights, not measurements of physical performance.

Weighted technical priority

A simple QFD priority score for technical characteristic j is:

where P_j is the priority score for technical characteristic j, I_i is the importance rating of customer requirement i, R_ij is the relationship weight between requirement i and characteristic j, and n is the number of customer requirements. The calculation assumes that the chosen importance and relationship scales are applied consistently. Scores help rank attention; they do not prove that the highest score is technically or economically optimal.

If competitive improvement or strategic weighting is included, a more complete score may be written as:

where G_i is an additional importance or improvement factor. The factor must be defined by the organization and should not be added merely to manipulate priorities.

Worked example

A company is redesigning a reusable delivery container. Customer requirements are secure closure, low weight, and easy cleaning, with importance ratings 5, 4, and 3. Technical characteristics are closure force, container mass, and surface roughness. Using relationship weights 9, 3, 1, or 0, suppose the relationships are:

The priorities are:

• Closure force: (5×9)+(4×0)+(3×1)=48
• Mass: (5×1)+(4×9)+(3×0)=41
• Surface roughness: (5×0)+(4×1)+(3×9)=31

Closure force receives the highest calculated priority. However, the team must also consider safety, durability, manufacturing capability, cost, and the possibility that excessive closure force could conflict with accessibility.

Benefits and limitations

QFD makes requirements visible, supports prioritization, and reduces the risk that technical teams optimize features that customers do not value. Limitations include subjective ratings, difficulty capturing latent needs, large matrices, and the possibility of treating customer needs as independent when they are interrelated. QFD is most effective when based on reliable customer evidence and updated as market and process knowledge develops.

4. Value Analysis and Value Engineering

Value is not equivalent to low price. In design, value is commonly considered as the relationship between function and total cost:

where V is a value index, F is the worth or performance of required function, and C is the relevant life-cycle cost. The expression is conceptual unless function and cost have been measured on compatible scales. It should not be used to justify reducing essential safety, legal compliance, or reliability.

Value engineering is applied during the design of a new product or process. Value analysis examines an existing product or process. Both use functional analysis to ask what a component or activity does, why it is needed, and whether the function can be achieved more effectively.

A structured value study commonly includes:

1. information gathering;
2. functional analysis using verb–noun descriptions, such as “support load” or “protect contents”;
3. creative generation of alternatives;
4. evaluation of technical, customer, risk, and cost consequences;
5. development and testing of the preferred alternative; and
6. implementation and follow-up.

Life-cycle cost should include acquisition, operation, maintenance, failure, disposal, and relevant environmental costs. Removing a cheap component may increase warranty failures or disposal impacts, reducing total value.

5. Standardization and Modularity

Standardization

Standardization establishes a consistent specification, method, component, interface, or operating procedure. It can reduce variation, simplify training, enable economies of scale, improve purchasing leverage, and make quality problems easier to detect. Standards may concern dimensions, materials, data formats, work methods, inspection criteria, or service scripts.

Standardization must be controlled rather than applied blindly. Excessive standardization can suppress innovation, reduce customization, and make a product unsuitable for diverse users. A standard should have an owner, revision process, effective date, training requirement, and method of verifying compliance.

Modularity

Modularity divides a product or process into relatively independent modules connected by defined interfaces. Examples include interchangeable vehicle components, configurable software services, furniture systems, and modular training programmes.

Modularity can provide variety through mass customization. Core modules are standardized, while selected modules are configured to customer requirements. It may reduce lead time, simplify maintenance, permit parallel development, and isolate failures. Its success depends on stable interfaces, clear specifications, and controlled configuration management.

The main trade-off is that modules and interfaces may add cost, weight, space, or performance constraints. A modular architecture should therefore be selected after considering demand variety, forecast uncertainty, change frequency, repair strategy, and life-cycle cost.

6. Service Blueprinting

Services are produced and consumed through interactions involving customers, employees, information, facilities, and technology. A service blueprint maps these interactions and separates what customers see from activities occurring behind the scenes.

A typical blueprint contains:

• customer actions: steps taken by the customer;
• frontstage or visible employee actions: interactions observable by the customer;
• backstage actions: support work not directly visible;
• support processes: information systems, suppliers, maintenance, and administration;
• physical evidence: locations, documents, screens, equipment, and communications;
• line of interaction: boundary between customer actions and employee contact;
• line of visibility: boundary between visible and invisible employee actions; and
• line of internal interaction: boundary between frontline work and support processes.

Blueprinting exposes handoffs, waiting, rework, failure points, and ownership gaps. It can be combined with failure mode and effects analysis (FMEA), queue analysis, customer-journey data, and process capability studies.

For example, in an outpatient appointment process, customer actions may include booking, arrival, registration, consultation, and payment. Visible actions include reception and clinical interaction. Backstage work includes record retrieval and room preparation. Support processes include scheduling software, insurance verification, cleaning, and equipment maintenance. A delay at any handoff can affect the complete experience even if individual activities appear efficient.

A blueprint should distinguish the ideal process from the actual process. Observation, transaction data, complaints, and employee knowledge are necessary to validate it.

7. Design for Manufacturability, Assembly, and Serviceability

Design for manufacturability (DFM) seeks to make a product easier and more economical to produce while meeting specified performance requirements. Design for assembly (DFA) focuses on reducing part count, simplifying orientation and handling, and enabling reliable joining. Design for serviceability considers inspection, diagnosis, repair, replacement, and safe maintenance.

Important DFM/DFA principles include:

• reduce unnecessary part count;
• use common materials and standard components where appropriate;
• avoid tolerances tighter than functional requirements;
• design parts for easy orientation and handling;
• provide access for tools, inspection, and maintenance;
• use mistake-proofing, or poka-yoke, to prevent incorrect assembly;
• specify robust joining methods;
• design clear interfaces and verification points; and
• involve production and suppliers before design freeze.

A tolerance is an allowed range around a nominal value. Tolerances should reflect function, process capability, measurement uncertainty, and safety requirements. Overly tight tolerances increase cost and may create unnecessary rejection; overly loose tolerances may cause poor performance.

DFM is not simply a cost-reduction exercise. It must preserve critical characteristics, worker safety, regulatory requirements, reliability, and customer value. Design reviews should use prototypes, capability evidence, assembly trials, and risk analysis rather than relying only on drawings.

8. Design for Sustainability

Sustainable design considers environmental, social, and economic impacts throughout the life cycle. Relevant stages include raw-material extraction, manufacturing, distribution, use, maintenance, reuse, recycling, and disposal.

Key practices include:

• reducing material and energy intensity;
• selecting safer and renewable or recycled materials where appropriate;
• increasing durability, repairability, and upgradeability;
• designing for disassembly and material recovery;
• reducing packaging and transport impacts;
• using life-cycle assessment rather than focusing on a single stage;
• avoiding hazardous substances and supporting regulatory compliance; and
• considering worker welfare, accessibility, and supply-chain ethics.

Life-cycle assessment (LCA) systematically evaluates environmental inputs and outputs across defined boundaries. Results depend on functional unit, system boundary, data quality, allocation rules, and impact categories. Consequently, environmental claims should be transparent and independently supportable.

The circular-economy perspective encourages maintaining products and materials at their highest practical value through repair, reuse, remanufacture, and recycling. However, circular strategies require appropriate reverse logistics, product identification, safe material separation, and viable markets for recovered materials. A recyclable design is not necessarily sustainable if collection and processing systems do not exist.

9. The Product–Process Matrix

The product–process matrix links product characteristics, especially variety and volume, with process characteristics, especially flexibility and flow. It is a strategic alignment tool rather than a rigid law.

A project process handles unique, complex outputs, such as construction. A job shop uses general-purpose resources for varied work. Batch production groups similar items, but changeovers create capacity and quality challenges. Repetitive lines support high-volume standardized products. Continuous processes operate with highly standardized flow, as in chemical or utility production.

The diagonal of the matrix represents a broad fit between product variety–volume and process structure. A position far from the fit may indicate strategic inconsistency. For example, a highly customized product made on a rigid flow line may generate excessive changeovers and errors. Conversely, a standardized high-volume item produced in a job shop may incur unnecessary cost and long lead times.

Service processes can also be interpreted through this logic. A specialist consultancy resembles a job shop, while a standardized digital transaction resembles a repetitive or continuous process. Hybrid systems are common, especially where postponement and modularity allow standard operations to be combined with late customization.

10. Integrating the Design Methods

The methods in this chapter should form a coherent design system:

1. Design thinking identifies user problems and opportunities.
2. QFD translates validated needs into measurable technical requirements.
3. Value analysis tests whether functions are delivered economically across the life cycle.
4. Standardization and modularity determine where consistency and variety should be located.
5. Service blueprinting or process mapping defines customer and operational interactions.
6. DFM, DFA, and serviceability reviews test feasibility and maintainability.
7. Sustainability assessment evaluates life-cycle impacts.
8. The product–process matrix tests whether the operating system fits demand and variety.
9. Pilots, capability studies, risk analysis, and customer feedback support controlled launch.

Design control should include requirements traceability, formal reviews, change control, validation, and post-launch learning. A design is not complete when a drawing or procedure is approved; it is complete when the organization can repeatedly deliver the intended outcome under real operating conditions.

Illustrative Case: Redesigning a University Meal-Delivery Service

Background

A university operated a meal-ordering service for students and staff. Complaints concerned late delivery, incorrect dietary selections, excessive packaging, and confusing refund procedures. The service used a small kitchen, several delivery zones, and a mobile ordering application.

Problem

Management initially proposed buying faster delivery vehicles. However, complaints indicated a broader design problem involving menu configuration, order batching, kitchen handoffs, delivery information, and service recovery.

Analysis

A design-thinking team observed ordering and collection, interviewed students with dietary restrictions, and mapped the customer journey. The service blueprint revealed that the application accepted orders after kitchen capacity had been reached. The kitchen printed paper tickets with incomplete allergy information. Drivers received batches without clear delivery sequence. Refund requests required a separate email and often lacked order evidence.

QFD converted the voice of the customer into requirements. The most important needs were accurate dietary information, reliable promised time, easy ordering, and simple recovery. Technical characteristics included validated menu data, capacity-controlled order slots, barcode verification, route sequencing, and an automated refund workflow.

Value analysis showed that adding more packaging layers would reduce leakage but increase waste and cost. A better alternative was a standardized recyclable container with a tested seal and a modular carrier system. Standard meal modules—base, protein, side, and sauce—allowed variety while reducing kitchen complexity. The product–process relationship moved from highly variable make-to-order work toward a batch and modular assembly system.

Approach and solution

The university introduced:

• capacity-based ordering windows;
• a controlled menu database with allergen fields;
• barcode checks at kitchen dispatch and delivery;
• modular meal components with standardized interfaces;
• a service blueprint with named process owners;
• a digital exception and refund process; and
• reusable or recyclable packaging evaluated across its life cycle.

A pilot was conducted in one delivery zone. Measures included on-time delivery, order accuracy, refund cycle time, packaging mass per meal, and customer satisfaction. Staff were trained using standard work, but a feedback channel allowed improvement suggestions and controlled revision of procedures.

Outcome

The pilot reduced avoidable errors and clarified accountability. The major improvement did not come from faster vehicles; it came from aligning demand information, capacity, modular design, process controls, and service recovery. The case is illustrative rather than a report of a real named organization; numerical performance claims are intentionally omitted because reliable baseline and post-implementation data are not available.

Learning points

• A visible symptom may arise from upstream design decisions.
• Customer requirements must be translated into operational characteristics.
• Modularity can provide variety without uncontrolled process complexity.
• Service blueprinting reveals hidden work and handoff failures.
• Sustainability decisions require life-cycle consideration.
• Pilots should measure both customer outcomes and process performance.

Challenges, Governance, and Contemporary Developments

Design decisions involve competing interests. A cheaper material may reduce affordability but increase environmental impact. Data-driven personalization may improve convenience but threaten privacy. AI-generated concepts may accelerate ideation but reproduce bias, infringe intellectual property, or obscure accountability. Automated design tools should therefore be governed through human review, data provenance, cybersecurity controls, explainable decision criteria, and documented validation.

Regulatory and ethical considerations include product safety, accessibility, consumer protection, data protection, occupational health, environmental claims, intellectual property, and responsible sourcing. Quality professionals should maintain evidence that requirements were identified, risks assessed, tests completed, and changes authorized.

Contemporary practice increasingly uses digital twins, additive manufacturing, mass customization, connected products, remote monitoring, and generative design. These technologies can shorten development cycles and improve resource use, but they also create new risks involving software updates, cybersecurity, data ownership, algorithmic bias, and dependence on specialized suppliers. Technology should be selected because it improves a defined customer or operational outcome, not because it is fashionable.

Best-Practice Checklist

Before approving a product, service, or process design, ask:

1. Which customer and stakeholder requirements are evidence-based?
2. Can every critical requirement be measured and traced?
3. Has a cross-functional team reviewed feasibility and risk?
4. Does the process fit expected volume, variety, and flexibility?
5. Are standardization and customization located deliberately?
6. Can the product be manufactured, assembled, serviced, and safely disposed of?
7. Have environmental and social impacts been considered across the life cycle?
8. Are failure prevention, inspection, and service recovery designed into the process?
9. Has the design been prototyped, piloted, validated, and approved under realistic conditions?
10. Is there a controlled method for learning and changing the design after launch?

Chapter Summary

Product, service, and process design determine much of the quality, cost, speed, flexibility, safety, and sustainability achieved by an operation. Design thinking provides a human-centred method for exploring uncertain problems. Quality function deployment translates customer requirements into technical priorities and supports traceability. Value analysis and value engineering improve the relationship between required function and life-cycle cost without sacrificing essential performance.

Standardization reduces unwanted variation and supports consistent operations, while modularity provides controlled variety through defined components and interfaces. Service blueprinting maps customer actions, visible and hidden employee work, support processes, and physical evidence. DFM, DFA, and serviceability principles ensure that designs can be produced, assembled, maintained, and repaired effectively. Sustainable design extends evaluation across the product or service life cycle. The product–process matrix helps align volume, variety, flexibility, and process structure.

The strongest designs integrate these methods through cross-functional review, risk analysis, piloting, validation, change control, ethical governance, and continual learning.

Key Terms

Design quality: The extent to which intended features satisfy customer and stakeholder needs.

Conformance quality: The extent to which delivered outputs match approved requirements.

Design thinking: An iterative, human-centred approach involving empathy, definition, ideation, prototyping, and testing.

Quality function deployment: A method for translating customer requirements into technical and process requirements.

House of Quality: A matrix-based QFD tool linking customer needs and technical characteristics.

Voice of the customer: Systematically collected information about customer needs, expectations, and problems.

Value engineering: Functional improvement performed during new-product or process design.

Value analysis: Functional and cost analysis of an existing product or process.

Standardization: Establishment of consistent specifications, methods, components, or interfaces.

Modularity: Division of a design into relatively independent units connected by defined interfaces.

Mass customization: Efficient provision of customer variety using standardized and configurable elements.

Service blueprint: A visual representation of customer actions, employee actions, support processes, and service evidence.

DFM: Design for manufacturability; designing products for efficient and capable production.

DFA: Design for assembly; designing products for simple, reliable, and economical assembly.

Serviceability: The ease with which a product can be inspected, diagnosed, maintained, and repaired.

Life-cycle assessment: Evaluation of environmental inputs and outputs across defined life-cycle boundaries.

Poka-yoke: Mistake-proofing that prevents or detects incorrect action.

Product–process matrix: A framework linking product volume and variety with process structure.

Configuration management: Controlled identification, approval, and tracking of design versions and changes.

Review Questions

Short Answer Questions

1. Distinguish design quality from conformance quality.
2. List the five commonly used stages of design thinking.
3. What is the purpose of the House of Quality?
4. State one benefit and one limitation of standardization.
5. What information does a service blueprint display?

Long Answer Questions

1. Explain how design thinking and QFD can be integrated in the development of a new service.
2. Discuss the contribution of value analysis, DFM, and serviceability analysis to total quality management.
3. Explain how modularity can increase variety while controlling process complexity.
4. Describe the principal elements of a service blueprint and explain how it identifies failure points.
5. Explain the product–process matrix and discuss the risks of operating far from the product–process fit.

Analytical / Application Questions

1. A manufacturer receives complaints about a product that is reliable but difficult to assemble and repair. Propose a cross-functional design review using QFD, DFM, DFA, and serviceability principles.
2. Design a service blueprint for an online university examination-registration process. Identify at least three possible failures and recommend preventive controls.
3. A company offers 200 product variants at low volume using a highly automated line. Analyse the likely consequences using the product–process matrix and recommend alternatives involving standardization, modularity, or process redesign.

Multiple Choice Questions with Answers

Question 1

Which activity is primarily associated with the empathy stage of design thinking?

A. Calculating machine depreciation

B. Observing and interviewing users

C. Approving the final production schedule

D. Setting the accounting period

Correct Answer: B. Observing and interviewing users

Question 2

In QFD, a strong relationship between a customer requirement and a technical characteristic is commonly represented by which value?

A. 0

B. 1

C. 3

D. 9

Correct Answer: D. 9

Question 3

Using P_j = ∑ I_iR_ij, what is the priority score for a technical characteristic with relationships 9 and 3 to requirements having importance ratings 4 and 2?

A. 14

B. 30

C. 36

D. 42

Correct Answer: B. 30

Question 4

Which statement best distinguishes value engineering from value analysis?

A. Value engineering is used only for services

B. Value analysis is used only for environmental assessment

C. Value engineering is generally applied during new design, while value analysis examines existing designs

D. Value engineering ignores function

Correct Answer: C. Value engineering is generally applied during new design, while value analysis examines existing designs

Question 5

What is a principal benefit of modularity?

A. It eliminates all interfaces

B. It permits controlled variety through defined modules

C. It guarantees zero defects

D. It always reduces material use

Correct Answer: B. It permits controlled variety through defined modules

Question 6

Which element of a service blueprint represents work that customers normally cannot see?

A. Backstage actions

B. Customer actions

C. Physical evidence only

D. The line of interaction

Correct Answer: A. Backstage actions

Question 7

Which practice is most directly associated with design for assembly?

A. Increasing unnecessary part count

B. Making components difficult to orient

C. Simplifying handling and joining of parts

D. Removing all inspection points

Correct Answer: C. Simplifying handling and joining of parts

Question 8

A high-volume, low-variety product is generally most compatible with which process type?

A. Project process

B. Job shop

C. Repetitive or assembly-line process

D. Individual craft process

Correct Answer: C. Repetitive or assembly-line process

Question 9

Which statement about life-cycle assessment is correct?

A. It evaluates only factory labour cost

B. Its conclusions are independent of system boundaries

C. It considers environmental inputs and outputs across defined life-cycle stages

D. It proves that every recyclable product is sustainable

Correct Answer: C. It considers environmental inputs and outputs across defined life-cycle stages

Question 10

A QFD technical priority calculated as 48 is best interpreted as what?

A. A guaranteed physical performance level

B. A ranking aid based on selected importance and relationship weights

C. A product price in currency units

D. A regulatory limit

Correct Answer: B. A ranking aid based on selected importance and relationship weights