Skip to main content

Analysis Tools - VoC

1) Customer / Feature Diagram


 


๐Ÿ”น 1. Basic Features – “Must-Have”

Definition: These are the essential features that customers require. If they are missing, the product or service is immediately rejected—regardless of how innovative or attractive other features may be.

  • Customer View: “I need this.”
  • Impact: Absence leads to dissatisfaction and rejection.
  • Examples:
    • A car must have brakes.
    • A hotel room must have a bed.
    • A mobile app must function without crashing.

Business Implication: These features are non-negotiable. They must be delivered reliably and consistently.


๐Ÿ”น 2. Expected Features – “Should-Have”

Definition: These are features that customers assume will be included based on industry standards or past experiences. Their presence doesn’t necessarily delight, but their absence causes disappointment.

  • Customer View: “I expect this.”
  • Impact: Presence maintains satisfaction; absence causes frustration.
  • Examples:
    • Free Wi-Fi in hotels.
    • Warranty with electronics.
    • Easy navigation in a website.

Business Implication: These features help meet baseline expectations and are crucial for maintaining competitiveness.


๐Ÿ”น 3. Exciting Features – “Delighters”

Definition: These are unexpected but desirable features that surprise and delight customers. They are not required, but their presence can significantly enhance customer satisfaction and loyalty.

  • Customer View: “Wow, I didn’t expect this!”
  • Impact: Presence creates strong positive emotions; absence doesn’t hurt.
  • Examples:
    • Complimentary upgrades.
    • Personalized thank-you notes.
    • Innovative design elements.

Business Implication: These features can be used to differentiate your offering and create emotional connections with customers.

2) Affinity Diagram :

An Affinity Diagram is a visual tool used to group ideas, observations, or feedback into meaningful categories based on their natural relationships. It helps teams make sense of large volumes of information by identifying patterns and themes.

๐Ÿ› ️ Steps to Create an Affinity Diagram for VoC

  1. Gather Raw Data
    Collect customer feedback from various sources—verbatim comments, survey responses, support tickets, etc.

  2. Write Each Idea on a Card or Sticky Note
    Each piece of feedback should be written separately to allow flexible grouping.

  3. Group Similar Ideas Together
    Without predefined categories, group notes based on similarity or shared themes.

  4. Label Each Group
    Assign a heading that summarizes the theme of each cluster (e.g., “Ease of Use,” “Pricing Concerns,” “Customer Support”).

  5. Review and Refine
    Discuss with stakeholders to validate groupings and identify priority areas.



Kano Diagram: Understanding Customer Satisfaction Through Feature Classification

The Kano Model is a powerful tool used in Voice of the Customer (VoC) analysis to categorize product or service features based on how they influence customer satisfaction. Developed by Professor Noriaki Kano, this model helps businesses prioritize features that deliver the most value.


๐Ÿ”น Three Main Feature Categories

  1. Basic Needs (Must-Be)

    • These are essential features. Their absence causes dissatisfaction, but their presence doesn’t increase satisfaction.
    • Example: A hotel room must have a bed.
  2. Performance Needs (One-Dimensional)

    • These features directly correlate with satisfaction—the better they are, the happier the customer.
    • Example: Faster internet speed in a hotel.
  3. Excitement Needs (Delighters)

    • Unexpected features that pleasantly surprise customers. Their absence doesn’t cause dissatisfaction, but their presence boosts satisfaction.
    • Example: Free room upgrade or welcome gift.





✅ Why Use the Kano Diagram?

  • Helps prioritize features based on customer impact
  • Supports strategic product design and innovation
  • Enhances customer satisfaction and loyalty



Comments

Popular posts from this blog

Voice of the Customer (VoC) vs Voice of the Business (VoB)

  Tthe differences and strategic importance of Voice of Business (VoB) and Voice of Customer (VoC) in Lean Six Sigma: Voice of Business vs Voice of Customer: Aligning Strategy with Value In the world of Lean Six Sigma , success hinges on understanding and balancing two critical perspectives: the Voice of the Customer (VoC) and the Voice of the Business (VoB) . While both are essential for driving sustainable growth and operational excellence, they represent distinct priorities that must be harmonized for optimal results. ๐Ÿ”Š Voice of the Customer (VoC) Definition : VoC refers to the needs, expectations, preferences, and feedback of the customer—whether internal or external. Focus Areas : Product/service quality Delivery timelines Customer experience Responsiveness and support Methods of Capturing VoC : Surveys and interviews Focus groups Customer complaints and feedback Net Promoter Score (NPS) Goal : To ensure that processes and outputs are aligned with what the customer truly ...

Control Chart in Lean Six Sigma

Control Chart in Lean Six Sigma Introduction In Lean Six Sigma , a control chart is a fundamental statistical tool used to monitor process performance over time and ensure that improvements are sustained . It belongs primarily to the Control phase of DMAIC , where the focus is on maintaining process stability and preventing regression after improvements have been implemented. A control chart helps distinguish between normal process variation and abnormal variation that requires investigation and corrective action. What Is a Control Chart? A control chart is a time-ordered graphical display of process data with statistically determined limits. It answers a critical question: Is the process stable and predictable, or is something unusual happening? A typical control chart consists of: Center Line (CL) – the process average or mean Upper Control Limit (UCL) – upper boundary of expected variation Lower Control Limit (LCL) – lower boundary of expected variation Plotted data points o...

Defect Leakage

Defect leakage occurs on the Customer or End User side after the delivery of the application. Once the application has been released to the client, if the end user gets any kind of defect using the application, it is called "Defect leakage". Formula for Defect Leakage: Defect Leakage = Number of Defect found during next phase / ( Number of Defects found during testing + Number of Defects found during next phase) * 100 For Example, During the UAT production site, 50 defects were detected by the end users and 150 defects were detected throughout the QA process, including both the test site and the production site. Therefore, the defect leakage would be: Defect Leakage = (50/150)*100 Defect Leakage =33 % Reasons for Defect Leakage: Absence of stringent test cases walkthrough and review process. Environment differences. Missing test cases to cover appropriate condition. Poorly designed test case due to misunderstood requirements. Incorrect deployment in UAT or production. Use of ...