Escaping the Pilot Trap: Building HR for the Agentic Era

Every HR leaderwe speak with now asks the same question about creating an agentic HR function: We understand the general destination, but how do we get there? We believe their approach should be rooted in what makes the agentic transformation different. In earlier HR transformation waves, the human was always the unit of execution, and technology was a tool that humans operated. Agents change that assumption. They can reason, act across systems, and be orchestrated into teams that are supervised and held accountable. The rise of agents changes the redesign problem in two ways. First, speed and frontline customization increase sharply. A payroll specialist or a recruiter can now configure a working agent in an afternoon using low-code tools. This is the greatest accelerant of the transformation and, at the same time, its greatest governance challenge. Local experimentation and design, without proper guardrails, can harden into a fragmented landscape of one-off agents faster than any central team can catalog it. Second, HR must transform itself at the same pace it is asking the enterprise to move. In the ERP and agile eras, HR was largely a downstream adopter of changes designed elsewhere. In the agentic era, HR has a dual mandate as both the architect of the enterprise’s human–agent redesign and a subject of that same redesign. A function that moves slower than the organization it advises, or that automates tasks while preaching workflow redesign, forfeits the credibility to lead. The implication is uncomfortable for leaders trained on the last two decades of transformation: The instinct to “start small and learn” is no longer conservative. When any specialist can stand up an agent in an afternoon, starting small happens whether leadership sanctions it or not. The question is whether those efforts unfold within a deliberate design or instead of one. In prior transformations, moving without a blueprint cost time. In this one, it costs the blueprint itself—every ungoverned agent hardens a fragment of the old operating model into code. We call this the pilot trap: speed at the level of the task, drift at the level of the design. That is why the redesign can’t be managed pilot by pilot and why the journey must run from what we call “North Star back.” A North Star should solve three core tensions Organizations are approaching the agentic HR journey in different ways. In our work with a wide range of companies, we see several common patterns emerging, from a focus on a small number of use cases ripe for agentification to a full reinvention of HR. Having watched these patterns play out, we believe they are not equal alternatives. The default should be the North Star–back approach: Define the 2030 human–agent operating model for the function first, then work backward to the implementation sequence, capability investments, governance structures, and quick wins needed to get there. Everything else is an entry point into that journey, not a substitute for it. In creating the North Star, some elements are commonly understood: AI frees humans for more strategic work, and humans bring judgment while agents propel scale. The harder conversations we have with executives involve three core tensions: Who owns the orchestration platform? The agents belong to HR, but the platform they run on is enterprise infrastructure covering identity, security, integration, and orchestration. If IT owns it outright, HR waits in a queue and loses the pace advantage that makes agents valuable. If HR builds its own, the enterprise inherits a shadow stack. The same question repeats inside HR: Which agents are built centrally as products, and which are configured locally by the people who own the workflow? Investment versus surveillance: Agentic HR can finally tailor its work to the individual rather than the segment, anticipating a career move, curating the next role, and tailoring development to how someone actually works. The same capability that goes one notch too far or is introduced without transparency stops feeling like an investment and starts feeling like surveillance. The line is not set by regulation. It is set by whether employees believe the personalization serves them. Automating work versus accelerating people: The easy decision is what agents should absorb. The harder one is determining which human capabilities become more valuable (judgment, relationships, coaching, persuasion) and where the organization will deliberately accelerate them, in HR and the business alike. That includes cognitive load, or the amount of mental effort employees must expend as they incorporate AI into their work, as well as rebuilding the apprenticeship path. If agents take the entry-level work, the next generation’s judgment has to be developed on purpose rather than absorbed on the job. None of these tensions is solved once; they are managed continuously. A North Star that does not take an explicit position on all three is not yet a North Star. This approach must also be rooted in an understanding of how HR meets evolving business needs, not just technological possibilities. That includes defining HR’s role in supporting the enterprise-wide workforce changes that accompany the AI transformation ahead: redesigning workforce models and building human–agent collaboration capabilities that create economic and strategic impact. Based on changing workforce needs, HR can help attract new talent, and redeploy existing talent, to fill future roles. And it can meet employee expectations for a more seamless and compelling employee experience. Once the North Star is established, organizations pursue two tracks in parallel: a bottom-up track that generates quick wins and builds momentum, and a structural redesign track that progressively transforms the HR function in line with the broader vision. The two tracks reinforce each other. Quick wins help to test the broader vision, while the North Star ensures that individual initiatives fit together as part of a coherent whole rather than a collection of disconnected solutions. Success also depends on close collaboration with IT and other business functions whose work is tightly linked to HR’s transformation. Over time, this approach rebuilds the HR function into a platform that enables the agentic organization of the future while continuing to improve performance. Three entry points, not three strategies Where, then, should an organization generate its first proof points? Bottom-up use cases, end-to-end process redesign, and domain-by-domain reinvention are best understood as entry points into the North Star–backed journey. Deciding which to tackle first depends on an organization’s starting point, data maturity, risk appetite, and leadership readiness. Bottom-up use cases Some organizations start by identifying pain points across the HR function, agentifying them selectively, and building momentum through quick wins. Technologically mature organizations put technology in the hands of all employees, turning everyone into a “citizen developer.” Fast and tangible, this method generates individual and organizational confidence and early proof points that are invaluable. One organization following this path implemented 50 use cases, each valuable on a small scale, from an AI-powered chatbot for employee queries to automated meeting synthesis to AI-augmented learning and performance management. As a result, the company identified significant annual cost savings along with meaningful improvements in HR service levels. The danger of this approach is that its impact can be limited if individual use cases aren’t tied to a broader redesign of workflows, roles, and HR capabilities. In some cases, organizations improve the efficiency of processes that, once work is redesigned end to end, are ultimately eliminated or absorbed into entirely different workflows. This is the pilot trap at work: effort spent perfecting steps that the future operating model eliminates. Succes