Head of Shared Services Guide: Shared Services & GBS

The Friction Points.

The 'Black Box' of Service Delivery

One of the most pervasive challenges facing GBS leaders in 2025 is the 'Black Box' syndrome. Despite millions invested in ERPs and point solutions, the actual intake of work often remains unstructured. Research indicates that in many mature GBS organizations, up to 40% of service requests still bypass formal ticketing systems, arriving via email, chat, or 'shoulder taps.' This creates an invisible workload that cannot be measured, optimized, or automated. When you cannot see the demand, you cannot resource it effectively, leading to burnout and missed SLAs. The business impact is severe: without data on volume and complexity, GBS leaders cannot defend their headcount or prove the unit cost of delivery, perpetuating the perception of GBS as a cost center rather than a strategic partner.

The Regional Divergence Dilemma

A critical failure point in global delivery models is the lack of process standardization across geographies. It is common for a 'Procure-to-Pay' process in a Manila center to operate on entirely different workflows and documentation standards than its counterpart in Krakow or Costa Rica. This divergence is often justified by 'local regulatory nuances,' but deep analysis usually reveals that 80% of the variance is cultural, not legal. This fragmentation prevents the deployment of global automation initiatives. You cannot apply a single RPA bot or GenAI solution to five different variations of the same invoice processing workflow. The result is a bloated tech stack and an inability to leverage economies of scale, costing organizations millions in lost efficiency annually.

The Talent & Retention Crisis (Gen Z Factor)

The traditional GBS talent model—hiring fresh graduates for transactional roles—is breaking down. With 84% of executives expecting Gen Z recruits to leave within three years, the cost of turnover is eroding the arbitrage benefits of low-cost centers. The challenge is twofold: first, the work itself (manual data entry, ticket routing) is unappealing to digital natives; second, the lack of clear career pathing within GBS structures makes retention difficult. In APAC and Eastern Europe, where competition for talent is fierce, wage inflation is rapidly closing the gap with source markets. GBS leaders are finding that they are constantly recruiting to stand still, with institutional knowledge walking out the door every 18 months.

The Value Perception Gap

Perhaps the most existential threat is the disconnect between GBS performance metrics and business outcomes. GBS leaders often report 'green' dashboards showing 99% SLA adherence (e.g., 'ticket closed in 4 hours'), while the business unit is frustrated because the underlying outcome (e.g., 'vendor paid on time') wasn't achieved. This metric misalignment creates a 'watermelon effect'—green on the outside (GBS reports), but red on the inside (business sentiment). When business partners do not see the ROI, they resist scope expansion and push back on chargeback models. In North America, where labor costs are highest, this scrutiny is intense; business units demand to know exactly what they are paying for, and 'allocated costs' without granular usage data are no longer acceptable.

A Smarter Operating System.

Phase 1: The Unified Intake Model (The 'Front Door')

The first step to solving the transparency crisis is closing the side doors. You must channel all requests—whether for HR, Finance, or IT—through a unified engagement layer. This does not mean forcing users into clunky forms; it means deploying multi-channel intake (Teams/Slack integration, email parsing, portal) that feeds a single orchestration engine.

• Action: Implement an 'Intake-to-Resolution' platform.

• The Mechanism: When a request arrives, AI triage should immediately categorize it, assign a complexity tier (Tier 0 for self-service, Tier 1 for basic, Tier 3 for expert), and route it to the correct queue.

• The Benefit: This generates the 'missing data' on demand patterns. You can finally see who is requesting what, when, and at what volume.

Phase 2: The Global Process Council & Standardization

To tackle regional divergence, establish a Global Process Council (GPC) with voting members from each tower (Finance, HR, IT) and region (NA, EMEA, APAC).

• Decision Tree:

• Is the process variance legally required? (e.g., GDPR in Europe, e-invoicing in Brazil).

• If YES: Configure a 'local compliance layer' on top of the global standard.

• If NO: Mandate the global standard workflow. Eliminate the variance.

• Strategy: Adopt a 'Global Design, Local Configure' mindset. The core process (80%) is fixed; the local configuration (20%) is flexible only for regulatory needs.

Phase 3: Outcome-Based Scorecards

Shift your reporting from 'Activity' to 'Outcome.' Stop reporting on 'Tickets Closed' and start reporting on 'Business Value Delivered.'

