Plan for the half-life of a skill

The framework adds a second axis to every role: how fast is the skill it depends on changing, and what replaces it. A recruiter whose day is 60 percent scheduling is not the same planning unit they were two years ago once agents handle scheduling. Your model has to see that.

The output is not a spreadsheet of seats. It is a map of which capabilities to build, buy, or automate, sequenced so your people move up the value chain instead of out the door.

Search “AI transformation leader” and you will find a hundred certifications and no agreement on what the role actually does. Having built and led this work inside a Fortune 500, here is the stack that separates a real transformation leader from someone with a badge.

Translation is the core skill

The job is not to be the best prompter in the room. It is to translate between three languages: what the business needs, what the technology can do, and what your people can absorb. Everything else, the tools, the models, the vendors, changes underneath you.

Certifications help when they teach frameworks and judgment, not just features. Choose the ones that leave you able to run a transformation, not just pass a quiz about one.

You have the mandate and a quarter to show it was real. The temptation is to write a strategy. Resist it. In the first 90 days, one shipped workflow beats a beautiful roadmap every time.

Ship one thing, involve the right three people

Pick a single high-volume, low-judgment workflow. Pull in one HR owner, one data or IT partner, and one person from legal or compliance early, not at the end. Deploy it to a real team, measure it against a baseline, and write down what broke.

Deliberately skip the enterprise platform decision, the center of excellence org chart, and the three-year vision deck. Those are Quarter Two problems. Quarter One is about proof, in production, that your People function can build.

Most HR AI governance fails the same way: a forty-page policy nobody reads, so people either freeze or freelance. The Governance Traffic Light replaces the document with a decision anyone on the team can make in a minute.

Red, yellow, green

Green is go: low-risk, low-judgment uses like drafting internal FAQs. Yellow needs a human in the loop and a named reviewer, like screening support. Red stops and escalates: anything touching a hiring or termination decision, protected data, or a regulated outcome.

Classify each use case once, make the classification visible, and revisit it as the tools change. Simple enough to use, strict enough to defend. That combination is what actually keeps a People function safe.

People buy a repeatable outcome, not a clever sentence

What holds up in production is a workflow: a defined input, a step the AI owns, a human check, and a measurable output you can defend. That is the difference between showing someone a trick and handing them something they can run every week and stand behind with their boss or their client.

If you support other teams, in-house or as an advisor, this is the line that matters. Generic prompts make you interchangeable. A framework you can name, apply, and measure makes you the person they call. Build the workflow, not the prompt library.

Two groups keep asking me the same question from opposite directions. HR people who want to lead AI transformation, and AI people who want to work in HR. Both already know they want to be something different. The only real question is how to build a practice someone will actually pay for.

Sell an outcome you own, not a tool you rent

The trap is teaching other people’s tools. If your offer is “I will show you a few AI apps,” you are interchangeable with everyone else running the same demo, and you own nothing. The durable move is to stand on a framework and a repeatable method that is yours, so the value walks in with you and does not evaporate when the tool changes.

Start narrow. One assessment, one workflow, one clear outcome a buyer can picture. Prove it delivers, then widen. A practice is not a menu of everything you can do. It is one thing you can do that people trust you to run.

Follow the tasks, not the titles

Scheduling, first-pass screening, policy lookups, benefits FAQs, and status updates are already moving to agents in production. What stays human is judgment: the coaching conversation, the sensitive investigation, the trade-off nobody wrote a policy for.

So the real risk is not redundancy. It is a People function that keeps spending its best people on the tasks a machine now does well, and has nothing built for the work only they can do.

Frequently asked questions

Will AI replace HR jobs?

Not the jobs, the tasks. AI is already handling scheduling, first-pass screening, and policy questions, while judgment-heavy work like coaching and investigations stays human.

Will AI replace HR consultants?

Not the ones who bring a repeatable method. Consultants who only pass along generic prompts are exposed; those who own a framework and can measure outcomes become more valuable, not less.

From assisted to integrated

Level 1 is assisted: a person uses a copilot for a single task. By Level 3 an agent owns a whole workflow with a human reviewing the output. At Level 5, agents run end-to-end processes and hand people the exceptions. Each level has a different risk profile, a different skill requirement, and a different ROI story.

The point is not to reach Level 5 fast. It is to know which level you are actually at, so the next move is the right size instead of a leap you cannot govern.

Frequently asked questions

What are examples of agentic AI in HR?

An agent that opens a requisition, drafts the description, screens the first pass, and books interviews; an agent that answers benefits questions end to end; an agent that runs onboarding steps and flags the exceptions for a human.

