Outsourcing at Office Supply Inc. Custom Case Solution & Analysis

Section 1: Evidence Brief

Financial Metrics

• Annual IT operating budget: 50 million dollars (Paragraph 2).
• Total projected savings from GSP proposal: 25 million dollars over a 10 year period (Exhibit 3).
• Annualized savings rate: 2.5 million dollars, representing a 5 percent reduction in annual IT spend (Exhibit 3).
• Total IT headcount: 150 full time equivalent employees (Paragraph 4).
• Capital expenditure requirements: 12 million dollars for hardware refresh if kept in-house (Exhibit 1).

Operational Facts

• Current IT structure: Centralized department managing infrastructure, desktop support, and proprietary supply chain software (Paragraph 5).
• Service scope: GSP proposal includes data center operations, network management, and help desk support (Paragraph 8).
• Personnel transfer: 150 OSI employees would transition to GSP payroll (Paragraph 10).
• Geography: Operations primarily serve the North American distribution network (Paragraph 1).

Stakeholder Positions

• David Marshall, Chief Information Officer: Expresses significant concern regarding the loss of institutional knowledge and the ability of an external vendor to respond to emergency supply chain disruptions (Paragraph 12).
• Chief Financial Officer: Views the proposal as a necessary step to shift fixed costs to variable costs and improve the balance sheet (Paragraph 14).
• Chief Executive Officer: Focused on meeting short term margin targets and reducing administrative overhead (Paragraph 3).
• IT Staff: High levels of anxiety regarding job security and benefits parity under GSP management (Paragraph 11).

Information Gaps

• Transition costs: The case does not detail the one time expenses associated with knowledge transfer or severance (Gap).
• Contract termination: No data on financial penalties if OSI chooses to end the GSP relationship early (Gap).
• Service Level Agreement penalties: Lack of clarity on financial recourse if GSP fails to meet uptime requirements (Gap).

Section 2: Strategic Analysis

Core Strategic Question

• Does the internal IT function provide a proprietary advantage in logistics and order fulfillment that justifies a 5 percent cost premium over an outsourced model?
• Can OSI manage the transition of 150 employees without triggering a catastrophic loss of operational knowledge?

Structural Analysis

The Core versus Context framework reveals that IT infrastructure is context, while supply chain logic is core. Infrastructure such as data centers and help desks are utility functions that do not differentiate OSI in the market. However, the proprietary software used to manage inventory and distribution is the engine of the business. Applying the Value Chain lens, the inbound and outbound logistics are the primary activities. IT serves as a support activity. If the support activity fails, the primary activities stop. The bargaining power of the supplier GSP will increase significantly once the 150 employees are transferred, as OSI will lose the internal capability to revert the decision.

Strategic Options

Option 1: Full Outsourcing to GSP. This path follows the current proposal. It captures the 25 million dollars in savings and removes 150 heads from the payroll. The trade-off is a total reliance on an external partner for every technical requirement. This requires a high level of trust in GSP and a legal framework that OSI currently lacks.

Option 2: Selective Outsourcing. This involves outsourcing commodity infrastructure like data centers and help desks while retaining the application development team. This path protects the core supply chain logic while reducing the burden of hardware management. The resource requirement includes a specialized vendor management office to oversee the contract.

Option 3: Internal IT Transformation. OSI could reorganize the internal team to match GSP efficiency. This avoids the risk of knowledge loss but requires an upfront investment in automation. This path is the most conservative and least likely to meet the immediate cost reduction targets of the CEO.

Preliminary Recommendation

OSI should pursue Selective Outsourcing. The company must retain the 40 employees who manage the proprietary supply chain software. The remaining 110 infrastructure and support roles should be transitioned to GSP. This strategy captures roughly 60 percent of the projected savings while maintaining control over the logic that drives the distribution network. It mitigates the risk of total vendor lock-in and ensures that emergency responses remain under the direct control of the CIO.

Section 3: Implementation Roadmap

Critical Path

The implementation must follow a phased approach to prevent operational paralysis. The first 30 days must focus on the creation of the Vendor Management Office. This team will define the metrics and penalties for the contract. Between day 31 and day 90, the team must conduct a comprehensive knowledge audit. Every process managed by the 150 employees must be documented. The actual transition of staff should occur in waves, starting with help desk functions, followed by data center operations, and finally network management. The proprietary software team will be formally carved out and exempted from the transfer to ensure continuity of the core business logic.

Key Constraints

• Talent Retention: The most skilled engineers are likely to leave during the transition. OSI must offer retention bonuses for the 90 day knowledge transfer period.
• Operational Friction: GSP will use standardized processes that may not align with the custom requirements of the OSI distribution centers. This will create delays in ticket resolution during the first six months.
• Contractual Rigidity: The 10 year term is too long for a volatile technology market. The contract must include a 3 year review clause.

Risk-Adjusted Implementation Strategy

To account for potential service drops, OSI must maintain a shadow team of 10 senior engineers for the first year. These individuals will act as a bridge between GSP and the business units. A contingency fund of 3 million dollars should be set aside to cover the cost of this shadow team and any unforeseen transition expenses. Success will be measured not by the reduction in headcount, but by the stability of the order fulfillment system. If system uptime drops below 99.9 percent during the transition, the next phase of the rollout will be paused until the vendor resolves the underlying issues.

Section 4: Executive Review

BLUF

Reject the full outsourcing proposal from GSP. The projected savings of 2.5 million dollars annually are insufficient to justify the high risk of operational failure in the supply chain. A 5 percent reduction in IT spend does not compensate for the loss of institutional knowledge and the creation of a single point of failure within the distribution network. OSI should adopt a selective outsourcing model, retaining core software development while offloading commodity infrastructure. This protects the competitive advantage of the company while still addressing the cost reduction mandates of the board.

Dangerous Assumption

The analysis assumes that GSP can maintain the current level of service with the same staff at a lower cost. This ignores the profit margin GSP must extract. The efficiency gains required to cover the GSP margin and the OSI savings are likely to come from reduced service quality or deferred maintenance, which will eventually manifest as system downtime.

Unaddressed Risks

• Knowledge Decay: Probability High, Consequence High. Once the 150 employees move to GSP, their loyalty shifts. Within two years, the unique understanding of the OSI legacy systems will be lost to the vendor, making any future transition to a different provider or back to internal management impossible.
• Contractual Lock-in: Probability High, Consequence Medium. A 10 year contract in the IT sector is an eternity. OSI risks being tied to obsolete technology and pricing structures while the market moves toward more efficient cloud based alternatives.

Unconsidered Alternative

The team failed to consider a cloud migration strategy as an alternative to outsourcing. By moving infrastructure to a public cloud provider, OSI could achieve the desired cost variability and hardware reduction without transferring its entire workforce to a third party service provider. This would allow for a more modern architecture while retaining the talent that understands the business.

Verdict

REQUIRES REVISION

The Strategic Analyst must provide a detailed comparison of the Selective Outsourcing model against a Cloud Migration model. The financial projections must be updated to include the costs of a Vendor Management Office and the 10 percent increase in management overhead that always accompanies large scale outsourcing contracts. The analysis must be mutually exclusive and collectively exhaustive regarding the IT cost categories.