Part of the People Ops AI Brain — ← Back to Hub
<aside> 🏛️
This page is about operating model redesign, not tools. Not "how do I use AI" but "how do I redesign my People function so AI is infrastructure, not an add-on." The roles, the team shape, the builder development model, the capability architecture. If you're a Head of People thinking about what your function looks like in 12 months, this is probably the most important page in the Brain.
</aside>
<aside> 🔀
Tool-agnostic. Everything here works whether your team uses ChatGPT, Copilot, Claude, Gemini, or a mix. The frameworks are about capability design, not any specific product. Where we reference skills files or workspaces, they work across all major AI tools.
</aside>
<aside> ⏱️
TL;DR | 20 min read | This one's for you, the senior leader.
AI-Enabled → AI-Augmented → AI-Native. A maturity model for your People function. Role evolution, team structures by company size, the AI Champion model, governance, and a 90-day plan.
Your decision: What maturity level are we targeting and by when? Your action: Place your team on the maturity model below and be honest about where you actually are.
</aside>
Three stages. Be honest about where your team sits today.
AI-Enabled: Using AI tools occasionally to speed up existing work. Someone on the team has a ChatGPT account and uses it for drafting. Maybe two people. No shared approach. No consistency.
AI-Augmented: Systematically integrating AI into core workflows. The team has shared skills files, agreed ways of working, and AI is part of how things get done. Not every time. But intentionally and consistently.
AI-Native: Your entire function is designed around what's possible when AI is a given. Not an add-on. A foundational assumption about how work happens.
The difference isn't just tools. It changes:
Most People teams are somewhere between Enabled and Augmented. That's fine. Knowing where you are is the starting point.
This is the big mental model change. And it's happening faster than most People leaders expected. The market moved from "should we use AI?" to "how do we redesign around it?" in about six months. The teams that figured this out early are already operating at a fundamentally different level.