Discovery field guide / Department
How to find AI opportunities in Human Resources
Where should discovery start?
Follow an employee request from first contact to resolution. Look for repeated policy interpretation, document collection, and handoffs between HR, payroll, IT, and managers. Interview the people handling exceptions, not only the HR leadership team. Begin with bounded administrative friction; hiring, promotion, discipline, and other consequential employment decisions need a separate legal, fairness, and accountability assessment.
The shared framework
Fourteen stages, from objective to portfolio.
Every guide uses this sequence to connect a business problem to an accountable investment. Revisit earlier stages when new evidence changes the assessment.
Stage 1: Business Objective
Name the outcome the organization is trying to move, so every later idea has something to be measured against.
Stage 2: Department
Locate the team that owns the objective and the work that feeds it.
Stage 3: Process
Describe how the work actually runs today: steps, handoffs, systems, and exceptions.
Stage 4: People
Capture who performs and depends on the work, and what they know that no document records.
Stage 5: Problem
State the friction in plain terms: delay, rework, error, cost, or risk, with evidence.
Stage 6: Opportunity
Frame a specific improvement that addresses the problem, not yet tied to any technology.
Stage 7: AI/Automation Fit
Compare AI, RPA, IDP, workflow automation, process redesign, and no technology change.
Stage 8: Value
Estimate benefit in the objective's own terms, with assumptions written down.
Stage 9: Feasibility
Check data, systems, skills, and change capacity needed to deliver.
Stage 10: Risk
Surface compliance, quality, security, and adoption risks and the controls they need.
Stage 11: Scoring
Rate each opportunity on the same dimensions so comparisons are consistent and explainable.
Stage 12: Prioritization
Sequence opportunities by score, dependencies, and capacity, with reasons people can challenge.
Stage 13: Investment
Match approved effort to the sequence; people with budget authority decide what gets funded.
Stage 14: Portfolio
Track opportunities over time as a living set: delivered, in flight, waiting, and retired.
Start with one observable journey
Select one employee-service journey, such as a new starter with a payroll exception. Trace the request, policy version, approvals, and follow-up. Compare employees in different locations or contract types so a convenient headquarters example does not become the assumed standard.
Discover work inside HR services and employee lifecycle administration. Do not treat this guide as permission to automate employee selection, assessment, or access to sensitive employee records.
Where to look in the work
Questions that cross policy boundaries
Review redacted service tickets where an answer depends on location, tenure, contract, or policy effective date. Repeated searching across conflicting documents can indicate a knowledge-maintenance problem before an AI opportunity. Record which source HR is authorized to treat as current.
Onboarding and change-of-role handoffs
Walk through missing forms, late approvals, duplicate entry, and unclear ownership between HR, payroll, and IT. Separate coordination failures from language-heavy work. A checklist with explicit ownership may solve a missed account setup without introducing probabilistic interpretation.
Who to interview and what each person knows
Service staff and employees with exceptions
Ask an HR coordinator to reconstruct a recently reopened request. Include an employee or representative with an accessible, consented way to describe the experience. Someone who could not use the self-service portal may expose barriers that ticket counts miss.
Policy, privacy, and payroll owners
Interview the policy owner, payroll specialist, and privacy or employee-relations lead. Clarify which information may be used, who can view it, and when a case must move to a person. Include worker representatives where applicable rather than treating consultation as a rollout detail.
What to ask: follow the evidence
Which fact changes the answer?
Ask: How do you verify the employee's applicable policy? What happened when two policy versions disagreed? Which requests require discretion rather than a standard answer? Ask for a case where the apparently obvious answer was wrong and identify the source that resolved it.
What would make this unsafe to delegate?
Ask who handles grievances, health information, accommodation requests, and contested decisions. How can an employee reach a person or challenge a response? Document necessary confidentiality boundaries and whether a proposed tool could reveal information across teams, managers, or employee populations.
Signals of opportunity, and reasons to look elsewhere
A bounded answer with a maintained source
Repeated navigation to an approved, current policy is a stronger signal than a broad wish for an HR chatbot. Look for clear applicability rules, an accountable editor, and an escalation path. Contradictory source material means the knowledge base needs repair before answers can be trusted.
Rework concentrated at one handoff
Missing onboarding details or repeated payroll queries may indicate a structured validation opportunity. Check whether staff spend time interpreting documents or simply chasing a missing field. Never infer employee performance or sentiment from service interactions merely because the data is available.
How to evaluate what you find
Test differences between employee groups
Use permissioned, minimized examples across relevant languages, locations, and employment arrangements. Check correct policy selection, source citation, accessibility, and escalation behavior. Review differential failure patterns with qualified owners; an average success rate can conceal a group consistently receiving wrong guidance.
Evaluate the service, not just the answer
Compare resolution quality and total handling effort, including correction, complaints, and follow-up. Confirm retention, access restrictions, and the route to human help. If the candidate begins ranking people or influencing employment decisions, stop and reassess scope rather than reusing an administrative pilot's approval.
How to compare, prioritize, and invest
Prefer reversible service assistance
Start with policy-source finding or completeness checks that trained staff can verify. Keep sensitive casework and consequential decisions out of that initial boundary. Where the same problem arises from an outdated policy, fund policy clarification before adding another interface over the confusion.
Make employee outcomes visible
Compare candidates on correct resolution, equitable access, staff capacity, and the effort employees expend getting help. Assign a service owner and a privacy reviewer. Define a pause condition for wrong entitlements, exposed records, or employees unable to reach a person, even if handling time improves.
Turn observations into a comparable opportunity record
Describe the current process before naming a solution. Record the trigger, owner, input, steps, handoffs, systems, output, and exception path. Separate what you observed from what someone recalled and what you still need to verify. A vivid interview story is a useful lead, not proof that every case behaves the same way. Validate it against a sample of ordinary work and difficult exceptions, with the limits of that sample made explicit.
Measure active work separately from waiting. Note the observation period, case mix, frequency, and source of each estimate. Include the receiving team's effort, checking, correction, and escalation so a local improvement does not merely transfer work. Describe the outcome in operational terms before attaching a monetary value. Capacity released is not automatically a budget saving; explain what can actually change and which manager has authority to make that change.
Compare interventions before selecting a tool
If a rule is explicit and the input is structured, test ordinary workflow automation first. If the task repeats a stable interface action, examine RPA and an integration alternative. If the difficulty is reading documents, consider IDP with source checks. AI may help where language or variable evidence requires interpretation, but its output still needs a task-specific acceptance standard. Process redesign or no technology change may be the right answer when policy, ownership, or an unnecessary step causes the problem.
Write down why each alternative would or would not address the observed cause. Do not compare a carefully controlled AI proposal with an artificially weak version of the current process. Include data repair, access approval, integration, training, review, and upkeep in each feasible option. An unavailable prerequisite is a reason to sequence work or pause, not a detail to hide inside a feasibility score.
Agree on a decision, not just a demonstration
Before a trial, name the business owner, evaluator, permitted data, review boundary, and person who can stop it. Define acceptable outputs and failures that must trigger escalation. Use examples held out from development, including missing information and uncommon cases. Compare the complete task with the baseline, including human verification and downstream consequences. Preserve the evidence behind the result so another owner can challenge the conclusion.
Keep value, feasibility, risk, and evidence confidence visible separately. A candidate with an attractive benefit estimate is not ready if its owner cannot obtain the data or operate the controls. Record the decision to investigate, pilot, wait, reject, or retire, with a reason and a condition for revisiting it. After delivery, compare observed results with assumptions rather than leaving the original estimate in the portfolio as fact.
Use the evaluation guide for the evidence standard and the prioritization guide to compare qualified candidates. Your leaders make funding decisions; a score or a discovery tool supplies structured evidence, not investment authority.
Continue through the discovery framework
Browse all departments and industriesRelated practice notes
For focused interview techniques, examples, and scoring detail alongside this field guide:
Map an employee-service process in IntakeOS
Bring a sanitized request journey and the applicable policy sources, not identifiable employee case files. See how IntakeOS can structure the problem, handoffs, and constraints before your HR and legal owners assess a candidate.
IntakeOS supports structured interviews, qualification, and comparison; it does not make funding decisions or replace professional review. Learn about VARA, review the trust page, or explore the platform before sharing sensitive information.
Explore discovery in an IntakeOS demo