The organizational design framework that defines how the HR function is structured, how it delivers services, how roles and responsibilities are distributed, and how HR interacts with the rest of the business to create value.
Key Takeaways
An HR operating model is the answer to a deceptively simple question: how does HR work here? It defines which HR roles exist, what each role does, how HR services are delivered to employees and managers, where decisions get made, and how the function connects to business strategy. Without a deliberate operating model, HR evolves organically, and organic growth usually means duplication, unclear roles, inconsistent service levels, and frustrated stakeholders. A company might have HRBPs who spend 80% of their time on operational tasks because shared services doesn't handle Tier 1 inquiries. Or Centers of Excellence that design programs nobody implements because there's no delivery mechanism. Or Generalists in every business unit doing the same work in slightly different ways with no standardization. The operating model fixes this by deliberately designing how work flows through the HR function. The most widely adopted framework is Dave Ulrich's model, which divides HR into three structural elements: HR Business Partners (strategic advisors embedded with business units), Centers of Excellence (specialized expert teams for compensation, talent, L&D, etc.), and Shared Services (centralized operational delivery for transactions and employee inquiries). But this isn't the only option, and many companies are moving beyond the classic Ulrich structure to models better suited to agile, technology-enabled, and distributed organizations.
There are several ways to structure an HR function. Each model has trade-offs in cost, consistency, responsiveness, and strategic capability.
| Model | Structure | Best For | Key Trade-off |
|---|---|---|---|
| Ulrich/Three-Pillar | HRBPs + Centers of Excellence + Shared Services | Mid to large enterprises (1,000+ employees) with diverse business units | High setup cost and complexity, but strong strategic alignment and operational efficiency at scale |
| Centralized | Single HR team serving the entire organization from one location | Small to mid-size companies (under 500 employees) with one or few locations | Cost-efficient and consistent, but can feel distant from business units and slow to respond |
| Decentralized | Separate HR teams embedded in each business unit or location | Companies with highly autonomous business units or diverse operating environments | Responsive and tailored to local needs, but expensive, inconsistent, and duplicative |
| Federated/Hybrid | Core functions centralized + local HR teams for business-specific needs | Global companies with regional variations in regulations and culture | Balances consistency with flexibility, but governance and role clarity require constant attention |
| Agile HR | Cross-functional HR squads assigned to business priorities rather than functional silos | Tech companies, fast-growing startups, organizations undergoing frequent change | Highly responsive and business-aligned, but hard to maintain specialist depth and career paths |
Dave Ulrich's model, introduced in 1997 and updated multiple times since, remains the foundation for most large-company HR structures. Understanding each pillar is essential.
HRBPs sit with business leaders and translate business strategy into people strategy. They advise on organizational design, workforce planning, talent decisions, and change management. In the Ulrich model, HRBPs are explicitly not operational. They shouldn't be processing payroll exceptions or answering benefits questions. When they are, the operating model has broken down. Good HRBPs understand the business P&L, competitive dynamics, and operational challenges as well as any other member of the leadership team. HRBP-to-employee ratios vary, but 1:250 to 1:500 is typical for strategic partnering. Anything lower and the HRBPs get pulled into operational work.
COEs are teams of subject-matter experts who design HR programs and policies: compensation structures, talent acquisition strategies, leadership development programs, employee engagement initiatives, DEI frameworks, and learning curricula. They set the standards and build the tools. They don't deliver programs directly to employees. That's shared services and line managers. A typical COE structure includes Compensation and Benefits, Talent Acquisition, Learning and Development, Talent Management, and Organizational Effectiveness. COEs need to balance innovation (designing new programs) with governance (maintaining existing ones).
Shared services handle transactional HR work at scale: payroll processing, benefits enrollment, employee data management, basic employee inquiries, and compliance administration. They operate on a tiered model: Tier 0 is self-service (portals, chatbots, knowledge bases), Tier 1 is the service center (phone, email, chat for questions the portal can't answer), and Tier 2 is specialists who handle complex cases. The goal is to resolve 70 to 80% of inquiries at Tier 0 or Tier 1, freeing COEs and HRBPs from operational interruptions. Best-in-class shared services operations resolve 85%+ of inquiries without escalation (APQC).
Designing or redesigning an HR operating model is one of the most consequential decisions an HR leadership team will make. It takes 12 to 24 months to implement properly.
Document how HR currently operates: who does what, where are the handoffs, what works, and what doesn't. Survey HR team members and their internal clients (managers and employees) to identify pain points. Map the time allocation of each HR role against what you'd want in an ideal model. If HRBPs spend 60% of their time on operational tasks, that's a structural problem the new model needs to solve. Tools like process mapping and time studies are useful here.
Start with the business strategy. What does the business need from HR over the next 3 to 5 years? If the company is expanding internationally, the model needs to account for multi-country compliance and localized service delivery. If the company is growing through acquisitions, the model needs to scale quickly and integrate new populations. If the business is shifting to agile, HR might need an agile structure to match. Define the service level expectations: how fast should HR respond to employee inquiries? What's the acceptable payroll error rate? How quickly should a new hire be fully onboarded?
Select the model that best fits your requirements (Ulrich, centralized, federated, agile, or a hybrid). Don't force-fit a model because another company uses it. A 200-person company doesn't need a full Ulrich model with COEs and shared services. A 10,000-person global company can't operate with a single centralized HR team. Match the structure to the scale, complexity, and strategy of the business.
The biggest failure point in any operating model is role clarity. If nobody knows whether the HRBP or the COE owns talent review, both will do it poorly or neither will do it at all. Create a RACI (Responsible, Accountable, Consulted, Informed) matrix for every major HR process. Define escalation paths. Establish governance forums where HRBPs, COEs, and shared services leaders align on priorities, resolve conflicts, and coordinate delivery. Without governance, the model fragments within 12 months.
Operating model changes affect every HR professional's job and every employee's experience with HR. Communicate the rationale, the expected benefits, and what will change for each group. Retrain people who are moving into new roles (an HR Generalist becoming an HRBP needs different skills). Run the old and new models in parallel during transition. Set milestones and measure adoption. Most operating model redesigns that fail do so because of inadequate change management, not poor design.
Gartner reports that 79% of HR leaders are dissatisfied with their operating model. These are the most common reasons the model doesn't work as intended.
This is the most common failure. The model says HRBPs are strategic partners, but in practice they spend most of their time on employee relations cases, payroll exceptions, and benefits questions because shared services is underfunded or doesn't cover enough. The fix requires investing in shared services capacity, building self-service tools, and explicitly removing operational tasks from the HRBP role description. If the HRBP answers a single benefits question, it signals to the organization that they're still the go-to for operational issues.
Centers of Excellence sometimes design programs in isolation that don't reflect what business units actually need. They create a learning program nobody completes or a compensation structure that doesn't match the talent market. The fix is embedding COE experts in HRBP conversations and requiring every COE initiative to have a business sponsor. COEs that only talk to each other produce academically sound but practically useless programs.
If shared services can only process basic transactions and everything else escalates to HRBPs, the model doesn't achieve its purpose. Shared services needs Tier 2 specialists who can handle complex cases: multi-state tax corrections, leave of absence coordination, cross-border transfers. Without this depth, the escalation path dumps operational work right back on the strategic layer.
When it's unclear who owns a process, nothing gets done well. Who is responsible for the annual performance review: the Talent Management COE (who designs the framework), the HRBP (who coaches managers through it), or Shared Services (who configures the system and tracks completion)? The answer is all three, but without a RACI and a governance forum, each assumes the other is handling it. Process ownership must be explicit and documented.
The way companies structure HR is evolving in response to technology, workforce changes, and business agility demands.
Josh Bersin and others have proposed adding a fourth pillar: People Analytics / HR Technology. In this model, analytics and technology aren't buried within shared services or scattered across COEs. They're a dedicated team that supports the entire HR function with data, insights, dashboards, and system design. This reflects the reality that data and technology capabilities are now as important as any traditional HR specialization.
AI is collapsing the tiers in shared services. Chatbots handle Tier 0 and much of Tier 1. Automated workflows handle routine Tier 2 processes. This means shared services teams are getting smaller and more skilled, focusing on complex exception handling rather than volume processing. For HRBPs, AI provides real-time analytics that previously required days of manual data gathering. For COEs, AI enables personalized program delivery at scale. The operating model of 2027 will require fewer people doing operational work and more people designing and overseeing AI-augmented processes.
There's no one-size-fits-all answer. The right model depends on specific organizational factors.