Skip to content
Back to articles

How to Use AI in HR: Redesign One Process End to End

November 4, 2026 7 min read
Share
Charcoal sieve clogged with grey pebbles, with one orange-rimmed gap letting them pass, illustrating how to use ai in hr

Your HR team has probably tried a dozen ways of using AI by now. Someone found a way to speed up job descriptions. Someone else uses it to draft performance review language. There is a tracker somewhere showing who completed the training modules.

And when you look at the output of the HR function, the hiring speed, the retention, the quality of management, nothing has moved.

This piece is about why that happens and what to do instead. The short version is that the gains are sitting inside individual tasks, and the processes those tasks belong to have not changed.

Why does HR keep finding new AI use cases without seeing results change?

Each use case gets added to an existing process and the process stays as it was. A faster first draft of a job posting does not fix a slow hiring process. It produces the same process slightly faster.

You can see it in most HR teams that have been experimenting for a while. Someone in recruiting uses an AI model to screen resumes faster. Someone in learning and development uses one to generate training content. Someone in compensation and benefits uses one to draft policy language. Each is a real time saver for one person on one task.

None of them touch the structure of the process they sit inside. The approval chain is still six people long. The handoff between recruiting and hiring managers is still where requisitions go to wait. The performance review cycle runs on the same calendar it ran on five years ago, with AI-assisted language in the boxes.

What is the difference between using AI in HR tasks and redesigning HR processes around AI?

Using AI in HR tasks means applying it to steps a person already does: writing an email, screening a resume, summarizing feedback. Redesigning a process around AI means rethinking the whole sequence, from trigger to outcome, so the process produces a different result.

Take onboarding. Using AI in the task might mean generating a welcome email faster or drafting a checklist. Redesigning the process means asking what a new hire needs in their first ninety days to become productive, then building it so AI handles the repetitive coordination and a person spends their time on the parts that need judgment: the manager conversation, the team introduction, the context only a colleague can give.

A shared starting point helps here. When everyone in the function learns AI together, on HR's own work, the team can build solutions to shared problems instead of a collection of personal shortcuts.

The moments that matter in the employee experience are where this redesign has to happen: hiring, onboarding, performance management, promotion, recognition. Working on individual tasks inside those moments while leaving the moment itself alone is why usage numbers climb and results stay flat.

How do you know if HR's AI adoption is working?

Look at the process metric the work exists to move. If time to hire is unchanged, if managers rate the review cycle the same way they did last year, if regrettable attrition is unchanged, the AI use cases have not reached the process that produces those outcomes.

This is a harder standard than many HR teams apply today. It is much easier to report that forty people completed an AI training module than to report that the average time from requisition to offer dropped. The first number is comfortable. The second tells you whether anything changed.

One honest test: if AI were switched off tomorrow, would the process just be slower, or would people have to go back to a different way of working? If it would only be slower, you have added speed to an old process. If the work itself would have to change back, you have redesigned something.

Who is responsible for turning HR's AI experiments into a real outcome?

Someone in HR leadership has to own it, because no individual contributor has the authority to rebuild a cross-functional workflow. Without a named owner, experiments stay experiments.

The CIO and CISO own the technology, and that is their job. Changing how people behave inside a process belongs to HR leadership: which recruiter talks to which hiring manager, when an AI draft gets reviewed and when it gets accepted, who decides the process has changed. If HR leadership does not hold that, nobody does.

The sign of a gap is HR staff each running their own version of an AI workflow, with no shared standard and no one checking whether the results differ. That points to an ownership decision nobody made. The organization decided who was accountable for buying the license and stopped there.

When a manager will not hand off a step to the new process, or a recruiter goes back to the old screening method, treat it as information. People who have run a process for years usually know where it breaks. Their reluctance to trust a new version is often the most accurate data you have about where the redesign is incomplete.

What should HR do instead of looking for more prompts to try?

Map one full process end to end, from the moment it is triggered to the outcome it is meant to produce, and look for the places where a person's judgment is being used to cover a gap in the process. Those gaps are where AI should be applied.

Start with one of the moments that matter: hiring, onboarding, performance management or promotion. Walk the sequence as it runs today, which is rarely how the process document says it runs. Note every point where someone is stitching information together by hand, every approval that exists because nobody trusts the step before it, and every place where a manager is doing work a system should be doing.

Those are the places where AI changes the shape of the process. This is slower and less satisfying than rolling out something new to the whole team, because it means admitting that the process is the current ceiling.

If you already know this is the work and want a structured way to run it, see how the AI Profit Partnership works. It starts by researching how your team works today, puts quick wins in place along the way, and ends with a plan for the year ahead.

Take it with you

Download this as a PDF

A clean, branded version to read offline or share with your team.

Frequently Asked Questions

How long does it take to redesign an HR process around AI?

It depends mainly on how many functions and handoffs the process touches, and how much authority the process owner has to change steps without new approvals each time. A process confined to one team moves faster than one spanning recruiting, legal and hiring managers.

Do we need to replace our current AI software to redesign the process?

Usually not. What people already use for individual tasks often stays in place. What changes is where in the sequence AI sits, and whether a manual step exists only because the surrounding process was never redesigned to remove it.

Is resistance from HR staff to new AI workflows a sign the launch failed?

Not necessarily. Staff resistance is often accurate information about where the redesigned process still has a gap, since the people running a workflow daily usually know its weak points better than the people who approved the budget.

Should HR leadership or IT own the AI redesign in HR processes?

IT and the CIO typically own the technology decisions. HR leadership needs to own the redesign of how people work inside the process, because that requires authority over how the function works together.

What is the first process HR should redesign around AI?

Start with one of the moments that matter most to the employee experience, such as hiring, onboarding or performance management, and map it end to end as it runs today before applying any AI model.

Share
Newsletter

With People

The people side of making AI pay.

  • One story from the news about AI at work, read through our book, The Elephant in the Algorithm.
  • A few links worth your time, and sometimes a podcast conversation.
Privacy Policy