By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
SmartData Collective
  • Analytics
    AnalyticsShow More
    data science anayst
    Growing Demand for Data Science & Data Analyst Roles
    6 Min Read
    predictive analytics in dropshipping
    Predictive Analytics Helps New Dropshipping Businesses Thrive
    12 Min Read
    data-driven approach in healthcare
    The Importance of Data-Driven Approaches to Improving Healthcare in Rural Areas
    6 Min Read
    analytics for tax compliance
    Analytics Changes the Calculus of Business Tax Compliance
    8 Min Read
    big data analytics in gaming
    The Role of Big Data Analytics in Gaming
    10 Min Read
  • Big Data
  • BI
  • Exclusive
  • IT
  • Marketing
  • Software
Search
© 2008-23 SmartData Collective. All Rights Reserved.
Reading: Improvement Project for Services; Remember You’re Never Really Done
Share
Notification Show More
Latest News
SMEs Use AI-Driven Financial Software for Greater Efficiency
Artificial Intelligence
data security in big data age
6 Reasons to Boost Data Security Plan in the Age of Big Data
Big Data
data science anayst
Growing Demand for Data Science & Data Analyst Roles
Data Science
ai software development
Key Strategies to Develop AI Software Cost-Effectively
Artificial Intelligence
ai in omnichannel marketing
AI is Driving Huge Changes in Omnichannel Marketing
Artificial Intelligence
Aa
SmartData Collective
Aa
Search
  • About
  • Help
  • Privacy
Follow US
© 2008-23 SmartData Collective. All Rights Reserved.
SmartData Collective > Big Data > Data Mining > Improvement Project for Services; Remember You’re Never Really Done
AnalyticsCollaborative DataData MiningData QualityData VisualizationData WarehousingDecision ManagementStatistics

Improvement Project for Services; Remember You’re Never Really Done

knowwareman
Last updated: 2012/04/13 at 4:40 PM
knowwareman
8 Min Read
SHARE

I am no longer surprised by the number of people who say, “I’m working on my Green Belt/Black Belt certification, but I’m not sure how to apply Six Sigma to [health care, telecom, hotels, food, transportation]—insert your service industry here. They just can’t seem to figure out how to translate manufacturing-oriented training and case studies to their industry. It’s not that difficult, but that’s what I do most of the time: help people translate the “map” used in manufacturing to their particular industry.

Contents
Where’s the pain?Find the dataMine the dataCreate the problem statement and gather a SWAT teamImplement and verify countermeasuresSustain the improvementRepeatProblem solving is easy

I am no longer surprised by the number of people who say, “I’m working on my Green Belt/Black Belt certification, but I’m not sure how to apply Six Sigma to [health care, telecom, hotels, food, transportation]—insert your service industry here. They just can’t seem to figure out how to translate manufacturing-oriented training and case studies to their industry. It’s not that difficult, but that’s what I do most of the time: help people translate the “map” used in manufacturing to their particular industry.

While manufacturing focuses on reducing variation (I call it “deviation” because it deviates from the customer’s requirements), services can best benefit by focusing on eliminating defects, mistakes, and errors in the service delivery process.

More Read

data-driven approach in healthcare

The Importance of Data-Driven Approaches to Improving Healthcare in Rural Areas

Essential Productivity Hacks in Cloud-Centric Workplaces
Automotive Industry Uses Analytics To Solve Pressing Supply Chain Issues
How can CIOs Build Business Value with Business Analytics?
Seven Benefits of Using AI to Perform Text Analysis

Where’s the pain?

The first step is to identify the pain caused by defects, mistakes, and errors. Is it:

• Medication errors, hospital-acquired infections, surgical complications, ventilator-assisted pneumonia, repeat radiology or lab tests?

• Incorrect or inaccurate orders that lead to incorrect service delivery that leads to waste, rework, and lost profit?

• Inaccurate bills or invoices? Improperly applied payments? Denied insurance claims?

• Defects in delivered software?

• Preventable adjustments and credits?

Find the data

While define, measure, analyze, improve and control (DMAIC) lead most people to believe they need to start by defining and measuring something, data about the number or cost of these types of defects are already collected somewhere by someone. Find the data! As described in my previous article about Control Charts for Services, get the data into a format that can be graphed as a control chart.

Most corporate pain revolves around money: adjustments, credits, and and so on. Because Six Sigma focuses on cutting the cost of waste and rework, it’s often easiest to start with lost revenue or the cost of waste. Here’s an example of using the cost instead of a count of defects. This hospital system’s pain was denied insurance claims. I simply summarized and charted the monthly cost of denied claims.