• Finance Example: Instead of 'Invoices Processed,' report on 'Working Capital Optimization' or 'Early Payment Discounts Captured.'

• HR Example: Instead of 'Queries Answered,' report on 'Time-to-Productivity for New Hires.'

• Framework: Implement the GBS Value Pyramid:

1. Base: Operational Efficiency (Cost/SLA).

2. Middle: Experience (NPS/Ease of Use).

3. Peak: Strategic Impact (Cash flow, Risk reduction, Revenue enablement).

Phase 4: The Automation Factory

Use the data from your Unified Intake to drive your automation backlog. Don't automate based on intuition; automate based on volume and friction data.

• Approach: Identify the 'Top 10 High-Volume, Low-Complexity' request types from your intake data.

• Execution: Deploy GenAI agents or RPA bots to handle these specific tasks (Tier 0).

• Talent Link: Upskill your Gen Z workforce to become 'Automation Supervisors' who manage the bots, rather than doing the data entry. This solves the retention issue by offering higher-value work.

Implementation Guide

Month 1-3: Discovery & The 'Front Door' Pilot

• Goal: Stop the bleeding of invisible work.

• Action: Select one function (e.g., Accounts Payable or IT Helpdesk) and implement a unified intake pilot. Shut down the shared email inboxes for this function.

• Team: Project Lead, Process Owner, IT Integration Lead.

• KPI: % of requests capturing structured data vs. free text.

Month 3-6: Baseline & Process Mining

• Goal: Establish the truth of current performance.

• Action: Run process mining software (or manual mapping) on the data collected from the pilot. Identify the 'Happy Path' vs. the exceptions.

• Deliverable: A 'Service Catalog' defining exactly what GBS offers, the SLA for each service, and the cost per unit.

• Regional Sync: Hold the first Global Process Council summit to agree on the 'Standard Process' for the next wave of migration.

Month 6-12: Scale & Automation

• Goal: Efficiency and Value realization.

• Action: Roll out the intake model to remaining towers. Begin the 'Automation Factory' sprints to automate the top 10 high-volume requests identified in the pilot.

• Pitfall to Avoid: The 'Big Bang' rollout. Do not try to migrate all regions and towers simultaneously. Go Tower by Tower, or Region by Region.

• Success Metric: Reduction in 'Cost Per Transaction' and increase in 'Touchless Processing Rate.'

Regional Intelligence.

North America (The Innovation Hub)

• Market Context: High labor costs drive a focus on high-value, judgment-based work. NA centers are increasingly becoming 'Centers of Expertise' (CoEs) rather than transaction hubs.

• Nearshoring Trend: There is a massive shift from APAC outsourcing back to LATAM (Costa Rica, Mexico, Colombia) for NA time-zone alignment. This 'nearshoring' enables real-time collaboration.

• Tactical Advice: In NA, focus on 'Business Partnering' roles. The staff here should be the face of GBS to the business, translating needs into requirements for the delivery centers.

Europe (The Compliance Labyrinth)

• Regulatory Environment: GDPR is the baseline, but local Works Councils (especially in Germany and France) heavily influence GBS changes. Moving roles or implementing monitoring software requires early engagement with employee representatives.

• Fragmentation: Europe is not one region. A center in Krakow serves different cultural expectations than one in Dublin. Language support is non-negotiable.

• Tactical Advice: Adopt a 'Hub and Spoke' model. A central hub (e.g., Poland/Romania) for transactional work, with local 'spokes' in major markets for relationship management and legal compliance. Be wary of 'monitoring' tools that track individual productivity, as these often violate EU labor norms.

APAC (The Scale & Transformation Engine)

• Market Context: India and the Philippines remain the volume leaders (India has ~1,590 centers). However, the narrative is shifting from 'cheap labor' to 'digital talent.'

• Challenges: High attrition (20-30% in some metros) and wage inflation. The 'night shift' culture is becoming harder to sustain with Gen Z.

• Tactical Advice: Pivot APAC centers to become your 'Automation Factory.' The technical talent in India is superior for building RPA and AI solutions. Rebrand these centers from 'Back Office' to 'Digital Innovation Hubs' to attract and retain talent.

Proof it Works

The Platform Dilemma: Build, Buy, or Compose?

