Applicability of Lean Six Sigma

During process improvement, Lean Six Sigma is often applied to two primary activities in an organization: service design and service delivery. These two activities are key to an organization’s ability to achieve excellence in its service product, service delivery process, and customer-provider interaction. They are also where nonvalue-adding activities can often be found.

Service design includes all of the activities associated with identifying elements of the service and creating the service. Three groups of activities comprise service design.

Service Product Design

Service product design refers to defining and designing all of the items that comprise the service. For example, the service product design for a restaurant includes the menu design, decisions on what kind of dining utensils, linens, music, and flowers to use, and service protocols.

Service Facility Design

Service facility design refers to the physical layout of the space where the service is delivered. For example, the facility design for a classroom includes the arrangement of desks and chairs, plus whiteboards. The quality of the facility design will directly affect the customers’ perception of the quality of the service.

Service Process Design

Service process design refers to designing the process for delivering service products to customers and maintaining those products. For example, in a car rental center, the service process includes all of the steps for renting a car to a customer.

Service delivery process refers to all of the activities involved in delivering the service to the customer.

Service Delivery Process

The service delivery process includes the steps necessary for delivering the service products to customers. The ideal service delivery process can deliver the routine service smoothly, effortlessly, and predictably; it also has the flexibility to deal with abnormal service requirements, personalized services, and difficult situations.

Service Encounter Environment

The service encounter environment is where the service is delivered and the customer-provider interaction occurs. For example, in a doctor’s office, the service environment includes waiting rooms, examination rooms, and bathrooms. Important elements in the service encounter environment include lighting, air quality, odor, noise, and cleanliness.

Customer-Provider Interaction

The customer-provider interaction is generally part of service delivery. In the car rental business, the representative should greet customers politely and ask customers for their car preference. The whole service process includes both the execution of process steps and the human interaction.

When seeking to eliminate waste, increase speed, and reduce defects in a service organization, you should not neglect any processes that have an impact on customer satisfaction.

Even a small change, such as redecorating a waiting room in a doctor’s office, can have an impact on customer satisfaction and, by extension, the bottom line.

Service processes tend to be slow, and slow processes tend to have problems with quality. An estimated 30-50% of the cost in a service organization is related to slow speed and to rework required to satisfy customer needs.

One reason why service processes are slow is that they are often complex and contain multiple nonvalue-adding “activities,” such as reports waiting on a desk, e-mails in an electronic inbox, or sales orders in a database. It’s not uncommon for work to spend as much as 90% of its time waiting between steps. This work-in-process is a waste that can be eliminated.

Using the Pareto principle, 80% of the delay is caused by less than 20% of the activities. This means that you only need to improve the speed of 20% of a process’s steps to achieve an 80% reduction in cycle time.

Many jobs in service organizations share characteristics that make them prime candidates for Lean Six Sigma improvement. For example, consider the kind of waste and time delays caused by these common situations:

Having to Chase Down Information to Complete A Task

Information is to service organizations as material is to manufacturing. If information is difficult to find or nonexistent, processes slow or stop. For example, to answer customer queries, call center operators access technical manuals and databases, and contact other operators for information. This often adds wait time for the customer.

Using Multiple Decision Cycles to Complete Work

Multiple decision cycles create a complex process of decision making, which moves up from the operational level to strategic levels. For example, a financial institution requires four levels of approval on any personal loan over $10,000. While this approval process ensures everyone is informed, it adds a great deal of wait time to the process.

Being Constantly Interrupted While Trying to Complete A Task

Telephones, e-mail, instant messaging capability, and questions from peers and customers – all of these interruptions can have a profound effect on worker productivity. For example, information workers, such as actuaries, send and receive an average of 204 e-mails per day, and experience an average of six interruptions each hour in a typical workday. These interruptions add to employees’ nonproductive time.

Performing Work in Batches

Working in batches means that workers must accumulate a group of items before they can start working. For example, insurance company data entry specialists must wait until they have a batch of 40 policy forms from a pre-approval process before entering them into the system.

Performing Tasks That Can Get Lost Between Organizational Units

When various departments are not seamlessly integrated as one single unit, they start working like silos; a lot of nonvalue-added work must be done just to get information and communication moving between silos. For example, current sales information in Finance is created separately and is updated by the account clerk at the end of every month from the sales reports.

The accounting department and external customers of a multinational corporation are complaining about the organization’s invoicing system. It takes much longer than it should to complete and submit an invoice to accounts payable. Customers find the invoices confusing, and often call the accounting department for clarification. A preliminary investigation indicates that, in addition to other problematic issues, there is no standard operating procedure (SOP) for filling out the invoice.

Management takes immediate action. The cost of poor quality (COPQ) is used to justify the project financially. Using failure mode effects analysis (FMEA), COPQ is estimated to cost the company $400,000 a year, in addition to the loss of customer goodwill. A goal is established to reduce service-processing time by 20-30%, which should produce a cost savings of over $100,000 in the first year.

Management decides to use Six Sigma for its structured DMAIC problem-solving methodology, rigorous toolkit, and statistics, which will be needed to control improvements. Lean tools and techniques will be pulled in and used as needed within the DMAIC structure.

During the Define phase, the project team identifies the parameters of the problem and determines how to conduct the project.

The team uses the following tools, processes, and steps:

Project Charter

The project’s goals, scope, budget, personnel, resources, and the problem to be resolved are documented in the project charter.

SIPOC Diagram

A SIPOC diagram is drawn to learn all the relevant elements of the project – suppliers, inputs, processes, outputs, and customers. This diagram serves as a value stream map (VSM) of the help desk operation.

Voice of The Customer (VOC)

The team members interview employees and external customers to learn what level of service they expect from the help desk. In addition to phone interviews, team members send out surveys.

Critical to Quality (CTQ) Issues

Using the results from VOC, the team narrows in on the elements that are critical to quality for the help desk operations.

Next, during the Measure phase, the team collects data about cycle time and help desk processes. The team

Measures Cycle Time

Cycle time is found to be 167 minutes with a standard deviation of 81 minutes.

Constructs A Current-State Value Stream Map and A Future-State Value Stream Map

The current-state value stream map reveals one nonvalue-added step that can be eliminated. The future-state value stream map is analyzed to determine the potential for reducing cycle time in each step.

Creates A Detailed Process Map

The inputs and outputs in each step are identified, and the team determines whether steps are controllable or not. Steps that are controllable can be improved.

Next, the team analyzes each step on the process map to determine root causes of problems. The current-state and future-state value stream maps are studied to determine whether there are gaps that represent areas for improvement. Then, the team brainstorms intensively and creates a cause and effect diagram to identify all potential causes of long service-processing time.

The team concludes that the root causes of long service-processing time are the lack of a documented SOP and lack of expertise among the technical help desk personnel.

The team adopts a multi-pronged approach during the Improve phase. It recommends that the organization:

  • develop an SOP to help deliver the services quickly and effectively
  • establish a requirement that anyone wanting to work on the help desk must have a minimum of two years of technical experience
  • monitor the help desk semi-annually to ensure that employees are staying current with changes in technology

During the last phase of the Six Sigma project, the team creates a checklist for internal strategic management to use, and a control chart to monitor service-processing time over the long term.