The process was stable, so the hospital could plan on losing more than a million dollars a month. Until I combined the $100 denied here and the $1,000 denied there, it had no idea how much it was losing.

Mine the data

Once you know the level of pain, it’s time to start using Pareto charts to drill down. In this case, I started with various reason codes. Timely filing (i.e., not filing the claim within 30 days) was the main culprit.

But I rarely stop at the first level of Pareto chart. I drill down into the “big bar” to see if there’s a Pareto pattern within that. In this case, one insurer accounted for almost two-thirds of timely filing denials:

Create the problem statement and gather a SWAT team

Once the problem has been narrowed to the most granular level, it’s easy to write a problem statement. The “big bar” on the Pareto chart becomes the head of the fishbone diagram: During 2002–2003, Insurer 1 accounted for 64 percent of denials for timely filing ($7,849,569), which was higher than desired and caused lost profit:

Most companies make the mistake of convening a team before they know what problem they are trying to solve. By narrowing the focus using data, it’s easy to figure out who should be on the team. After showing this analysis to the sponsor, she immediately identified the five people that should be on the root cause team.

This “SWAT team” of experts was able to diagnose the root causes and define countermeasures in fewer than four hours.

Implement and verify countermeasures

The team figured out the problem on a Friday and implemented changes to work around this particular insurer on Monday. Getting the insurer to comply with its contract took a while longer.

To verify that the countermeasures actually reduced the pain, add data to the control chart begun when finding the data. In this case, the change resulted in savings of almost $5 million per year:

Notice that this also reduced the variability in denied claims, which means fewer surprises from month to month.

Sustain the improvement

Where most improvement projects go wrong is during the control phase of DMAIC. Project teams forget to put a control system in place. So once the solution has been verified, just continue to use the control chart to monitor the cost or count of defects forever, and implement corrective actions when it goes out of control.

Repeat

The team continued to work through other issues with rejected, appealed, and denied claims to save an additional $24 million.

Note: This project could have begun with the number of denied claims instead of the cost of denied claims and probably would have arrived at a similar answer, although sometimes the highest-volume defect is not the most expensive one.

Problem solving is easy

• Focus on the pain (defects or costs). If you don’t know what the pain is or where to find it, ask any manager or leader. They can usually tell you a half a dozen things that keep them up at night. • Find the data (defects or costs) • Control-chart the data to establish a baseline • Laser-focus the analysis using Pareto charts • Develop a problem statement • Convene a SWAT team to analyze root causes • Implement and verify countermeasures • Repeat until the pain is gone • Find a new source of pain and repeat the process

The good news is that you can start today; the bad news is that you are never done.

 

View Page:‹ Previous12Next ›

TAGGED: analytics, hospitals, mistakes, Productivity, six sigma
knowwareman April 13, 2012
Share this Article
Facebook Twitter Pinterest LinkedIn
Share

Follow us on Facebook

Latest News

SMEs Use AI-Driven Financial Software for Greater Efficiency
Artificial Intelligence
data security in big data age
6 Reasons to Boost Data Security Plan in the Age of Big Data
Big Data
data science anayst
Growing Demand for Data Science & Data Analyst Roles
Data Science
ai software development
Key Strategies to Develop AI Software Cost-Effectively
Artificial Intelligence

Stay Connected

1.2k Followers Like
33.7k Followers Follow
222 Followers Pin

You Might also Like

data-driven approach in healthcare
Analytics

The Importance of Data-Driven Approaches to Improving Healthcare in Rural Areas

6 Min Read
cloud technology for productivity boosts
Cloud Computing

Essential Productivity Hacks in Cloud-Centric Workplaces

8 Min Read
supply chain analytics
Analytics

Automotive Industry Uses Analytics To Solve Pressing Supply Chain Issues

6 Min Read
Analytics

How can CIOs Build Business Value with Business Analytics?

8 Min Read

SmartData Collective is one of the largest & trusted community covering technical content about Big Data, BI, Cloud, Analytics, Artificial Intelligence, IoT & more.

ai is improving the safety of cars
From Bolts to Bots: How AI Is Fortifying the Automotive Industry
Artificial Intelligence
data-driven web design
5 Great Tips for Using Data Analytics for Website UX
Big Data

Quick Link

  • About
  • Contact
  • Privacy
Follow US

© 2008-23 SmartData Collective. All Rights Reserved.

Removed from reading list

Undo
Go to mobile version
Welcome Back!

Sign in to your account

Lost your password?