Institutions separate shared services from business units to control scale, cost, and risk without constraining execution. The distinction is structural, not administrative. In Organizational Strategy & Design, the shared services versus business units decision determines where authority is centralised, where accountability sits, and how value is delivered at speed without governance erosion. This is not an efficiency debate. It is a power allocation decision that shapes how the institution operates under growth, stress, and scrutiny.
What Shared Services and Business Units Are Designed to Do
Shared services exist to standardise, control, and scale. Business units exist to execute, compete, and deliver outcomes in defined markets. Confusing these mandates produces friction. Separating them correctly creates clarity. The operating model assigns each a distinct purpose, authority set, and performance logic.
Shared Services as Control Infrastructure
Shared services consolidate functions where consistency, compliance, and cost discipline matter. They enforce standards, protect the institution, and remove duplication. Their mandate is institutional, not commercial. Authority flows from governance, not revenue targets.
Business Units as Outcome Owners
Business units own market-facing outcomes. Revenue, client delivery, and operational performance sit with unit leadership. Authority is sufficient to execute within defined limits. Accountability is direct. Results are measured against commercial objectives and strategic priorities.
Functions That Belong in Shared Services
Not all functions qualify for shared services. Centralisation is justified where deviation creates risk or inefficiency.
Legal, Risk, and Compliance
Legal interpretation, risk management, and compliance standards centralise by default. These functions require independence from commercial pressure. Shared services ensure uniform application of policy, consistent escalation, and enforceable oversight across the institution.
Finance, Treasury, and Capital Control
Financial reporting, treasury, and capital allocation operate as shared services to protect balance sheet integrity. Capital approvals, cash management, and financial controls remain centralised to prevent leakage and inconsistency.
Core Technology and Data Governance
Infrastructure, cybersecurity, and data governance centralise to protect resilience and integrity. Shared services define standards and platforms. Business units consume services within approved architectures.
Procurement and Vendor Management
Procurement centralises to leverage scale, enforce controls, and manage supplier risk. Local execution occurs within centrally defined frameworks.
Functions That Belong in Business Units
Business units retain functions where proximity to market and execution speed determine outcomes.
Commercial and Client-Facing Operations
Sales, client delivery, and market operations sit within business units. Authority is localised to respond to market conditions. Performance is measured against revenue, margin, and service outcomes.
Operational Delivery
Operations that directly impact customer experience or product delivery remain embedded in business units. This preserves accountability and responsiveness.
Market-Specific Adaptation
Where regulatory, cultural, or competitive conditions vary materially, business units retain limited functional capability to adapt execution within institutional constraints.
Designing the Interface Between Shared Services and Business Units
The interface determines whether the model functions or fails. Ambiguity at this boundary creates delay and conflict.
Clear Service Mandates
Shared services operate under defined mandates. Scope, service levels, authority, and escalation are documented. Business units know what is provided, how decisions are made, and when escalation applies.
Decision Rights and Escalation
Decision ownership is explicit. Shared services decide on standards and controls. Business units decide on execution within those standards. Escalation triggers are predefined and enforced.
Performance Accountability on Both Sides
Shared services are accountable for quality, timeliness, and compliance. Business units are accountable for outcomes and utilisation. Performance metrics reflect these distinct responsibilities.
Hybrid Models and Selective Centralisation
Most institutions operate hybrid models. Discipline lies in intentional design.
Centralised Policy, Decentralised Execution
Policies, frameworks, and controls are centralised. Execution is decentralised. This preserves speed while maintaining institutional discipline.
Phased Centralisation During Growth
As organisations scale, functions migrate into shared services deliberately. Timing matters. Premature centralisation constrains growth. Delayed centralisation increases risk.
Reversibility Where Justified
In specific contexts, limited re-decentralisation may be justified to restore execution speed. These decisions are explicit and governed, not reactive.
Common Failure Patterns
Shared services models fail when discipline is compromised.
Shared Services Without Authority
Central functions lacking enforcement power become bottlenecks rather than controls.
Business Units Overriding Standards
Allowing local exceptions without governance erodes consistency and increases exposure.
Unclear Cost and Service Accountability
Opaque cost allocation and service expectations undermine trust and performance.
Conclusion
Shared services versus business units is a structural decision that defines how institutions balance control with execution. When designed intentionally, shared services protect the enterprise while business units deliver results at speed. Authority is clear. Accountability is enforced. Governance holds as scale increases. Where this balance is misdesigned, organisations oscillate between bureaucracy and fragmentation. Structural clarity determines which outcome prevails.
