English
A manager and new hire sit on a couch during an informal 1:1, reviewing a book and tablet together.

What we've learned helping HR teams automate their people programs

What does HR automation actually look like in practice? We've helped hundreds of teams find out. Here's what we've learned along the way.

HR teams have been making imperfect tools work for a long time. They've stitched together HRIS workflows and manual processes, built onboarding programs out of Google Docs and calendar reminders, and kept entire employee communication systems running through personal effort and institutional memory. With the tools they had available, which were often not built for purpose, they made it work.

We've helped hundreds of HR teams automate their people programs, and the desire is always the same. They want to stop spending their time on operational follow-up so they can get back to the strategic, people-centered work they want to do.

Here's what we've learned working with our customers — drawn from our own experience and from the patterns that Julianna Kapjian-Pitt, Pyn's Director of Customer Success, has seen firsthand across hundreds of implementations.

What the "before" actually looks like

After hundreds of implementations, the starting point is almost always the same. The HRIS holds the employee data. Then a patchwork of manual work fills in everything the HRIS can't do.

That patchwork looks like static checklists that employees and managers might ignore. Calendar reminders and Slack DMs sent by hand. A Notion doc people can never seem to find. Workflows that break silently. People Ops copy-pasting emails and chasing managers for tasks.

The period between offer acceptance and Day 1 is almost universally a black hole — multiple customers have used that exact phrase. The new hire hears nothing. The manager isn't prompted to do anything. HR has limited visibility into whether the basics are happening.

And the most time-consuming work is often the manual follow-ups. It's the Slack DM that an HR person sends to a manager to remind them to do something for their new hire. It can feel like a small nuisance, but multiply it across 20 managers and 50 new hires a month, and you've found where the time is actually going.

At Rhino, the People Ops team was running 5 to 10 manual onboardings per week at peak hiring as the company grew from 40 to 230 employees in two years. At Mindbody, Lauren Whitehouse, Senior Corporate Communications Specialist, discovered that an entire cohort of non-US employees hired through third parties had been receiving zero communications. Not a degraded experience. None at all. "Before Pyn, I didn't have a campaign for employees who were being hired through a third party," Lauren told us. "I had a huge swath of the population who was joining the company that wasn't getting onboarding messages."

These aren't edge cases. They're what "before" looks like at most growing companies.

Many employee journeys nail week one and then fade away

One pattern we have seen is that companies put enormous energy into a new hire’s first few days. The welcome email. The Day 1 schedule. The IT setup checklist. And then the employee journey starts to go quiet.

The employee is still figuring out the organization at Day 30. They're still building relationships at Day 60. They might not have had a single structured check-in with their manager since week one. The Senior L&D Program Manager at Carta told us: "The initial experience a new hire has as an employee sets a real expectation around what's ahead. And that has a lasting impression way beyond their first week."

The teams that get this right build the journey out further than feels necessary. Carta runs structured touchpoints at 30, 60, and 90 days plus engagement moments at the conclusion of their onboarding program and key milestones after that. They sent over 3,000 messages to new hires in a single year. He estimated that automating those communications gave him 271 hours back (almost two full months of work!), which he redirected into building an aspiring managers program and revamping their manager onboarding. "I got to do more things strategically instead of operationally because our communication process was more efficient," he said.

Beyond efficiency, this is about what becomes possible when the operational work isn't eating all your capacity.

Managers are the most under-supported part of the equation

This one shows up in almost every implementation. Managers are the single biggest variable in whether an employee has a good experience or a bad one during a transition whether that's a new hire, a promotion, or a return from leave. 

The problem is often twofold. First, managers ignore or are overwhelmed by system notifications. Messages from bots get dismissed. Messages that appear to come from a real person get actioned. That gap alone explains a huge amount of failure in employee lifecycle programs. 

Second, most programs don't deliver the right information to managers at the moment they actually need it. A manager who just got a new hire on their team needs different support than one whose direct report is hitting Day 30, or one navigating a difficult performance conversation. Without that context-specific guidance arriving at the right time, even well-intentioned managers default to doing nothing.

One Manager of Employee Development we work with was direct about why this mattered to her team: "Making sure our managers are engaged in the onboarding process is really important because they play such a critical role in those first 90 days for a new hire and beyond."

MongoDB has also focused heavily on supporting managers. With over 4,600 employees and more than a thousand managers, Anne O'Gara and her L&D team built their entire Pyn program around new manager development. They created a series of automated messages to newly promoted managers, plus parallel messages to each manager's manager, prompting them to support the transition. To date they've delivered over 8,000 pieces of content through that single use case. Kelly Bouzi, L&D Specialist at MongoDB, put it simply: "By automating support for new managers we don't have to think about it constantly. It just runs and that helps a lot."

The goal isn't to automate the relationship between a manager and their team. It's to make sure the manager can best show up for it.

The best programs start small and then become infrastructure

The most common early mistake we see is trying to build the perfect employee journey before sending a single message. Teams arrive with journey maps and stakeholder alignment and content outlines. They want to get it right before anything goes live. Then they hit a wall because the data isn't clean enough to support the complexity they've designed.

As Julianna puts it: "The customers who get the most out of Pyn are the ones who build the right things first. My first question with any new customer is never 'what do you want to build?' It's 'what have you already designed that you're still doing by hand?' That reframe changes everything."

