When Shared Services Strengthen a Portfolio—and When They Slow It Down
Centralize leverage, not every decision.
Shared services can give a portfolio access to capabilities that individual companies could not justify alone. Finance, legal, talent, data, technology, procurement, and brand systems can all become sources of leverage. But centralization can also add queues, distance decisions from customers, and make operating companies less accountable for their own performance.
The question is not whether a function can be centralized. It is whether centralization improves the portfolio’s total speed, quality, control, or economics.
Centralize repeated expertise
Shared services work best when the need is common across companies and the capability improves through scale. Examples may include baseline security, financial controls, vendor management, leadership development, or technical infrastructure. A shared team can establish standards, retain specialized knowledge, and reduce duplicated effort.
The service should have a clear product mindset. Operating companies need to know what is available, how to request it, how priorities are set, and what level of service to expect. Without that clarity, “shared” often means informal dependence on a small central team.
Keep market judgment close to the customer
Decisions that depend heavily on customer context usually belong within the operating company. Positioning, sales conversations, delivery tradeoffs, and product priorities require proximity to the market. Central teams can provide tools and standards, but they should be cautious about substituting portfolio-wide consistency for local understanding.
A useful rule is to centralize capability while distributing application. The parent may provide a common data standard; the operating company decides which customer signals require action. The parent may create brand governance; the company communicates in a voice appropriate to its audience.
Measure friction as well as savings
Shared services are often justified by cost savings, but the hidden cost is delay. A cheaper process that causes teams to wait, re-explain context, or miss opportunities may not be efficient at the portfolio level.
Review shared services through four lenses:
- Quality: Does the service improve the standard of work?
- Speed: Does it reduce or create decision latency?
- Economics: Are real costs lower after coordination is included?
- Accountability: Is it clear who owns the outcome?
The wider view
The goal of shared services is not maximum centralization. It is maximum useful leverage. Strong portfolio operations centralize expertise, infrastructure, and controls where scale matters, while preserving the autonomy required for customer responsiveness. The center should make operating companies more capable—not more dependent.
