We run three distinct service divisions, and our division heads are fighting over whether People Operations and Recruiting belongs as a centralized seat under the Integrator or embedded inside each division. How do we structure shared operational seats on the Accountability Chart without creating bureaucratic bottlenecks?

Question

Tyler Smith · Accepted Answer

Structure must always follow the needs of the business, not the preferences of department heads. In multi-division organizations, the question is whether talent acquisition and HR represent a core competitive advantage that requires division-specific customization, or a repeatable shared service that gains efficiency through centralized scale.

In most middle-market companies, splintering People Operations across three divisions creates redundant vendor costs, inconsistent compliance, and competing job postings that confuse the market. The cleaner model places a centralized People Operations seat reporting directly to the Integrator.

That centralized seat owns recruiting pipelines, compliance, benefits, onboarding frameworks, and HR tech infrastructure. Its customer is the division leadership. However, the division heads retain absolute veto power over hiring decisions within their own teams. The central seat sources, screens, and manages the process; the division head decides if the candidate fits the seat and the culture.

Define the five core roles for the People Operations seat with explicit service-level commitments. For example, role definitions should include recruiting pipeline velocity, compliance and risk management, and onboarding execution.

If an individual division grows large enough to require a dedicated, full-time recruiting resource, that recruiter sits inside the centralized People Operations department but is permanently assigned to support that specific division. This preserves single-point operational accountability while keeping your executive Accountability Chart clean.