How should an executive evaluate an India Shared Services Head mandate with service ownership?

A centralisation target can combine efficiency, control and service goals without ranking their trade-offs. For service proposition, the tested record is the approved service catalogue linked to business outcomes, costs and retained responsibilities, reconciled through the CFO, COO and consuming business leaders. An unclear proposition turns the leader into an operator of transferred work rather than owner of a coherent service system.

Stop if scope is measured by migration volume while service purpose and retained ownership stay ambiguous; apply that premise result to shared services head alone, preserving the source date for service proposition and any authorised contrary record before the appointment story enters candidate or market communication.

A shared-services proposition should state who the internal customer is, which end-to-end processes are in scope and how efficiency, control and experience are ranked. Migration volume and cost targets do not explain the service promise. Ask which business outcome will improve because work is shared and what retained responsibilities remain with the consuming unit. Without that compact, the incoming head becomes accountable for tasks transferred from several models whose demand, data and process choices continue to differ. Ask which internal-customer outcome, process or economic mechanism shared delivery must improve and what retained work remains with businesses. Migration volume is not a sufficient premise. The appointment needs a service proposition, process boundary and accountable consuming-unit compact.

Central delivery may inherit tasks while process design and upstream data remain with multiple functions. For process ownership, the tested record is one end-to-end process traced from demand creation through exception, outcome and corrective action, reconciled through functional owners, technology, controls and business users. The handoffs show whether the executive can repair causes or only manage downstream workload.

Pause when service measures are fixed but process and demand decisions remain fragmented; carry this authority result into the shared services head contract, with the process ownership resolver and reserved matter visible before personal scorecard accountability begins.

Process ownership should be traced upstream from the service queue. Select a recurring exception and follow how demand was created, information entered, work performed, outcome consumed and root cause corrected. Identify whether the shared-services leader can change standards and technology or only manage downstream effort. A central team cannot own cycle time or quality when businesses preserve inconsistent inputs without consequence. The mandate needs an end-to-end owner, explicit handoffs and a route for pricing or refusing repeated non-standard demand. Follow a repeated service exception upstream from demand creation through outcome and correction. Determine whether the head can change standards, technology and inputs or only manage downstream work. End-to-end evidence separates service ownership from task administration.

Businesses may support efficiency while preserving local workarounds and urgent requests that destroy scale economics. For business compact, the tested record is a material service exception with sponsor, incremental cost and expiry treatment, reconciled through business presidents, functional chiefs and finance partners. The precedent reveals whether standardisation survives influential local demand or becomes optional.

Withdraw if business exceptions carry no accountable cost while shared services owns all performance consequences; record this coalition result for shared services head, keeping the documented sacrifice, dissent and binding forum for business compact visible before support becomes a private relationship obligation.

The business compact is tested when a powerful unit asks for a local exception that weakens scale. Review who authorised it, what incremental cost or control effect was recorded and whether it expired. Ask business presidents which standards they will accept and how non-compliance enters their scorecards. If every unit can preserve its preferred process while the central leader owns savings and service, shared services is a supplier without contractual symmetry. The candidate should require visible demand ownership before accepting aggregate performance. Compare business presidents, functional owners and finance on a local exception with real cost or control consequence. Record sponsor, duration and accountability. Standardisation cannot remain the central leader's target if consuming units may opt out without visible trade-offs.

Migration dates can advance despite weak documentation, unavailable experts and unresolved control ownership. For transition readiness, the tested record is a completed transition pack with readiness decisions and post-stabilisation lessons, reconciled through sending teams, receiving leaders, risk and technology owners. Readiness evidence determines whether the first year scales services or recovers transfers made for timetable optics.

Reject migration accountability when the leader cannot delay scope that fails agreed readiness gates; rebase the shared services head promise to the evidence finding for transition readiness, retaining its source owner and closure date before the first-year operating commitment is fixed.

Transition readiness should include process documentation, source experts, controls, data, technology, staffing and stabilisation capacity. Review one completed transfer to see which assumptions failed and who absorbed the consequence. The future head needs authority to delay scope that misses agreed gates, while communicating the economic and business effect transparently. A fixed migration date without a qualified readiness route encourages hidden workarounds and later service failure. It also lets sending leaders claim completion before the receiving operation can govern the outcome. Seek qualified legal, tax, data, employment or financial advice for transfers, entity responsibilities, incentives and personal terms. Provide actual service scope and documents. Operational diligence cannot establish jurisdiction-specific duties independently.

Shared functions can accumulate tasks because no one owns the decision to stop or redesign them. For scope and exit rules, the tested record is a service-lifecycle charter with entry, review, pricing, exception and retirement criteria, reconciled through the executive committee, finance and process owners. Lifecycle governance prevents the mandate from becoming a permanent repository for unresolved organisational work.

Decline if all new scope is mandatory but service retirement and demand control have no governing route; keep the shared services head conclusion dated and private, reopening scope and exit rules only through authorised contrary evidence that changes the original reason and decision date.

Service lifecycle governance should define entry, catalogue, measure, exception, pricing, review and retirement. Ask for an example of work that was returned, automated or stopped because the central model was no longer appropriate. If no service can leave, the function will accumulate unresolved organisational tasks and permanent customisation. The candidate should secure authority to redesign demand as well as delivery. Decline when all additions are mandatory, operating owners retain no obligations and the shared-services head is expected to resolve scope through goodwill. Set conditions for service proposition, process rights, business demand, transition readiness and lifecycle authority. Decline if new scope is mandatory while retirement, exception pricing and upstream correction have no governing route.