Choosing Where AI Helps at Work

Now that you can tell the AI capabilities apart, the next move is harder and more useful: deciding which of your actual HR tasks belong in an AI workflow and which ones absolutely don't. Choosing the right starting point matters. A use case that looks exciting but is hard to verify—like AI-drafted termination letters—can drain time and create legal, EEO, and confidentiality risk, while overlooking practical everyday tasks can leave value untapped. This unit gives you a simple lens to sort your week and choose a first win you can defend.

By the end, you’ll be able to:

• Sort recurring HR work into communication, research, planning, and analysis tasks.
• Evaluate AI candidates using Value, Risk, Repeatability, and Human Review.
• Select a low-risk pilot with a clear success criterion.

Start by looking at a normal week and asking: what kind of HR work keeps showing up? Most AI-assistable tasks fall into four practical buckets.

Why bother sorting? Because each bucket has a different risk profile and a different verification cost. A draft onboarding email may only need a quick tone check. A benefits detail or a labor-law statement may need a source. If you don’t separate these task types, you may treat every AI output the same way, which is exactly how a confident-but-wrong policy detail slips into an employee message.

Try This: Take ten minutes this week and list five recurring HR tasks under each bucket. That list becomes the candidate pool for everything that follows.

Once you have candidates, run each one through the AI Task Fit Screen, four quick checks that tell you whether a task is a fit, a maybe, or a hard no.

Value asks whether the payoff is worth it. Look for tasks where AI can meaningfully reduce time, improve consistency, or help you get unstuck. If AI shaves three minutes off something you do twice a year, the math doesn’t work.

Risk asks what a bad output could cost—and what a careless input could expose. A typo in an internal pipeline update is recoverable; a fabricated credential in a hiring file, a wrong eligibility promise in a benefits note, or a non-compliant line in a termination letter is not. Risk also runs in the other direction: never paste real candidate, employee, medical, accommodation, or personnel data into an AI tool unless it's been explicitly approved for that use, since anything you submit may be stored or used to train the model. Run the HR AI Safety Checkpoint before you start.

Repeatability asks whether the task happens often enough to justify the setup. Recurring work—like a weekly pipeline update or a batch of outreach emails—is usually a stronger candidate because you can reuse the prompt, refine the workflow, and compare results over time.

Human Review asks whether a person can actually sanity-check the output in reasonable time. If you can’t tell whether a policy line is accurate or a credential is real, you can’t use the tool safely, no matter how good the writing sounds. And for anything consequential, legal, or EEO-sensitive, "human review" means escalation to Legal/Compliance, not just you — which changes how fast and how cheaply a task can really be reviewed.

The trap most HR pros fall into is anchoring on Value and ignoring the other three. High value plus high risk plus weak human review is not a pilot, it's a future compliance incident.

Here’s what that sounds like in practice.

• Natalie: I want our first AI pilot to be drafting termination letters. Huge time save for Employee Relations.
• Dan: Value's real, agreed. But run it through the screen with me. What's the cost if it invents a reason or drops a required line?
• Natalie: Could be a legal or EEO problem, plus a confidentiality exposure. Not great.
• Dan: And can someone without Legal review the output and catch that?
• Natalie: Honestly, no. We'd still need Legal to read every line.
• Dan: So Value's high, Risk's high, Human Review's weak. Worth a conversation with Legal someday, but not our first pilot.

Notice Dan didn't kill the idea, he named the framework, walked the checks, and let the score speak. That's the move when someone anchors on a flashy candidate.

Your first AI workflow should be deliberately boring: a task that scores well on all four checks, with low risk if it goes sideways. Recurring internal communication is a classic fit (the weekly recruiting-pipeline status update, an onboarding-checklist draft, a first pass at engagement-survey theme tags) because the value is real, the risk is contained, the task repeats weekly, and you can eyeball the output in under a minute.

Then commit to a success criterion before you start, not after. Something concrete you can measure, like "cuts my pipeline-update drafting time in half across three consecutive weeks with no data corrections needed." Vague criteria like "saves time" let you talk yourself into a pilot that didn't actually work.

The takeaway for this unit: pick the task, not the tool, and let the AI Task Fit Screen tell you which task earns the pilot slot. The next step is a live conversation where you'll pressure-test five candidate HR tasks against the Screen with a manager who's anchored on the flashiest option. Bring the framework by name and walk the checks out loud, that's where the skill actually gets tested.