What are the levels of AI maturity in HR?

The 5-Level AI Maturity Model runs from assisted (a copilot on one task) to integrated (agents running end-to-end processes and handing people the exceptions). Each level carries a different risk and skill profile.

Most AI readiness assessments are built for the whole enterprise and written by vendors who want the answer to be “buy our platform.” HR needs something narrower and more honest: where is my team, really, and what is the next concrete step.

Score the team you have, not the one on the slide

Run the assessment across four dimensions: data, tooling, skills, and governance. Score each against the 5-Level Maturity Model, from novice to fully integrated. The gaps between dimensions matter more than the average. A team with great tooling and no governance is not ready, it is exposed.

The deliverable is a single page: current level per dimension, the one gap to close first, and the smallest project that closes it. That is a plan a CHRO can fund on Monday.

Frequently asked questions

How do you assess AI readiness for an HR team?

Score four dimensions, data, tooling, skills, and governance, against the 5-Level AI Maturity Model. The gaps between dimensions matter more than the average score.

What is the 5-Level AI Maturity Model?

A practitioner model that maps an HR team’s AI capability from novice to fully integrated, so the next step is the right size instead of a leap you cannot govern.

When AI value gets reported as “hours saved,” it dies in the budget review. Time saved is real, but on its own it reads as soft. The 5 Dimensions of AI ROI give you a fuller, more defensible case.

Beyond cost savings

The five dimensions are cost, speed, quality, risk, and experience. A screening agent might save modest cost, but cut time-to-fill in half, improve consistency, reduce compliance exposure, and raise candidate satisfaction. Report one dimension and it looks marginal. Report five and it looks like a decision.

Thanks for reading Chronicles of an Unfinished Journey! Subscribe for free to receive new posts and support my work.

The discipline is to name the dimension before you build, instrument it during the pilot, and report it in the unit each stakeholder cares about. That is how AI work survives contact with finance.

Frequently asked questions

How do you measure the ROI of AI in HR?

Look beyond cost savings and measure across five dimensions: cost, speed, quality, risk, and experience. Name the dimension before you build, instrument it during the pilot, and report it in the unit each stakeholder cares about.

What are the 5 Dimensions of AI ROI?

Cost, speed, quality, risk, and experience. Reporting only one dimension makes AI look marginal; reporting all five makes it a decision a CFO can sign off.

Look at your People function’s roadmap for the next three years. The HRIS migration, the skills strategy, the service-delivery redesign: they are all really one thing now, an AI transformation. Pretending otherwise just means someone outside HR gets to define it for you.

Own the transformation, do not outsource it

I lead AI transformation for HR inside a publicly traded company, and the pattern is consistent. The teams that win treat AI as a capability they build, not a product they buy. They start with one workflow, measure what breaks, and expand from there.

Thanks for reading Chronicles of an Unfinished Journey! Subscribe for free to receive new posts and support my work.

This playbook frames the work so HR leads it: the maturity model to anchor the plan, the ROI language to fund it, and the governance model to keep it safe. None of it requires you to become an engineer. It requires you to stop waiting.

Frequently asked questions

Is HR transformation the same as an AI transformation?

Increasingly, yes. Most HR transformation programs now depend on AI, so treating them as separate work leaves the AI decisions to someone outside the People function.

Who should lead AI transformation in HR?

The People function, not IT or an outside vendor. HR owns the workflows, the change management, and the risk, which is exactly where AI transformation succeeds or fails.

Where should an HR team start with AI transformation?

One high-volume, low-judgment workflow. Prove it in production, measure it, then expand using the 5-Level AI Maturity Model.

The distinction sounds like semantics until it hits your operating model. A copilot drafts the job description after you ask. An agent watches the req open, drafts the description, screens the first pass, and books the interviews, then tells you what it did.

Why the difference reshapes the org chart

Copilots make individuals faster. Agents change how many individuals you need for a given volume of work, and which skills those individuals require. A 2026 strategy built only around copilots quietly assumes the headcount stays flat. It will not.

The practical move is to map your HR workflows by how much judgment each step really needs, then let agents own the low-judgment, high-volume steps first. That is where the time-to-value is real and the risk is lowest.

Frequently asked questions

What is the difference between an AI copilot and an AI agent?

A copilot assists a person on one task when asked. An agent takes a whole task or workflow off your plate and reports back. Copilots make people faster; agents change how much work a team needs people for.

Which HR tasks should AI agents handle first?

Start with high-volume, low-judgment steps: scheduling, first-pass screening, policy and benefits questions, and status updates. Keep judgment-heavy work, like coaching and investigations, with people.