01
Establish
Define workforce plan, initial organisation structure, role architecture, hiring ownership, employee lifecycle, HR service model and manager responsibilities before headcount accelerates.
PeopleOS · Global Capability Centres
A GCC needs more than hiring capacity. It needs clear role architecture, global-local decision rights, manager capability, employee-lifecycle processes, service ownership and people data that support both local execution and global integration. PathWeave focuses specifically on that people operating system.
The operating question
That question sits at the centre of GCC people design. A global policy or COE can define standards, but India leaders and managers still need workable local ownership. Likewise, local HR can run delivery without becoming the default owner of every people decision.
PeopleOS makes those interfaces explicit, then connects them to workforce planning, organisation structure, talent acquisition, manager routines, HR operations and data.
Three stages
01
Define workforce plan, initial organisation structure, role architecture, hiring ownership, employee lifecycle, HR service model and manager responsibilities before headcount accelerates.
02
Add management layers, strengthen talent acquisition, formalise performance and career practices, improve people analytics and increase HR service capacity without creating unnecessary bureaucracy.
03
Clarify global-local ownership, improve COE/shared-service interfaces, refine role architecture, build leadership depth and improve governance where the original setup no longer matches the scale.
Global-local HR architecture
Six design areas
01
Translate capability, location and function plans into role families, hiring sequences and management capacity.
02
Clarify levels, spans, accountabilities, reporting relationships and interfaces with global teams.
03
Define role intake, sourcing ownership, assessment, interview governance and handoffs as hiring volume grows.
04
Equip managers to run goals, feedback, performance and employee decisions rather than escalating routine people work to HR.
05
Design employee-lifecycle workflows, local/global handoffs, service ownership and escalation across HR, shared services and COEs.
06
Define data ownership, reporting logic, governance forums and management questions before adding dashboards or automation.
Connected PeopleOS work
HR Transformation connects operating-model changes with process, technology and adoption.
HR Operating Model defines service boundaries, HR/manager ownership and decision rights.
Organisation Design & Role Clarity strengthens structures, levels, accountabilities and global-local interfaces.
Recruitment & Talent supports more disciplined role definition and hiring governance.
Performance Management builds manager-led expectations, feedback and calibration.
HR Operations & HRMS strengthens employee workflows, data and service delivery.
Strict scope
PathWeave is not positioning this page as advice on entity incorporation, taxation, transfer pricing, company law, immigration, office real estate, statutory payroll certification or regulatory approvals.
The scope is people strategy, organisation and HR operating systems. Where a decision requires legal, tax or other specialist advice, the organisation should use the appropriate qualified adviser.
Experience behind PeopleOS

Founder · leads PeopleOS
PeopleOS draws on Renu’s HR leadership, consulting and outsourced HR delivery experience across organisation structures, policies, recruitment, performance management, HR operations and people systems.
This page describes PathWeave's PeopleOS methodology and does not imply GCC client delivery unless separately evidenced.
Where this sits
For broad growth-stage HR needs, see HR Consulting for SMEs. For the overall practice, see PeopleOS. For one focused HR operating issue, start with the HR Health Check.
Start with workforce, organisation, HR ownership or manager capability.