top of page

 
Discover the root of the issue
People often notice the surface features of a problem and address those surface issues, allowing the root problem to fester. However, to effectively solve a problem you must invest extra time to discover and address the source of the problem. This is precisely what I had to do as a Sales Representative when working with customers' whose transitions over to UPS had not been as seamless as they hoped it would be. Once, I converted a large customer over to UPS from FedEx, but for some reason, he had not been experiencing pick-ups at the time that I negotiated with him. As a result, he was threatening to divert business from UPS to FedEx. At first, the customer insisted on getting a refund for the missed pickups. But money was not the issue here. The true problem was that he was missing pickups on a regular basis. To resolve this issue, I spent time speaking with our Operations Center to determine what we needed to do to prevent this issue from reoccurring. Ultimately, we settled on adjusting the time frame, which satisfied the customer. Taking the time out to resolve the root problem took more time, but it was the more efficient and effective way of providing good customer service that minimized the amount of time that I was handling the same issue for the same customer. Further, it minimized the amount of time that the customer spent calling around UPS' large corporation to try to resolve this issue. 
 

Introduction 

When I worked as a Sales Representative, part of my job was  to ensure customers are satisfied with UPS' service, thereby minimizing the amount of diversion experienced. The customer service aspect of this job required me to improve my problem-solving skills so that I could excel in my role. During my tenure at UPS, I learned effective problem solving involves 1) discovering the root of the issue, 2) determining whether the solution implemented addressed the root and symptomatic issues, and 3) evaluating personal processes to improve personal performance and minimize the occurrence of the problem in the future problems. My experience has taught me this is a more efficient and effective way to resolve a problem.

Determine whether the solution implemented addressed problem

Implementing a solution is not enough. You must also determine whether the solution implemented was the most appropriate solution to resolve the problem. When I spoke with the Operations Center, I realized the customer's desired pickup (4:00 PM) had a 30-minute window before and after that time frame. Therefore, the time frame originally arranged may not have been the best time frame for the customer's business model. After speaking with the Center Manager, I spoke with the customer and we determined that a 3:30 PM window may be more conducive to his business model. Once the window was adjusted, I set aside time each day at 4:00 PM for the following three days to check with the Center to ensure that a driver was on his/her way at the appropriate time. Furthermore, I also confirmed with the customer he was getting his pickups at the appropriate time. As a result, the customer felt pleased with UPS' services and was happy that I took the time to resolve this issue for him. Determining the time frame we put in place was not the most appropriate time frame, helped me resolve this issue in a way that minimized the amount of time I was not making sales and ensured my customer was pleased with his UPS services.  

 

Evaluate personal processes to improve future performance 

Finally, I learned self-evaluation is critical in preventing problems from reoccurring. Because the UPS drivers normally came at the requested time, I realized I had not been notifying customers about the 30-minute window. From my experience with the drivers, they had been fairly consistent about pickups and drop offs, and I estimated the probability a driver would come thirty minutes earlier or later as low. I conflated a low probability with no chance the driver would arrive thirty minutes earlier or later. Thus, I was not informing customers about the 30-minute window. Moving forward, I made sure to inform new and current customers, if their shipments must go out that day, the shipments  need to be prepared at least thirty minutes before the pickup time and the driver may come up to thirty minutes after the pickup time. This helped me manage customers' expectations, discuss whether the pickup time they are setting is really appropriate for their business model, and ensure I put a pickup time in place that fits their circumstances. By evaluating my processes for discussing pickup times, I was able to effectively mitigate encountering this issue in the future.  

 

Conclusion

Although it can be tempting and seem efficient to attempt to address the symptoms of a problem, I realized it is worth the extra time to determine the root of the problem and resolve that root issue.  I have also learned to  evaluate the solutions I have put in place to see if they actually addressed the source of a problem. If not, it indicates the problem may have simply been patched. Finally, I have found that it is important to evaluate and streamline personal processes to mitigate the recurrence of a problem. Although this process may seem time-consuming, it is the more efficient and effective way to solve a problem.

Problem Solving

Teammate and I with Call Quality Award
Call Quality Award

Connect with Marlisa

Proudly created with Wix.com
 

  • Twitter Social Icon
  • LinkedIn Social Icon
  • Facebook Social Icon
bottom of page