Jump to content

Sandeep V Achari

Excellence Ambassador
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Average

About Sandeep V Achari

  • Rank
    Newbie

Profile Information

  • Name
    Sandeep V Achari
  • Company
    Conduent LLP
  • Designation
    Quality Assurance Senior Analyst

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yes, we need to ensure below points are considered while taking VOC. 1. Identifying all relevant customer groups Identify your customers This includes identifying internal groups who have insight into the bill-paying customer. This was illustrated in a Life Insurance retention project that gathered Voice of the Customer from current and former policyholders; VOC missed a key component; namely, whether customers were given alternatives to help decrease premium payments. This was only identified much later in the project, through involvement of Call Center representatives during the Improve phase. How to avoid: In addition to providing process flow information, the SIPOC (Suppliers, Input, Process, Output, and Customers – see below for diagram) can help you identify customer groups you might otherwise forget. In a SIPOC, the customer is defined as any person or group who receives the output from a process step. A good example comes from a project that identified Agents as a customer group for the Endorsement process, where bill-paying customers request changes to their insurance coverage. After analyzing external customer data, a sample of ‘best practice’ Agents were interviewed. This served as a key source of recommendations to implement across all Agencies. SIPOC template 2. Clarifying goals of the data collection step upfront What do you want to know? One common mistake is to focus too much on the outcome, and not enough on factors that may influence that outcome. This can result in Voice of the Customer data that doesn’t provide enough detail around these input factors, which are often the keys to identifying potential improvements. This is illustrated in a project focused on reduction of employee calls to the company service desk. One of the themes identified through VOC was lack of information available to employees to resolve issues on their own. Because there was not enough detail on what types of information employees needed, it was necessary to conduct an additional round of data collection. 3. Using the correct data collection method for the type of information you need Choose your collection methods wisely There are a variety of data collection methods to choose from, including: surveys, one-on-one interviews, focus groups, and user testing/observation. One of the most frequent mistakes at this stage is over-reliance on surveys; although interviews and focus groups are more labor-intensive than surveys, they are generally much more effective in gathering detailed qualitative information that can help lead to improvement. How to avoid: Understand the pros and cons of each method, and consider the use of multiple data collection methods. Often, phone interviews and on-line focus groups can provide a good balance between need for efficiency and need for detailed Voice of the Customer data. You should also use the goals identified in the previous step to help guide your choice of which method(s) to use. 4: Doing the work of translating customer statements to Critical-to-Quality characteristics (CTQs): It’s imperative to operationalize customer CTQs, because this is what feeds into subsequent phases such as gathering baseline measures, identifying root causes, and developing Control Plan metrics. Many times, initial verbatim comments are not themselves specific or actionable enough. For example, suppose a customer says he/she wants “good customer service”: what does this really mean? You need to either probe the customer on what he/she means, or translate this statement in some other way, such as brainstorming with your project team. How to avoid: You can use a tool such as the CTQ tree to translate customer input into CTQs. In using a CTQ tree, you keep asking the question: “What does that mean?” until you reach the proper level. This approach can either be used directly during the VOC data collection, or after the fact as a team brainstorming tool. The example below shows how you can get from a generic statement (“Good customer service”) to more specific CTQs. CTQ Tree example Summary By looking at Voice of the Customer as a process and by taking advantage of the tools available in the Six Sigma toolkit, you can gather the right information from the right people using the right method. This will lead to objective CTQ measures that will serve as critical input throughout the DMAIC phases, which in turn will allow you to achieve maximum results. Let the voice of the customer (VOC) drive your process improvements, and other key areas of your business. Your main business goal after all, is to go beyond your customer’s expectations.
  2. Dear All, Robotics Process Automation is a new trend in the industry and I would like to know how Lean Six Sigma Practitioner can add value to RPA projects. Regards, Sandeep Achari
×
×
  • Create New...