AI for HR Teams: 7 Workflows That Pay Back in Week One (2026) | Viktor Blog
Key Takeaways
- HR ops is one of the most underserved targets for an AI coworker. Most HR teams under 200 people are running on tribal knowledge, half-finished spreadsheets, and email threads that nobody can find later. The runbook discipline closes those gaps faster than a new tool would.
- Recurring, multi-tool, low-cost-of-error work pays back fastest. Exit interview synthesis, comp review prep, performance review aggregation, headcount tracking, engagement survey rollups. None of these touch a customer; all of them recur monthly or quarterly.
- Anything that touches a person's compensation, employment status, or legal record stays human. The AI drafts the comp letter; a human always sends. The AI summarizes the exit interview; a human decides what to do about it.
- The HR data spine is usually two tools: an HRIS (Rippling, Gusto, BambooHR, Justworks) and a feedback tool (Lattice, Culture Amp, 15Five). Connect those plus Slack, and the first three runbooks come online inside two weeks.
- HR teams are smaller than they should be at most companies. A 100-person company often has one or two HR people doing the work of four. The time the runbook discipline saves is meaningful enough that the HR team can finally do strategic work instead of report-assembly.
- The biggest risk is the tribal-knowledge gap. If the only person who knows how the comp review actually runs is the HR director, the AI cannot help until that knowledge becomes a runbook. The first month is mostly knowledge capture, not automation.
The HR data spine
The two non-negotiable tools
The HR data spine is two tools.
| Role | Examples |
|---|---|
| HRIS (system of record for people) | Rippling, Gusto, BambooHR, Justworks, Workday, Deel |
| Feedback / performance | Lattice, Culture Amp, 15Five, Leapsome, Officevibe |
Plus Slack as the output. Three integrations cover roughly 80% of useful HR runbooks.
What you do not need on day one
ATS (Greenhouse, Ashby) is for recruiting, which is a separate workflow shape covered in our recruiting post. LMS (Lessonly, Sana) is for L&D, which most companies under 200 people do not have. Comp tools (Carta, Pave) are useful at the comp-review window, not weekly.
Workflow 1: monthly headcount and ramp tracking
Every HR team has a monthly "where are we on hiring" deck or thread, usually built manually the day before the leadership meeting. The runbook builds it on the day of, automatically.
Copy
First Monday of every month at 8 AM Warsaw, post in #people-ops:
- Current headcount from Rippling (active employees, contractors)
- Open roles from Greenhouse / Ashby (count by department, days open)
- Hires made last 30 days (name, role, start date, ramp status)
- Departures last 30 days (name, role, voluntary / involuntary)
- Three-month forecast: open roles + their target start dates
If any role has been open more than 90 days, flag it explicitly.
If voluntary departures exceeded 5% of headcount in the last quarter, ping me first and wait for review before posting.
Post as a Slack thread in #people-ops, draft for review the first two months, auto-post after.
The first month, the HR director reviews and corrects. By month three, the post runs without review. The leadership team gets cleaner, faster headcount data; the HR director gets four hours back.
Workflow 2: exit interview synthesis
Exit interviews produce raw text. Most HR teams collect them in a Google Doc or a Lattice template, which often results in either nobody reading the corpus or one person trying to summarize it manually.
The runbook does the synthesis. Pull all exit interview responses from the last quarter from your feedback tool. Cluster the comments by theme and surface the three most-mentioned themes with representative direct quotes (anonymized). Post a synthesis report to the HR leadership channel.
Why this beats manual synthesis
Manual synthesis suffers from recency bias: the last person to leave dominates the report. The AI clusters across the entire window evenly. Manual synthesis tends to soft-pedal uncomfortable themes; the AI surfaces them as patterns, not as one person's complaint.
What stays human
Decisions based on the synthesis. For example, if the theme is "managers are not giving career feedback," that is a leadership decision.
Workflow 3: comp review prep
Comp review is one of the most painful HR workflows at most companies. HR teams spend two to three days assembling the deck.
The runbook builds the deck in 30 minutes. It pulls from HRIS for current comp and tenure, performance tool for the last review cycle's rating, and comp benchmarks for highlighting outliers.
The runbook does not decide who gets a raise. It produces the analysis for the comp committee to decide.
Workflow 4: performance review aggregation
The HR team aggregates review responses, flags inconsistencies, and prepares the calibration deck.
What the runbook does
The runbook does the aggregation. It summarizes manager ratings, peer ratings, and flags any rating delta.
Workflow 5: engagement survey synthesis
If your team runs quarterly engagement surveys, the runbook reads everything, clusters open responses by theme, and compares current quarter to previous quarter.
Copy
After every Culture Amp quarterly survey closes, within 48 hours:
- Pull all open-text responses
- Cluster by theme
- Count mentions and pull 3 representative quotes
- Compare counts to previous quarter
- Build a Slack thread in #hr-leadership with executive summary
What stays human
The HR director reviews, adjusts, and forwards to leadership.
Workflow 6: onboarding nudges and check-ins
The runbook handles the schedule. It pulls new hires from your HRIS and schedules DMs for check-ins at key intervals like day 30 and day 60.
What stays human
The actual check-in conversation.
Workflow 7: birthdays, anniversaries, and recognition
Pull birthdays and work anniversaries from your HRIS weekly. Post a Slack message with the upcoming week's list.
What stays human in HR
There is a clear list of HR work that should never graduate past Rung 3. High-stakes actions should keep a human in the loop.
| Action | Maximum rung | Why | | --- | --- | | Termination communication | Rung 1 (read-only) | Legal and human cost is too high | | Comp letter delivery | Rung 3 (draft only) | A wrong number sent is unrecoverable | | Performance review delivery | Rung 3 (draft only) | The manager owns the conversation | | Workplace investigations | Rung 1 (read-only) | Legal privilege and confidentiality | | Diversity / pay-equity reporting | Rung 3 (draft only) | Numbers must be human-verified before publication | | Internal celebrations and reminders | Rung 4 (auto) | Low stakes, high frequency | | Headcount and report assembly | Rung 4 (auto) | Mechanical, recurring, no employee impact |
How to start in week one
Week 1: connect and observe
Connect HRIS, performance tool, and Slack. Do not write any runbooks yet. Build trust by having the AI answer ad-hoc questions in Slack.
Week 2: write the headcount runbook
Manually run the monthly headcount post first. Match or fix the process.
Week 3: graduate to auto on the headcount runbook, write the next one
Once the headcount runbook has produced correct drafts, promote it to auto and move to the next workflow.
Week 4 onward: the harder workflows
Comp review prep and exit interview synthesis are highest-value but require more context.
Frequently Asked Questions
Which workflow should we start with?
Start with the engagement-survey rollup or the headcount snapshot. Both are simple and produce useful artifacts quickly.
How do I handle PII?
The AI does not export data outside existing tool boundaries and always anonymizes direct quotes.
What if our HR team is one person?
This is when an AI coworker pays back fastest. It allows solo HR persons to transition from operational tasks to strategic work.
Closing thought
HR is often underserved until something goes wrong. Automating runbooks allows HR teams to reclaim time and focus on strategic initiatives.