We are trying to apply the Plan-Do-Check-Act (PDCA) cycle to our customer support desk to reduce ticket resolution times. What are some real-world examples of the 'Check' and 'Act' phases in a service-oriented environment rather than a manufacturing one?
3 answers
In a service desk, the 'Check' phase involves analyzing the data from your 'Do' phase—like CSAT scores and Average Handle Time. For instance, if you implemented a new chatbot (Do), you 'Check' by seeing if it actually reduced the number of live agent transfers. The 'Act' phase is then deciding whether to roll that chatbot out to all regions or tweak its script based on the gaps identified. It’s a literal loop; if the results weren't what you planned, you start the cycle again with a new hypothesis. This constant iteration ensures that your service quality never stagnates.
How are you ensuring that the frontline agents are actually involved in the 'Plan' phase, or is the strategy coming strictly from upper management?
Don't forget the 'Check' should also include qualitative feedback. Metrics are great, but reading the actual customer comments tells the real story of the improvement.
I agree, Patricia. A low resolution time is useless if the customer feels the agent was rude. Quality must be holistic, covering both speed and sentiment.
Gregory, that’s a vital point. We’ve started weekly "Pain Point" sessions where agents suggest the 'Plan' items. Since they are the ones talking to customers daily, their insights into what needs fixing are far more accurate than what the data alone tells us managers.