When an HR Problem Isn't an HR Problem
|
ANNOUNCEMENT: The HR Strategy newsletter is evolving and separating into two voices - one voice is more general and will continue being posted on LinkedIn as well as direct to our email subscribers.
HR Strategy Starts With Understanding the Organizational SystemFor years, Human Resources has worked to earn a more strategic role in organizations. We have changed titles, adopted new technology, created centers of excellence, implemented new HR operating models, and worked to become better business partners. But there is a more fundamental shift HR leaders need to make: Stop thinking about HR primarily as a department and start thinking about HR as part of the organizational system. Organizations Operate as Systems Think about what happens when an organization pursues a new strategic objective. A company wants to grow by 20 percent. A government agency needs to deliver services faster. A healthcare organization wants to improve patient access. A university needs to address declining enrollment. Another organization decides to automate a significant portion of its operations. Each objective creates questions about people, work, structure, skills, technology, management, and performance.
These questions cross traditional functional boundaries. HR cannot—and should not—own all the solutions. It rarely controls all the conditions necessary to produce the desired outcome. Every organization is a collection of interconnected components. Strategy establishes direction. Finance allocates resources. Technology enables work. Operations delivers products and services. Leaders set priorities. Managers translate those priorities into daily work. And people operate throughout all of it. That is what makes these organizational problems rather than simply HR problems. When an HR Problem Isn't an HR Problem Organizations frequently address symptoms within individual functions:
Any of these actions may be appropriate. But they can fail when the underlying cause exists elsewhere in the organizational system. Without analysis and diagnosis, the problem remains hidden beneath the symptoms. High turnover, for example, could reflect compensation, engagement, or management. But it could also result from poorly designed work, excessive spans of control, inefficient processes, outdated technology, unclear decision authority, or managers without sufficient capacity or leadership capabilities. If HR approaches the issue only through an HR lens, it may successfully implement an HR solution while leaving the organizational problem unsolved and waiting to resurface. Diagnose Before You Prescribe Imagine a department requesting ten additional employees because the team is overwhelmed. In a transactional model, the request may move directly into recruitment. HR validates the positions, develops job descriptions, determines compensation, and begins recruiting. In a systems-oriented model, HR first helps determine whether recruitment is the appropriate organizational response.
These questions determine whether additional headcount is the right workforce solution. But ten additional employees also represent a significant recurring labor investment—not simply ten recruiting requisitions. Organizational leadership therefore needs answers to a second set of questions:
These questions determine whether additional headcount is the right organizational investment. Both analyses are necessary. Level 1 – Organizational and Workforce Justification: Is additional headcount the right solution? Level 2 – Executive and Investment Approval: Is additional headcount the right investment? Only then can leaders determine whether ten additional employees are actually the right answer. This does not mean HR owns operations, technology, finance, or organizational strategy. It means HR understands how these components interact with the workforce and helps leadership make better decisions. HR Strategy Should Connect the System This is why HR strategy should not begin with a list of HR initiatives:
Those may become strategic initiatives, but first HR must understand what the organization is trying to accomplish and what capabilities it will need to succeed. The sequence is: Business Strategy → Organizational Requirements → Workforce Implications → HR Priorities → Execution That distinction matters. An HR strategy built primarily from HR priorities improves the HR function. An HR strategy built from organizational requirements helps improve the enterprise. The Opportunity for HR When viewed as part of the organizational system, HR has a unique vantage point because it touches nearly every part of the organization. Recruiting sees changing skill requirements. Employee Relations reveals management patterns. Learning identifies capability gaps. Compensation reflects how work is valued. HR technology exposes process complexity. Workforce planning connects business demand to capacity. Payroll and timekeeping can reveal operational problems far upstream from the paycheck. Individually, these look like HR activities. Collectively, they provide intelligence about how effectively the organizational system is working. The opportunity is to connect those signals and ask a different question: “What is happening in the organizational system that is producing this result?” To lead strategically—whether in HR, Finance, Technology, Operations, or another function—requires more than expertise in your department. Strategic leaders must understand how decisions in one part of the organization create consequences elsewhere. To build a better strategy, you first must understand the organizational system that strategy is designed to support. |