Managerial Tier · 4 PCF processes across 2 process groups
Computed from PCF 7.0's confirmed RACI data using the Responsible/Accountable touch rule.
Director of HR Ops holds Accountable on 4 L3 processes: 7.1.1 (R only, HR strategy formation), 7.1.2 (workforce planning & HR program design), 7.1.3 (monitoring/updating HR strategy), and 7.4.5 (monitoring the legal and regulatory environment).
Director of HR Ops has previously been described in this framework as the owner of Enable & Govern — 16 L3 processes, the largest single lane in PCF 7.0 — based on who the value stream's nominal owner is. Under the strict R/A-touch rule used here, that owner-level description doesn't match this role's actual Accountable footprint: only 1 of Enable & Govern's 16 L3s (7.4.5) carries Director of HR Ops as Accountable; most of the rest (particularly the HRIS-heavy 7.7.x processes) are Accountable to HRIS Analyst or HRBP Manager. This role's real Accountable scope is concentrated in HR strategy/policy formation (7.1.x), not day-to-day Enable & Govern operations — stated as a genuine owner-vs-accountable mismatch, the same diagnostic pattern this project has surfaced before (e.g. the original Recruit-to-Hire split), not something to smooth over.
Each Mixed-pattern process is shown with its own aggregate rollup row (a proportional pattern-mix bar), followed by its individual Level 4 activities.
| PCF | Activity | Pattern | M1 UNDESIGNED | M2 EMERGING | M3 ★ DESIGN INTENT | M4 OPTIMIZED | M5 LEADING | Δ M1→M3 |
|---|---|---|---|---|---|---|---|---|
| 7.1.1 | Develop human resources strategy | 82% | 74% | 60% | 47% | 37% | -22% | |
| 7.1.1.1 | Identify strategic HR needs | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.1.2 | Define HR and business function roles and accountability | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.1.3 | Determine HR function roles and structure | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.1.4 | Determine HR delivery model | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.1.5 | Determine HR costs | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.1.6 | Establish HR measures | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.1.7 | Communicate HR strategies | Document | 72% | 58% | 40% | 28% | 18% | -32% |
| 7.1.1.8 | Develop strategy for HR systems/technologies/tools | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.1.9 | Manage employer branding | Document | 72% | 58% | 40% | 28% | 18% | -32% |
| 7.1.1.10 | Design the employee experience | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2 | Develop and implement workforce planning, policies, and strategies | 78% | 69% | 56% | 43% | 33% | -22% | |
| 7.1.2.1 | Perform strategic workforce planning | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.2 | Develop total compensation and rewards strategy | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.3 | Develop succession plan | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.4 | Develop high performers/leadership programs | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.5 | Develop diversity, equity, and inclusion plan | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.6 | Implement diversity, equity, and inclusion plan | Transaction | 60% | 48% | 35% | 22% | 12% | -25% |
| 7.1.2.7 | Design talent acquisition program | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.8 | Design talent development program | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.9 | Develop other HR programs | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.10 | Develop HR policies | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.11 | Administer HR policies | Transaction | 60% | 48% | 35% | 22% | 12% | -25% |
| 7.1.2.12 | Plan employee benefits | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.13 | Develop workforce strategy models | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.2.14 | Implement workforce strategy models | Transaction | 60% | 48% | 35% | 22% | 12% | -25% |
| 7.1.2.15 | Manage job families | Transaction | 60% | 48% | 35% | 22% | 12% | -25% |
| 7.1.2.16 | Develop and maintain job descriptions | Document | 72% | 58% | 40% | 28% | 18% | -32% |
| 7.1.3 | Monitor and update HR strategies, plans, and policies | 82% | 73% | 59% | 46% | 36% | -23% | |
| 7.1.3.1 | Measure realization of HR objectives | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.3.2 | Measure contribution of HR to business strategy | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.1.3.3 | Communicate HR plans and provide updates to stakeholders | Document | 72% | 58% | 40% | 28% | 18% | -32% |
| 7.1.3.4 | Review and revise HR plans | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
| 7.4.5 | Monitor legal and regulatory environment | Knowledge | 85% | 78% | 65% | 52% | 42% | -20% |
7.4.5 (Monitor legal and regulatory environment) is the one single-pattern process in this role's scope — Knowledge-pattern, 85% M1 baseline, matching the domain's typical strategy-tier ceiling. The rest of the role's real automation exposure sits inside 7.1.2's Transaction-pattern activities (policy administration, DEI plan implementation, workforce-model implementation, job-family management).
None of the first five roles profiled quite match this shape. HRBP Manager and Director of L&D both had genuinely mixed portfolios; CHRO's was orchestration from the top with almost no personal task exposure. Director of HR Ops sits in between: real Transaction-pattern exposure (policy administration, program implementation) alongside a distinct, less automatable responsibility — owning the legal/regulatory monitoring that keeps the rest of HR's automation defensible.
Josh Bersin's April 2026 “HR 2030” research is squarely about this exact intersection: how an HR operating model builds a new agentic architecture while coexisting with the transactional systems (payroll, compliance, labor relations, taxes) that took years to build and “won't go away.” His research frames this as an HR-and-IT-leader problem specifically — not an HR Business Partner or Talent Acquisition problem — which lines up with this role's actual scope: strategy formation, workforce program design, and regulatory monitoring, not front-line HR service delivery.
Bersin's HR 2030 vision names the operating-model questions a role like this now has to answer, not just execute against.
Framework connection: This maps directly onto the Role Impact Snapshot's finding: the role's real Accountable scope is HR's own operating model — strategy, policy, and regulatory posture — not the broader Enable & Govern lane it's sometimes described as owning. Bersin's research is about exactly that operating-model layer, not front-line service delivery.
| Getting Started | Established | Future-Focused | |
|---|---|---|---|
| Role focus | Maintaining today's transactional HR systems (policy admin, benefits, compliance records) alongside a new agentic layer | Building the HR operating model's agentic architecture in a way that extends, not replaces, existing transactional systems (payroll, compliance, labor relations) | Owning the enterprise HR operating model as a living system — policy, workforce strategy, and regulatory compliance running through the same agentic architecture |
| Key activities | Auditing current HR policy/regulatory content for what's ready to feed into an AI system vs. what still needs a human owner | Deciding which processes get ‘core’ agents (holding first-order data) vs. ‘decision-making’ or ‘observing/reporting’ agents layered on top | Governance-by-design for explainability — Bersin expects regulators may start requiring explainability data when automated decisions go wrong |
| Skills to build | Data integration and data-quality fundamentals — Bersin names this as the near-term focus for HR and IT leaders together | Architecture governance — Bersin's research finds a single ‘giant HR agent’ approach fails; domain-specific agents need clear boundaries | Enterprise architecture ownership spanning HR and IT; a defensible answer for how each agent's decisions are logged, explained, and challenged |
| Common pitfalls | Assuming agentic HR replaces transactional systems outright — Bersin is explicit these will coexist for years, not get swapped overnight | Under-scoping regulatory embedding — pay, layoff, hiring, and promotion-bias laws all have to be built into the system design, not bolted on after | Treating architecture as a one-time build — Bersin frames this as a multi-year integration, not a project with an end date |
Source: Josh Bersin, “Introducing HR 2030: A Vision For Agentic Human Resources,” joshbersin.com, April 6, 2026. Fetched and read in full for this profile, not paraphrased from a snippet.