Every HR Leader I Know Is Drowning in Ideas
Someone I connected with recently built a site that generates a personalized user manual for how someone works. Clean concept, real product, live in the world. I walked away from that conversation equal parts inspired and embarrassed. I had thought about something like that at least twice. I never built it.
That gap is what I keep running into.
HR practitioners are having more ideas about AI than almost any other function. We are attending the sessions, listening to the podcasts, collecting the use cases. We are genuinely curious and genuinely engaged. And most of us are still not shipping anything.
I have been sitting with why that is, because “I’m too busy” is not an honest answer. “I’m not technical” stopped being a real excuse about eighteen months ago.
Zachary Parris named something useful on the Modern People Leader podcast. He said it comes down to mindset, not tools, not capability. The people who are building things have made a specific internal shift. The people who are not building have not made it yet, including me, until recently.
The shift is not about knowing more. It is about tolerating the gap between the idea and the messy, imperfect first version of the thing. Parris framed it directly: you do not pitch the workflow. You build the workflow and show it running.
We are trained to get things right before we put them in front of people. Every piece of guidance, every framework, every communication has to be approved, reviewed, considered from multiple angles. That instinct is useful in a lot of HR work. It is death to building. The version you will actually learn from is the one you made in two hours and put in front of a real person to watch them use.
There is a cost to staying in ideas mode, and it is not just missed opportunity in the abstract. It is credibility. HR has been talking about being strategic, about demonstrating value, about having a seat at the table for twenty years. Building is the clearest way to make that case right now. When you ship something, even something small, you are not describing what HR could become. You are showing it.
What Parris also said, and what I keep returning to, is that the problem statement has to come first. Before you touch a tool or a prompt or a prototype, you have to genuinely understand what you are solving for. That discipline HR actually has. We know how to diagnose. We know how to ask what the real problem is underneath the stated one. That is a real edge. Most of us are just not using it to build anything.
So here is the honest question. You have had at least one idea in the last ninety days that could have become a real tool, a working agent, a prototype someone could actually try. What is still sitting in a note somewhere? And what would it take to give it a deadline?