Arrow Electronics Case Study
Arrow Electronics is the fastest growing distributors of electronic components in North America and the world’s largest overall at the time of this study. Arrow’s capital structure policy is heavy on dependence on debt financing, which is sharp in contrast to its main rival, Avnet. CEO Stephen Kauffman is struggling with the implementation of an accurate and reliable way to evaluate his employees. Kauffman implemented an EPR (Employee Performance Review) system that was currently not providing him with enough information that he needed to determine the level of performance given to him by his employees.
Because of industry trends and compensation practices, the electronics distributors sales force is transitory. The industry has a high turnover in sales and usually when sales reps move to other companies they take their customers with them. For five years Arrow struggled with the accuracy and implementation of their EPR. Arrow saw problems ranging from inflated scores, ratings that reflected the self-serving bias of the managers who administered the appraisal, to lack of consistency. Kauffman decided to respond to these problems by providing training on how to scale, score and administer the appraisal.
Arrow Electronics Case Study Essay Example
He made video notifiying managers exactly what he wanted and set goals to what percentage of employees should score in every single one of the categories. When Kauffman received the results from managers he became frustrated because the results were skewed. A problem existed with how the appraisals were given, but the real problem lied with the appraisal itself. The EPR that Arrow was asked to use was asking the managers to evaluate their employees compared to one another, rather than comparing them to expected standards using behavioral targets.
The appraisal is worded in a way that each individual employee’s success is defined within the parameters of the success or failure of their coworkers. Because of this system, the appraisal was driving subjective feedback when Kauffman was looking for objective feedback. Building on this mishap, Kauffman’s system to evaluate his employees is used as a point in a field of data to determine an employee’s chance for promotion or termination. Kauffman states that he wants employees to understand that getting a low score is not punitive, but how would you respond if you received a low score?
Kauffman needs to find a way to keep Arrow salespeople with Arrow. One way of doing this would be to have employees appraise their work satisfaction and have management develop and implement a system that increases the employee’s satisfaction. Arrow had a couple key company objectives. Arrow wanted to eliminate long turnaround to answer RFPs, improve sales process by automating quotes, reduce pricing and inventory errors, and expand information capture capabilities.
Arrow Electronics was experiencing a competitive disadvantage because of long turnaround times on customer requests for product pricing and availability. Even though Arrow had a sophisticated quoting system, their customers submitted RFPs in multiple different formats such as Microsoft Word, Microsoft Access, Microsoft Excel, or CSV text file. Because of these different formats, this created turnaround and accuracy problems and required Arrow personnel to post data manually and prepare a response to the customer’s RFP.
The costly delays that resulted from this turnaround resulted in lost sales. Scheihing had described the poor shipping performance as resulting from a late day surge in orders hitting the PDCs in large quantities that it was not possible to pick and ship them by the last carrier pick-up. When Scheihing was the operations manager in the Philadelphia branch, she recalled that late orders just meant a little overtime in the warehouse and an early start in the morning for their driver.
With the closing of the local branch warehouses and the building of the four PDCs, the situation had changed. Scheihing needs to focus on what actions are needed to get the same day shipping performance back to 95%. One way of doing that would be to focus on pushing back the carrier pick up times, adding permanent full-time staff to handle the daily surges, and building a part-time staff to call in on short notice instead of only working more overtime. The Mainframe System that Arrow was using as a repository of all data and converted the orders received from the Sales Desktop to shipping
instructions for the appropriate PDC was experiencing some problems. One of the abilities the Mainframe System had was the ability to track inventory at very detailed levels. There existed five possible on-hand positions for inventory that had been put on the shelf or picked for an order. Scheihing once remarked that Arrow was “controlled by the IT System. ” Arrow was dependent on its systems and the information contained in them had to be accurate. Inaccurate inventory data has the potential to drastically affect Arrow’s performance.
Arrow tracked their inventory accuracy and if it experienced dings between 2-5% then it needed “turning up. ” Anything over 5% was a serious problem and would require a team from corporate to audit and suggest improvements. Sheihing believed that accurate data were central in such a way that failure to maintain data accurately resulted in managers being fired. Inaccurate inventory data could cause a trickle down affect that would negatively affect the way Arrow did business and portray them as someone who cannot be relied on as a successful business entity.