Category: Academy

Reflections on Newly Acquired Knowledge

  • Applying DMAIC to Average Handle Time: A Practice Analysis

    One of the most important things I have learned during my Six Sigma certification journey is that DMAIC is not just a framework you read about. It is something you have to apply before it actually makes sense. So I did exactly that. I took a real world technical support scenario and walked it through every phase of DMAIC to see if I actually understood what I was doing.

    The scenario involved a technical support team of 25 agents across two shifts. Over 45 days the team handled 18,750 interactions and 4,219 of them exceeded the company Average Handle Time target of 8 minutes per interaction. Leadership wanted answers. I used DMAIC to find them.

    DEFINE

    The problem was clear. 4,219 out of 18,750 interactions exceeded the 8 minute AHT target over a 45 day period. Missing AHT creates higher labor costs per interaction, longer queue times for customers, and potential impact on service levels and customer satisfaction. The Critical to Quality measure for this analysis was simple: any interaction exceeding 8 minutes counts as a defect.

    MEASURE

    This is where the data started telling the real story.

    Overall Performance:
    Total Interactions: 18,750
    Total Defects: 4,219
    Yield: 77.5%
    DPMO: 225,013
    Sigma Level: 2.26

    Morning Shift Performance:
    Total Interactions: 11,250
    Total Defects: 1,349
    Yield: 88.01%
    DPMO: 119,911
    Sigma Level: 2.68

    Evening Shift Performance:
    Total Interactions: 7,500
    Total Defects: 2,870
    Yield: 61.73%
    DPMO: 382,667
    Sigma Level: 1.80

    The overall team was operating at 2.26 sigma. But the evening shift was operating at 1.80 sigma while handling 40 percent of total call volume and producing 68 percent of all defects. The problem was not organization wide. It was shift specific.

    ANALYZE

    The data pointed clearly at the evening shift as the primary driver of AHT failure. Evening shift agents averaged only 0.8 years of tenure compared to 2.3 years on the morning shift. Three evening agents had been hired within the last 60 days. Customer reported reasons for long calls included complex issues requiring escalation, agents placing customers on hold multiple times, and customers having to repeat information already provided. These three reasons pointed to gaps in troubleshooting depth, inefficient knowledge navigation, and documentation breakdowns respectively.

    IMPROVE

    Five targeted solutions were implemented. First, accelerated coaching for newer evening agents focused on call control and troubleshooting structure. Second, a standardized decision tree for the most common complex issue types. Third, improved access to internal knowledge resources to reduce unnecessary hold usage. Fourth, improved case documentation standards to eliminate customers repeating information. Fifth, temporary shift specific performance check ins until results stabilized.

    CONTROL

    Weekly AHT tracking by shift, tenure group, and individual agent was implemented. A control dashboard was created covering total interactions, defect rate, and escalation frequency with separate visibility into morning and evening performance. New hires were placed into a defined ramp plan with milestone reviews at 30, 60, and 90 days. Standard troubleshooting workflows were formalized and reinforced through team meetings. If defect rates rise again leadership intervenes immediately with targeted retraining.

    WHAT I LEARNED

    The most important thing this exercise taught me is that DMAIC does not just find problems. It finds where problems actually live versus where they appear to live. Without measuring shift level sigma separately the evening shift defect concentration would have been buried inside the overall team number. The data forced precision that instinct alone could not have produced.

    I also learned that DPMO is the honest unit of measurement because it removes volume bias entirely. The evening shift handled fewer calls but produced a defect rate more than three times higher than the morning shift. Raw numbers would have hidden that and DPMO corrected it.

    This is what Six Sigma actually does. It makes the invisible visible.

    Robert A. Reinhardt
    Independent Researcher
    ORCID: 0009-0007-6568-9784

  • Understanding the Inclusion-Exclusion Principle (Set Union Formula for Three-Set Functions)

    Formula: | A ∪ B ∪ C | = | A | + | B | + | C | – | A ∩ B | – | A ∩ C | – | B ∩ C | + | A ∩ B ∩ C |
    A represents Data Set A
    B represents Data Set B
    C represents Data Set C
    A ∪ B represents the overlapping data sets
    A ∩ C represents the overlapping data sets
    B ∩ C represents the overlapping data sets
    A ∩ B ∩ C represents the middle center overlapping data sets

  • Understanding the Inclusion-Exclusion Principle (Set Union Formula for Two-Set Functions)

    Fascinated by my vague attempt at performing the Practice GMAT (Score: 11/15), I found myself diving deeper into the Set Union Formula (Two-Set Function) and it’s revelance to the Venn Diagram. What’s important to note is that this formula helps when you need to compare two or more data sets from groups that overlap with each other. But I discovered that you’ll need to know three important things:

    • Know how many are in the group individually
    • How many are in both groups
    • Want to find how many are in either group or both

    Formula: | A ∪ B | = | A | + | B | – | A ∩ B |
    A represents Data Set A
    B represents Data Set B
    A υ B represents the total of both data sets
    A n B represents the overlapping data sets

    Learning Source: https://www.youtube.com/watch?v=YlKDp03Kg68