IBM Credit Case Study: Operational Inefficiencies and Solutions

Discussion contrasts two systems: Schuldice Hospital (efficient) vs. IBM Credit (inefficient).
Schuldice excels in suppressing variability leading to a focused production process.
IBM Credit suffers operational inefficiencies and customer delays due to variability.

The main issue at IBM Credit is the long delays customers face when seeking credit approvals.
Key points regarding their operations:
- Salespeople sell IBM systems with financing options through IBM credit, aiming for a lucrative business model.
- Long delays lead customers to seek credit alternatives or not purchase at all.

Step 1: An IBM salesperson logs a call for financing at a desk in Greenwich, Connecticut.
- Information is recorded on paper.

Step 2: Logged calls are delivered to the credit department.
- A credit specialist uses a computer to evaluate the applicant's creditworthiness.
- The outcome is documented on paper and forwarded to the business practices department.

Step 3: The business practices department checks if loan terms require variations from standard covenants.
- Adjustments are made using their system.

Step 4: A price specialist enters details into a spreadsheet to determine the interest rate.
- This information is also documented on paper and included in the loan packet to be sent to the customer via FedEx.

Information primarily recorded on paper leads to multiple re-entries and errors.
Inefficient communication and data flow between departments due to reliance on traditional methods.
Equal attention to several issues:
- Delays: Up to 14 days, average 6 days for loan approvals.
- Control Desk Implementation: Attempts to enhance transparency did not reduce average processing time.
- Managers conducted a hands-on assessment revealing the application process can take only 90 minutes when observed but typically took much longer due to inefficiencies.

Batching calls for credit checks introduces delays.
Variability in processing times and queuing across departments.
Capacity imbalances between operational stages lead to bottlenecks.
Insufficient scheduling and too many handoffs slow progress.
Non-value-adding time increases significantly; actual processing (value-added) is relatively minor.

IBM Credit replaces the specialist model with a generalist approach.
- Generalists are cross-trained to handle multiple tasks (logging, credit checks, pricing).
- This eliminates delays between process stages as one individual manages the application from start to finish.

Reduction in process delays as tasks flow seamlessly from one step to the next without batching.
Increased ownership and accountability of tasks amongst generalists leads to better problem resolution.
When generalists are idle, tasks can be processed immediately, preventing queues.
Resulting improvements:
- Flow time reduced from 6 days to 4 days.
- Throughput increased one hundredfold.
- Introduction of a unified computer system reduced data re-entry errors.

The case of IBM Credit illustrates significant operational variability versus the low variability seen in the Schuldice Hospital model.
Future discussions will delve deeper into managing such variability effectively in operational systems.