Every HR Process Is Really a Decision Process
I don't think HR manages processes.
I think HR designs decisions.
The more I think about it, the more I realize that almost everything we do eventually leads to someone making a decision. Hiring, promotions, compensation, succession, learning, workforce planning, organizational changes... they're all decisions. The forms, workflows, approvals, systems, and policies that surround them are simply mechanisms to help people make those decisions consistently.
It's a small shift in perspective, but I think it changes how we think about HR.
Take recruiting. Most organizations spend time improving the recruitment process—reducing time to hire, increasing recruiter capacity, introducing AI, redesigning interview stages. Those initiatives matter, but they're not the end goal. The process exists because, at some point, someone has to decide whether a candidate should join the organization. Everything else should increase the quality of that decision.
Performance management is no different. We often debate rating scales, calibration sessions, forms, deadlines, and system configuration. Yet the real purpose isn't completing performance reviews. It's helping leaders make fair decisions about development, recognition, promotions, compensation, and future potential. If those decisions don't improve, it doesn't matter how efficient the process becomes.
Once I started looking at HR this way, I realized something else. Many of the disciplines we've traditionally treated as separate are actually solving the same problem.
People Analytics exists to provide evidence for decisions.
Job Architecture creates consistency so decisions are comparable across the organization.
Skills provide another input into those decisions by helping us understand capability, potential, and future readiness.
People Operations builds the processes that allow decisions to happen efficiently and consistently.
Governance clarifies who makes decisions, what information they use, and how those decisions remain fair over time.
Even AI starts to look different. Instead of asking where AI fits into HR, we should ask which decisions could benefit from better information, faster analysis, or a different perspective. AI doesn't replace decision-making. It changes how we prepare for it.
This also explains why some HR initiatives create lasting value while others don't. We often celebrate successful implementations because a new platform went live or a dashboard was launched. But technology doesn't improve organizations by itself. If managers still make inconsistent hiring decisions, if promotions remain subjective, or if workforce planning is disconnected from business strategy, then we've improved the process without improving the decision.
That's why I think HR should measure itself differently.
Instead of asking whether a process was completed on time, we should ask whether it helped someone make a better decision.
Did leaders have better information?
Were decisions more consistent?
Did employees understand why a decision was made?
Did the organization become more effective because of it?
Those are much harder questions to answer, but they're also much closer to the reason HR exists.
Perhaps that's why I'm becoming less interested in individual HR initiatives and more interested in the decisions they support. Job architecture, AI, governance, skills, analytics, organization design, and workforce planning aren't independent disciplines. They're all different ways of improving the quality of organizational decisions.
Maybe that's the real work of HR.
Not managing processes.
Designing better decisions.