In the majority of the audit forms that I have witnessed thus far, I have rarely seen any efficiency metric being included in the audit form. Our audit forms are normally used to check compliance to Customer Service Guidelines (CSAT requirements), Process guidelines, Client instructions and language accuracies. There is seldom a parameter in the audit form which objectively scrutinizes the efficiency of the transaction. This results in either the quality department or the operations team taking up additional projects to improve productivity.
In my opinion, being lean and efficient is a continual goal rather than a once-in-a-while attempt to meet targets when the productivity targets are not being met. In order to cultivate the culture of continually improving the efficiency of the project, it must be inculcated into an activity which is continually being performed and that activity is Transaction Monitoring.
So the question arises, how do we improve productivity using the transaction monitoring process. The answer is pretty simple – turn your transaction monitoring into a mini time & motion study. It would require you to draw a process map for each and every type of transaction that an agent handles, find the optimum time required to complete each of those process steps and arrive at an optimum time to handle the entire transaction.
After this exercise of baselining is complete and you know the optimum time required to complete almost all types of transactions, you will train your QAs on this process map along with the time required to perform each step in the process map and have them compare the transactions they are auditing with the process map that was baselined for optimum performance. When the QAs perform the comparative audit, they will be able to find the redundancies in the transactions. We can then classify these redundancies into controllable and non-controllable redundancies. For example: An agent wasting time due to lack of knowledge or placing the customer on hold without any reason or the agent’s system facing latency issues – each of these can be classified as a controllable redundancy. However, in the event that a Customer places the agent on hold for a reason, it can be classified as a non-controllable redundancy.
The data from the audit can be used to:
1. Impart feedback to the agent on improving their individual efficiencies
2. Analyze and derive action plans at process level by finding areas of high redundancies (Pareto) and then making changes to the training/refreshers
3. Keep better control on time spent on each parameter using control charts
4. Reduce variation amongst agents on different steps in the process map
5. Use the data for Bottom Quartile Management
Once the process is setup, you will not need to look at any other source to find root causes for low productivity. You will have the most relevant and up to date data for analysis and taking actions on a continuous basis without wasting any time or using up additional resources. This simple exercise can pay rich dividends in terms of cost savings and improving the financial health of the project.
I hope you will find this article to be informative and hopefully, you will use it to become more competitive and profitable in the marketplace.
Earn upto Rs. 9,000 pm checking Emails. Join now!