Heads of Shared Services face a crowded technology landscape. The choice typically falls into three categories: ERP-native extensions, specialized GBS platforms, or point solutions.

1. The Orchestration Layer (ServiceNow, Salesforce, Jira Service Management)

• Pros: These platforms act as a 'layer of engagement' sitting above your fragmented ERPs (SAP, Oracle, Workday). They provide a unified front door and robust workflow orchestration. They are essential for visibility.

• Cons: High licensing costs and implementation complexity. Requires a dedicated product owner.

• Verdict: Essential for mature GBS (>500 FTEs) to achieve transparency.

2. Specialized Point Solutions (RPA, Process Mining - UiPath, Celonis)

• Pros: High impact on specific tasks. Process mining (e.g., Celonis) provides irrefutable data on process bottlenecks.

• Cons: Creating 'islands of automation.' If not connected to the core workflow, they create maintenance debt.

• Verdict: Use these as engines connected to your orchestration layer, not as standalone fixes.

3. ERP-Native Modules

• Pros: Already paid for; deep integration with data.

• Cons: horrible user experience (UX). Business users hate logging into SAP/Oracle to make simple requests. Poor intake capabilities.

• Verdict: Keep them as the 'system of record' but do not use them as the 'system of engagement.'

Evaluation Criteria Checklist

When selecting tools, GBS leaders must ask:

• Multi-Tower Capability: Can this handle HR, IT, and Finance requests in one portal? (Avoids portal fatigue).

• Geo-Awareness: Does it support multi-language and data residency requirements for GDPR/China Cyber Security Law?

• SLA Transparency: Can the business user see a 'Pizza Tracker' view of their request status?

• Integration: How easily does it talk to legacy on-prem systems via API?

Frequently asked questions

How long does it realistically take to see ROI from a GBS transformation?

While quick wins (like shutting down email inboxes) can be felt in 3 months, a full ROI typically matures between 12-18 months. Initial costs often rise during implementation due to dual-running costs and technology investment. However, industry data suggests that once stabilized, mature GBS models deliver 30-50% reductions in delivery costs. The key is to communicate this 'J-curve' investment profile to the CFO early to manage expectations.

How do I handle business units that refuse to use the new ticketing system?

Resistance is natural. The solution is not enforcement, but experience. If the 'Front Door' is harder to use than email, they won't use it. Ensure your portal is SSO-enabled and requires fewer than 3 clicks to submit a request. Secondly, implement a 'No Ticket, No Service' policy *after* a grace period, but ensure the ticketed path is faster. If an email takes 2 days and a ticket takes 4 hours, behavior will shift.

Should we build our own intake portal or buy a platform like ServiceNow?

Buy, don't build. Maintaining a custom portal creates technical debt and rarely keeps pace with consumer-grade UX expectations. Platforms like ServiceNow, Salesforce, or specialized GBS tools have built-in workflows, analytics, and mobile capabilities that would cost millions to replicate. Your core competency is Service Delivery, not software development.

How do we address the high turnover rates in our APAC centers?

Shift the value proposition. If you hire bright graduates to do 'human middleware' work (copy-pasting data), they will leave. Re-engineer roles to be 'Exception Handlers' and 'Bot Managers.' Invest in their development by certifying them in Lean Six Sigma or Agile. Show them a career path that leads from the delivery center to the Global Process Council. Retention improves when employees see a future beyond the transaction.

Can we really standardize processes across Europe given the regulatory differences?

Yes, but you must distinguish between 'Regulatory' and 'Preference.' About 80% of process variance in Europe is preference-based (legacy habits), while only 20% is regulatory. Use a 'Global Standard, Local Twist' approach. Mandate the 80% standard, and build specific configuration modules for the 20% regulatory requirements (e.g., specific VAT handling in Italy vs. France).

15-20% → 30-50%

Cost Reduction (Mature GBS)

Achieved through global standardization and aggressive automation (Tier 0)

40-50% → 80-90%

Touchless Invoice Processing

Requires unified intake and integrated OCR/AI validation layers

90-95% → 98%+

SLA Adherence (Quality)

Best-in-class centers measure 'User Experience' alongside SLA

10-15% → 40-50%

Auto-Resolution Rate (Tier 0)

Driven by robust knowledge bases and self-service portals