The teams that get to value fastest pick one flow with the cleanest trigger and ship it. For example, a pre-boarding message to a manager or an anniversary reminder. The advantage of this is that it is something they can run, watch, and trust within two weeks of going live. Then they can continue to iterate.

Julianna also notes that the customers that have become the most successful in embedding their employee journeys are the ones who divide ownership early. Instead of one HR person running everything, they bring in Benefits, Revenue Enablement, Talent Acquisition, etc. Each team owns their own flows. 

Lauren at Mindbody described it this way: "Unlimited licenses for Pyn has been a game changer for us, because I have other teams using Pyn now. Before, everything had to filter through me, but now I have a separate enablement team that helps other teams — like customer service, sales, payroll, benefits — get set up in Pyn so they have their own newsletters and programs. I taught them to fish, and now they can just run it on their own."

The benefit of this approach is that you have more teams in the organization thinking about and owning the employee journey. Not to mention that instead of five teams each buying their own point solution, you have one platform with shared infrastructure and distributed ownership. The employee journey map stays coherent even as more teams build on it.

The harder moments are where it matters most

Teams usually start by automating the more predictable stuff like onboarding, anniversaries, compliance reminders. But the moments that matter most in an employee's experience aren't always the predictable ones.

The People Ops team at Rhino told us they started using Pyn's content library during moments that were genuinely hard to navigate, such as communicating during social upheaval, economic uncertainty, layoffs. "Sometimes we think, 'Is it our place to comment on this?'" they shared. "Then you see a resource come through from Pyn and it's a reminder that everyone else is thinking about this."

Arctic Wolf built an entirely parallel communication track for employees joining through an acquisition using personal emails before company emails were provisioned, with separate logic that kept the cohort invisible to standard flows. 

ServiceTitan asked us to help them automate proactive coaching talk tracks for managers the moment a performance rating gets calibrated down so the manager has guidance ready before they deliver the news. We've also seen return-from-leave sequences built because someone on the team went through a bad return experience and decided no one else should have to.

These are some of the tougher moments in an employee’s journey where a well-timed, well-worded communication can change how someone experiences a genuinely difficult moment at work. And they're the ones that only become possible once a team has built enough confidence in the platform to trust it with the hard stuff.

What we'd tell an HR leader who's about to start

Start small, iterate, and cross-collaborate. Trying to build the whole journey before going live can be overwhelming and causes teams to lose momentum. 

Some of our most powerful use cases have come from customers who saw possibilities we hadn't explored yet — an acquisition communication track built from scratch during a live M&A, an internal learning program that went from 25 sign-ups to 290 by rethinking how invitations were sent. That's what this work looks like at its best: a platform and a team that build on each other.

If you're thinking about automating your people programs and want to see how other teams have done it, we'd love to show you.

FAQ

What's the most common mistake HR teams make when starting to automate?

Trying to design the perfect journey before a single message goes out. Teams spend months on alignment, content, and journey maps then stall when the data isn't clean enough to support the complexity they built. Start with one simple, reliable trigger and build from there.

How long does it take to see results from HR automation?

Most teams see time savings within the first 90 days, typically from replacing manual follow-ups and compliance reminders. Broader impact across the full employee lifecycle builds as the program expands and more teams adopt the platform.

What should HR teams automate first?

Something with a clean data trigger and a clear recipient. A pre-boarding message to a manager, an anniversary reminder, or a single compliance nudge are all good starting points. The goal is to ship something you can run, watch, and trust quickly and then use that confidence to build the harder stuff.

Why do managers ignore automated HR messages?

Most system notifications come from bots or apps, and managers have learned to tune them out. Messages that appear to come from a real person, such as a colleague or manager, are more likely to get actioned. That design decision alone has a significant impact on whether your program actually changes behavior.

What does a mature HR automation program look like?

Multiple teams running their own flows independently, with People Ops owning the overall employee journey. Benefits manages open enrollment and reminders. TA handles interview feedback nudges. The platform becomes shared infrastructure across the organization, not a single team's tool.

Can HR teams automate sensitive communications?

Yes, and many teams do. Talk tracks for managers before difficult performance conversations, return-from-leave sequences, acquisition communication tracks — these are all in use today. The sensitive use cases come after teams have built enough trust in the platform to hand it the harder moments.

What's the biggest operational risk after launching an HR automation program?

Losing the person who built it. When one person holds all the institutional knowledge about how the system was designed, any transition creates risk. Document the logic, distribute ownership across teams, and treat your automation program like the infrastructure it is.

How does HR automation work alongside an HRIS?

The HRIS stays as your system of record. Automation uses HRIS data like start dates, promotions, role changes, or tenure milestones as triggers to deliver the right communication at the right moment, through Slack, email, or both. Pyn connects with BambooHR, Workday, ADP, and more.

Is HR automation only useful during high-growth hiring phases?

No. Teams that started with automation during rapid growth consistently find new use cases as hiring slows — holiday and milestone communications, manager enablement sequences, benefits enrollment, sensitive moment support. The value shifts, but it doesn't go away.

How do you measure whether HR automation is working?

Start with time recovered from manual work. Then look at manager response and task completion rates, employee lifecycle coverage (are all cohorts actually being reached?), and whether other teams are adopting the platform. Expansion across the organization is one of the clearest signals that the program has real roots.

Share