Product & Service Design: Principles, Processes & Case Studies

TAKEAWAYS:

• Product design is a structured process that balances functionality, cost, and customer needs using tools like QFD (Quality Function Deployment) and DFM (Design for Manufacturability).
• Service design follows a blueprinting approach (e.g., service encounter maps) to ensure seamless customer experiences, as seen in eSewa’s digital payment flow or Pathao’s ride-hailing process.
• Key principles (e.g., modularity, standardization, aesthetics) reduce costs and improve scalability—Daraz’s modular product packaging cuts logistics expenses by 15%.
• Emerging issues include sustainability (circular design), personalization (AI-driven customization), and digital integration (IoT-enabled products).
• Worked examples tie theory to practice: Nabil Bank’s loan approval process (service design) or Himalayan Java’s coffee bean roasting line (product design).
• Exam focus: Expect case studies (e.g., BIROI electronics), comparison tables (product vs. service design), and quantitative questions (e.g., cost trade-offs in design choices).

1. Definitions: Product vs. Service Design

Core Definitions

mindmap
  root((Product Design))
    Principles["1. **Functionality**
               2. **Aesthetics**
               3. **Cost Efficiency**
               4. **Manufacturability**"]
    Tools["QFD, DFM, CAD"]
    Example["Apple iPhone: **Modular design** for repairs (e.g., battery replacement)"]

  root((Service Design))
    Principles["1. **Customer Journey**
               2. **Touchpoints**
               3. **Reliability**
               4. **Recovery Systems**"]
    Tools["Service Blueprinting, Empathy Maps"]
    Example["eSewa: **Multi-step digital flow** (authentication → payment → confirmation)"]

• Product Design: The engineering and artistic process of creating a physical good (e.g., a phone, textile fabric) that meets technical, economic, and user requirements. Example: Hetauda Kapada Udhyog Ltd. designs standardized fabric patterns to reduce waste and appeal to mass markets.

• Service Design: The systematic planning of intangible experiences (e.g., banking, ride-sharing) to ensure efficiency, consistency, and customer satisfaction. Example: Pathao’s driver-app interface is designed for low-literacy users with minimal text.

Key Differences

2. Product Design: Principles and Process

Core Principles

1. Functionality: Must perform its intended purpose (e.g., Nabil Bank’s ATM must dispense cash reliably).
2. Aesthetics: Appeals to target customers (e.g., Daraz’s minimalist packaging for eco-conscious buyers).
3. Cost Efficiency: Balances development costs vs. manufacturing costs (e.g., Himalayan Java’s bulk coffee roasting).
4. Manufacturability: Designed for easy production (e.g., modular phone designs like Google Pixel).
5. Sustainability: Uses recyclable materials (e.g., Chaudhary Group’s eco-friendly textiles).

Product Design Process

flowchart LR
  A["Market Research"] --> B["Concept Development"]
  B --> C["Feasibility Study<br/>(Cost, Tech, Legal)"]
  C --> D["Prototype<br/>(3D Printing, CAD)"]
  D --> E["Testing<br/>(User, Stress, Durability)"]
  E --> F["Design Optimization"]
  F --> G["Final Design<br/>(Technical Drawings, BOM)"]
  G --> H["Launch<br/>(Pilot, Full Scale)"]

Worked Example: Daraz’s Product Design for Nepali Market

• Challenge: High shipping costs due to fragmented last-mile delivery.
• Solution:
  • Modular packaging: Standardized boxes reduce material costs by 15%.
  • Localized designs: Lighter, smaller products for hilly regions (e.g., solar lamps).
  • DFM (Design for Manufacturability): Partnered with Chinese suppliers for cost-effective assembly.

3. Service Design: Frameworks and Applications

Service Design Process

flowchart TD
  A[Define Customer Needs
  (Empathy Maps)] --> B[Map Customer Journey
  (Touchpoints: Pre-Service, Service, Post-Service)]
  B --> C[Develop Service Blueprint
  (Frontstage: Customer View
  Backstage: Support Processes)]
  C --> D[Prototype
  (Low-Fidelity: Paper
  High-Fidelity: Digital Mockups)]
  D --> E[Test
  (Pilot Groups, A/B Testing, Usability Studies)]
  E --> F[Implement
  (Staff Training, IT Integration, SOPs)]
  F --> G[Monitor
  (NPS, Complaint Rates, Performance Metrics)]

Service design process with explicit stages and deliverables for clarity.

Key Tools

1. Service Blueprinting:

   • Visualizes customer actions vs. company processes.
   • Example: eSewa’s payment flow:

     Customer: Logs in → Selects Bill → Enters Amount → Confirms
     System: Validates → Deduction → SMS Alert
     

   • Failure Points: If SMS alert fails, recovery system (call center) kicks in.

2. Empathy Maps:

   • Captures customer thoughts/feelings at each touchpoint.
   • Example: Pathao driver’s experience:

     Touchpoint	Customer Says	Driver Thinks
     Ride Requested	"Finally a ride!"	"Traffic is bad today..."
     Navigation	"Why is it taking long?"	"Google Maps is wrong!"

3. Journey Mapping:

   • Tracks emotional highs/lows in a service.
   • Example: Nabil Bank’s loan approval:

     1. Apply Online (Frustration: "Too many forms!")
     2. Document Submission (Relief: "Submitted!")
     3. Approval Wait (Anxiety: "Will I get it?")
     4. Disbursement (Joy: "Got the money!")
     

4. Emerging Issues in Product and Service Design

Case Study: NTC’s Smart Meter Design

• Challenge: Manual meter reading led to billing errors and delays.
• Solution:
  • IoT-enabled meters transmit usage data real-time.
  • Service Design: Customers get SMS alerts for high consumption.
  • Result: 30% reduction in billing disputes.

5. Worked Example: Hetauda Kapada Udhyog Ltd. (Textile Design)

Scenario: Hetauda Kapada Udhyog Ltd. wants to expand from local to national markets but faces:

• High inventory holding costs for unsold fabrics.
• Customer complaints about color mismatches.

Solution Using Product Design Principles:

1. Standardization:
   • Limit fabric colors to 10 standard shades (reduces inventory by 20%).
2. Modular Design:
   • Offer interchangeable fabric strips for custom orders (e.g., saris).
3. DFM (Design for Manufacturability):
   • Use automated dyeing machines to ensure color consistency.
4. Service Design for Retailers:
   • Provide digital swatch cards (QR codes) so retailers can order samples instantly.

Cost-Benefit Analysis:

6. Quality Function Deployment (QFD): Bridging Customer Needs to Design

What is QFD? A matrix-based tool that translates customer wants into engineering specifications. Used by: Toyota (lean manufacturing), Apple (product development).

QFD Process:

flowchart LR
  A[Customer Needs
  (E.g., "Easy to use", "Durable")] --> B[Importance Rating
  (1-5 Scale)]
  B --> C[Competitor Benchmark
  (Score: 1-5)]
  C --> D[Technical Requirements
  (E.g., "Button size: 1.2cm", "Material: ABS plastic")]
  D --> E[Relationship Matrix
  (Strong/Weak/Linear/None)]
  E --> F[Target Values
  (E.g., "Button reach: ≤2cm")]
  F --> G[Design Specifications
  (Final engineering specs)]

Example: Designing a Nepali Solar Lamp

Nepali Application:

• Himalayan Java’s solar-powered coffee grinders:
  • Customer Need: "Works in rural areas with no electricity."
  • Technical Solution: Solar panel + battery backup.

7. In the Real World

1. Daraz: Modular Product Design for E-Commerce

• Idea Used: DFM (Design for Manufacturability) + Standardization
• How:
  • Modular packaging: All products use 3 standard box sizes, reducing shipping costs by 15%.
  • Localized designs: Lighter products for hilly regions (e.g., solar lamps instead of heavy appliances).
• Impact: 30% faster delivery in Kathmandu Valley vs. rural areas.

2. eSewa: Service Design for Digital Payments

• Idea Used: Service Blueprinting + Customer Journey Mapping
• How:
  • Multi-channel support: Customers can pay via app, SMS, or IVR.
  • Failure recovery: If payment fails, automatic callback from eSewa’s IVR.
• Impact: 90% customer satisfaction rate (Nepal’s highest for fintech).

3. Nabil Bank: Loan Approval as a Service Design

• Idea Used: Journey Mapping + Empathy Maps
• How:
  • Problem: Long approval times caused customer drop-offs.
  • Solution:
    1. Digital pre-approval: Customers get instant eligibility score.
    2. Progress tracker: SMS updates (e.g., "Your loan is 60% approved").
    3. 24/7 chatbot: Answers queries instantly.
• Impact: 40% faster approvals, 25% increase in loan applications.

8. Exam Tip: How to Score Full Marks

For Case Studies (e.g., BIROI Electronics)

1. Structure Your Answer:

flowchart LR
  A[Introduction
  (Case context + key players)] --> B[Key Issues
  (SWOT, gaps, constraints)]
  B --> C[Theoretical Framework
  (QFD, DFM, Service Blueprint)]
  C --> D[Solutions
  (Link to Toyota/Apple examples)]
  D --> E[Conclusion
  (Impact: cost savings, customer satisfaction)]
  E --> F[Recommendations
  (Actionable steps)]

Case study structure with explicit analysis and solution phases. 2. Use the PESTEL Framework for broader analysis:

For Short Questions (e.g., "Principles of Product Design")

• Must Include:
  • Definition (1 mark).
  • 3-4 principles with examples (3 marks).
  • One Nepali/global application (2 marks).

For Quantitative Questions (e.g., Cost Trade-offs)

• Example Question:

  "The annual demand of a product is 10,000 units. Each unit costs Rs. 100 if orders are <200 units but Rs. 95 for ≥200 units. Holding cost is 10% of inventory value. What’s the optimal order quantity?"

• How to Solve:
  1. Identify cost components:
     • Ordering cost (S): Fixed cost per order (assume Rs. 500).
     • Holding cost (H): 10% of Rs. 95 = Rs. 9.5 per unit/year.
  2. Use EOQ formula (from Unit 6, but applicable here): $$Q^{\ast }=\sqrt{\frac{2DS}{H}}$$ Where:
     • $D=10,000$ units,
     • $S=500$,
     • $H=9.5$.
  3. Calculate: $$Q^{\ast }=\sqrt{\frac{2\times 10,000\times 500}{9.5}}\approx 320\text{ units}$$
  4. Check price break:
     • Since 320 > 200, use Rs. 95/unit.
  5. Conclusion: Order 320 units per batch to minimize total cost.

Common Mistakes to Avoid

• Ignoring the context: Always relate answers to Nepal’s business environment (e.g., "Given Nepal’s rural-urban divide, modular designs are critical").
• Overlooking service design: Many students focus only on products; service questions (e.g., banks, eSewa) are high-weightage.
• No numerical justification: For cost/benefit questions, always show calculations.

Final Visual Summary: