Transform Home Transform Aviation Transform Healthcare Transform Services Transform TechnologyGovernment

Transform

200 Westpark Drive

Suite 310

Peachtree City, GA 30269

 

Phone

770.631.3826

Facsimile

770.631.3794

E-mail

info@321transform.com

 

transform


AviationdividerHealthcaredividerServicesdividerTechnologydividerGovernment

White Papers.

 

Driving Process Improvement in Shared Services Implementation

(October 2008) Transform

The Shared Services Model

The purpose of the shared services model is to consolidate redundant operations within the global enterprise. As the enterprise grows through organic growth or acquisition, so does the supporting infrastructure. Consolidation of those redundancies into a shared services model drives cost out of the organization (frequently as head count) and improves the delivery of specific services to the organization.

The term “internal sourcing” best describes the objectives of shared services. However, some elements of shared services may also include outsourcing. For example, while an enterprise maintains control of over Human Resources (HR) operations as a whole, it may outsource recruitment to take advantage of specific technology available in the marketplace. Candidates are presented to HR when they have been vetted and tested. The standard interview and hiring processes begin at that point but the cycle time for the selection is significantly streamlined.

The most familiar shared service is Information Technology (IT). Every division and individual within the enterprise is touched by IT. Sustainable growth is dependent upon the consistent delivery of data and the implementation of next generation technology. For the high-technology enterprise, IT is its lifeblood.

Beginning in the early 1980’s and accelerating through today, IT operations have proven the viability of the shared services model.

IT operations have and are continuing to move back into the traditional Data Center paradigm, although what was once a “raised floor”, “heavy iron” (mainframe) environment is now populated by racks of servers and storage “farms” set in a secured and (frequently) hardened facility. Although there are technical teams in the field providing localized support, they do so through shared services.

Beyond IT, all of the following are candidates for shared services:

  • Accounting and Finance
  • Human Resources
  • Procurement & Purchasing
  • Facilities and Environment
  • Legal and Tax
  • Logistics and Supply Chain
  • Marketing and Sales (may be limited by product and geography)

Shared Services - The Ideal

The objective of shared services is to improve the financial performance of the corporation.

Shared services drive internal providers to leverage economies of scale and improve efficiencies through common, standardized processes and methodologies.

Frequently, the enterprise will reevaluate and refocus its core business operational methodology to include shared services. Also, more than one shared services entity may exist within the enterprise.

Shared services enable affected business units to shift focus from non revenue- producing activities to core revenue- producing activities. Affected business units focus on core-support areas while shared services accepts responsibility and accountability for the non-core areas. This is not to say that “non-core” equates to non-essential. The reverse is true. For example, “incorporating” accounting functionality into shared services enables greater control over those mission critical activities. But it does so without the oversight necessary to bring multiple divisions into compliance.

Shared services improve the overall responsiveness of the organization to change. It frequently acts as a change agent (for example, IT driving new technology throughout the organization) or it can act as a cost center for a specific functionality (for example Procurement and Purchasing).

Shared Services - The Reality

There is frequently resistance to the conception, inception and acceptance of a shared services entity within the enterprise. Perhaps the best example is the Program Management Office (PMO) that was accountable for the planning and execution of major IT initiatives within the enterprise. PMOs proliferated through the 1990s with varying degrees of success. However, many encountered heavy resistance from the internal constituencies because of inadequate preparation on the part of the planners and a lack of a clearly defined pathway for acceptance (and use) by those constituencies.

Resistance to change is common in every organization – because change requires stepping or leaping into the unknown. Even though non-core services can be clearly identified, there is still resistance to moving those services and consolidating them into a single new entity. If real or perceived head count reduction is involved, the resistance will be even stronger and more apparent. The best way to overcome this resistance is to plan for it and to drive acceptance from the executive level downwards.

Shared Services - Operations

Shared services are designed to function as a separate business unit within the enterprise. They “own” certain functionality of the organization and bill back to the constituencies utilizing their services.

Shared services are designed to break even – to bill for products delivered or services rendered and to collect payment from the budgets of constituent divisions. For example, a global organization provides logistics support to the manufacturing divisions within the organization. That support is based upon a reverse auction process and tracking and billing technology owned and maintained by the shared services office (or division, etc.). Every manufacturing and support division that ships products or supplies to corporate customers is required by executive mandate to utilize shared services. With centralized control, the enterprise realizes a transportation cost savings of over $240,000 per week.

Operationally the commitment to shared services includes a commitment from the executive leadership to:

  • Create the shared services division (or divisions); and
  • Put in place all of the technology necessary to support the division; and
  • Expend the political capital necessary to drive acceptance of the division.

In the above example, the CEO of the enterprise personally mentored the shared services project and expended his personal (“rock-star-type”) political capital to drive acceptance throughout the enterprise.

Shared services maintained a visual dashboard that tracked the success of the reverse auction process and the resulting cost savings for each internal customer. Post implementation surveys of both internal (the shipper) customers indicated greater acceptance of shared services as the reverse auction took hold and costs were brought under greater control. A similar survey of external customers (the receiver) indicated improved adherence to delivery terms and timetable by the enterprise and a corresponding reduction in the penalties levied for shipment delays. Both internal and external customers appreciate saving money.

The successful implementation of a shared services initiative requires clearly defined objectives, goals and the processes necessary to control the initiative from start to “Go Live”. Without following an orderly pathway for success:

  • The initiative runs the risk of outright failure. Causation will be failure to adequately plan and control and resistance to change.
  • Partial success that eventually reverts to failure – Other divisions will retain a portion of the core functionality that should be part of shared services. A “shared control” paradigm leads to further conflict between shared services and the “rogue” division(s). Cost will not be driven out of the organization because the enterprise will not be able to adequately and fully leverage one of its greatest assets – the enterprise itself – to manage vendor relationships. Consolidation enables the global enterprise to leverage real power in the marketplace.
    • The financial underpinnings of shared services must be clearly defined and supported by adequate technology.
    • Financial “housekeeping” must be airtight and regulatory compliant. This is critical if shared services are to successfully handle transactions for the enterprise.
    • Service level agreements (SLAs) must be clearly defined and in place between shared services and all internal customers.
    • If shared services touch external customers, adherence to sales terms must be monitored for compliance (frequently in cooperation with legal). It is important to note that the delivery contract is between the enterprise and the client, and the enterprise pays for adherence failures through penalties that may accrue on a daily basis.

Shared Services - Critical Factors

An enterprise focused on the following critical factors will have a greater opportunity for success when implementing a shared services model:

  • Products and Services: Both are clearly defined and targeted performance levels are clearly communicated to the constituencies.
  • Customer: Products and services are specifically designed to meet the business needs of the internal customer. The aforementioned SLAs establish demand forecasts and help set relationship expectations.
  • Fulfillment: A process and delivery model is clearly defined. Included within fulfillment are responsiveness and efficiency processes (and metrics), backed by an appropriate order fulfillment processing and tracking mechanisms.
  • Finance and Cost Management: Shared services must understand the cost structure and be prepared to internally market products and services lines. Pricing is accomplished through consistency with the existing cost structure and market information. Organizations are electronically invoiced for the products and services which they actually use.
  • Strategies, Principles, and Policies: Shared services are a strategic initiative, initiated and driven by the executive team. The organization is process driven, with a clear mandate for success. Both the underlying (strategic) principles of the enterprise and the (tactical) mandate for shared services drive the business. Both financial and operational performance is monitored by the executive team or executive champion.
  • Processes: Customer (internal and external) interfaces, vendor management and operations are driven by clear and unambiguous processes. As a provider, shared services maintain an SLA with each internal customer and are held to the performance levels specified in the SLA.
  • Metrics: For every action there is a reaction – and there is a metric for every process. “Best Practices” are linked to processes within shared services and performance metrics are shared with internal and external customers on an as-needed basis.

Shared Services - Migration

The shared services business model requires rethinking of the typical business paradigm. Instead of divisions that “do everything”, the enterprise transforms itself into a business that is more mission and core-revenue-producing focused.

Shared services provide support to those divisions while improving cost containment and quality improvement for the specific mission-critical functionality owned by shared services.

For enterprises with multiple business units or frequent acquisitions, the shared services model provides improved financial oversight and cost reduction for the enterprise. In fact, shared services can actually drive the acquisition process.

Summary

The executive vision for shared services is clearly defined and communicated throughout the enterprise. That is by far the most critical “first step.”

Alteration or creation of processes and procedures for shared services is the second step.

Realignment of hard-core functionality from outliers to shared services (i.e., plant, equipment, tools, existing SLAs, etc.) follows once the physical entity known as shared services comes into existence.

Finally, action plans must be communicated from shared services to the constituent divisions. This is both an informational exercise and also a degree of “hand holding” until high acceptance levels are measured. It is important to differentiate between mandated and accepted. Mandates frequently generate resistance. Acceptance planning overcomes that resistance.

Below are the key steps necessary in building shared services within the enterprise. This is by no means a comprehensive or exhaustive list and both strategic and tactical planning will enable the enterprise to clearly define shared services functionality:

  1. The functionality to be incorporated into the shared services model is clearly defined.
  2. A clear direction is set by the executive team and implemented by the (to be) shared services team.
  3. Action plans are communicated vertically and laterally.
  4. Products and services to be included in the shared services model are clearly defined, as are the pathways to “customized” products or services.
  5. A customer service strategy is built and implemented. As salespersons, vendors tend to revert to known individuals when confronted by a vendor management project that is “new” or “strict”. An “end-around” to bypass shared services cannot be permitted or tolerated.
  6. Critical cost containment and reduction strategies are identified and “owned” by shared services.
  7. Vendor and/or supplier strategies are linked to process improvements
  8. Sourcing principles and strategy are clearly defined and communicated to the constituencies.

 

This white paper is made available to you with the compliments of Transform.
© 2008 321Transform LLC. Transform Healthcare LLC. All rights reserved.

Home | Contact Us

Copyright © 2010 Transform LLC. All rights reserved. Terms & Conditions