6.1: Putting It Together- Organizational Structures
Back to IBM Credit Corporation
Let’s return to our case study of IBM’s credit arm that we considered at the outset of this module. You’ll recall that credit applications could take six days to several weeks to be processed, during which time sales were being lost to competitors. So what did IBM do?
Two senior managers with the company decided to follow a credit application throughout the entire process. When they did, they were surprised to discover that the actual processing time for each application was only ninety minutes! It quickly became evident that the delays were not a result of the amount of work that needed to be completed. Instead, it was a function of the structure the company had implemented. Each step in the approval process was routed to a different specialist to be completed.
- Step 1: Central office operator receives a finance request from a salesperson and records it on an input form → form is routed to the credit department
- Step 2: Credit specialist reviews the customer and makes a credit decision → result is recorded on the form, which is routed to the business practices department
- Step 3: Business practices approves any customer-requested changes to the standard loan covenants → changes are noted on the form and it is sent to the pricing department
- Step 4: Pricing specialist determines the appropriate rate to charge based on the customer’s credit and specific loan covenants → form moves to the administration department
- Step 5: Administration specialist turns all information recorded on the form into a quote letter → quote letter is routed to the sales specialist for delivery to the customer
Based on what you learned in this module, how would you describe IBM Credit’s organizational structure? Thinking back to Schein’s four key elements of an organization, where do you see opportunities for improvement?
- Common Purpose – Do the specialists understand their role in the overall purpose of the credit arm’s goal to support the sale of IBM computers, software, and equipment?
- Coordinated Effort – Has management coordinated the effort of work in a way that best adds value to the organization?
- Specialization and Division of Labor – Has management broken down the tasks into optimum sizes to allow maximum efficiency?
- Hierarchy of Authority – Is the optimal reporting structure in place?
In the end, the company realized that it had done a poor job of coordinating the efforts of the organization. Although each of the specialists was working hard, the structure did not support the overall goal of maximizing IBM Corp’s sales. In fact, the problem was based on an erroneous assumption that every request that was received was unique and difficult. In reality, the majority of credit requests were straightforward and easy to process. It generally did not require someone with the in-depth knowledge of a specialist. The organization had divided the labor too narrowly.
The company changed its structure, and instead of using specialists, it assigned generalists trained to handle a standard credit request. They would own the request from start to finish and would only engage the help of a specialist if the situation was more complex than they could handle. The result? The new turnaround time was closer to four hours compared with six days or weeks!
This example clearly illustrates the need for managers to carefully analyze their organizational structure to ensure that it is capable of delivering the desired results.
Contributors and Attributions
- Putting It Together: Organizational Structures. Authored by : Jeff Heflin and Lumen Learning. License : CC BY: Attribution
- IBM. Authored by : Michael Cote. Located at : https://www.flickr.com/photos/cote/4709133844/ . License : CC BY: Attribution