Practical Strategies for HR Leaders Navigating AI Without a Roadmap
.jpg)
AI is already reshaping how work gets done. But if you’re in HR, you’re probably frustrated and tired of everyone asking you what they should do about it. But,there’s no clear playbook for how you’re supposed to integrate AI into the workplace.
No standard policies. No best practices. No clean “start here, then do this.”
Instead, it’s just a steady stream of questions coming your way.
In a recent popup workshop hosted by TroopHR, I sat down with people leaders to unpack exactly that: how HR teams can navigate AI when the rules don’t exist yet.
The takeaway? You don’t need a perfect playbook. But you do need to start writing one. HR shouldn’t be on the sidelines of AI - we need to be at the center.
HR is typically looped in when new technology that touches employee data is introduced. AI is no different. While it’s not just another tool, we don’t need to reinvent the wheel to start figuring out how to manage it. Because AI is changing how work gets done, who (or what) does the work, and what roles even look like, HR can’t afford to wait and react. Instead, HR leaders need to:
One of the most practical tactics shared in the session was simple: Run AI hackathons for your HR team. Here’s what that looks like:
Once this is done, you’ll feel some momentum in your team. Imagine if this work could be done by AI!
Now, you start building your AI literacy skills, together. There are many free resources out there (check Reddit or Substack!), pick one and get started. We suggest picking the AI tool you use at work or all have access to.
Teams that do this consistently uncover tons of opportunities. You don’t need everyone to become an AI expert, you just need a few people to get excited - and they’ll help pull the rest of the team forward.
One of the biggest shifts happening right now is that teams aren’t just using AI tools - they’re building AI agents that act like team members. This creates a new kind of workforce that’s part-human and part-AI. It introduces questions HR has never had to answer before:
One of the most useful mental models I shared in the session is that we need to treat AI agents like new hires. That means its role should be defined clearly, boundaries and guardrails should be set, and it should have human oversight. Because here’s the reality: AI is great at execution, but it’s not great at judgment. And that’s why HR needs to be involved.
There’s a lot of noise right now about AI-driven layoffs. But most HR leaders in the session agreed: “Rip and replace” is short-sighted. A better approach is to let AI take over repetitive work, shift humans towards higher-impact responsibilities, and build new roles around evaluating, managing and working with AI.
For example:
The question isn’t: “Which roles disappear?” It’s: “How do roles change, and how do we help people grow into that change?”
Small teams don’t need more time. They need better leverage.
One of the most relatable questions during the session came from a team of one: “This all sounds great, but how do I do this without extra time?” The answer isn’t to do more. It’s to be intentional about carving out time to experiment. Even a couple of focused hours can unlock automated workflows, simple scripts, and reusable prompts. Shift your mindset to treat AI like a collaborator by asking, “How would you build this?” and “What’s the best way to automate this?”
What data can you use with AI? Our advice is to start safe, then expand. Avoid using PII, anonymize wherever possible, and start with broad, non-sensitive data sets. Also speak with your IT/security team regularly around how you’re using AI and if there are any flags that should be raised.
Additionally, HR leaders are feeling tension around the potential of AI’s bias, privacy, environmental impact and workforce disruption. Opting out entirely doesn’t solve these problems. Start by learning how AI works, understanding its limitations and participating in shaping how it’s used.
There’s no perfect framework yet, but there are clear patterns emerging: