How We Cut Employee Onboarding Labor by a Third
Six hours. That's how much time one trainer was spending per new hire during their first two weeks. Multiply that across four teams and 3 to 5 hires per quarter, and the math gets ugly fast.
Earlier in my career, I worked at a mid-size IT services company where the onboarding process was broken for everyone — new hires and trainers alike.
Challenge
Every single new hire went through the same two-week gauntlet.
New hires spent their first two weeks in back-to-back one-hour, one-on-one meetings. Each meeting covered generalized information, delivered inconsistently depending on who ran the session. No structure. No role-specific preparation. Just a firehose of facts and a calendar full of meetings.
The impact went both directions.
New hires left those two weeks overwhelmed and missing critical information they didn't even know they needed.
Existing employees were getting pulled out of their actual work to deliver the same training repeatedly. In the worst cases, a single trainer was losing entire mornings to a single new hire. Most trainers spent less than two hours, but even that added up month after month with no end in sight.
Action
I co-led the redesign with the Operations Manager. I owned the data gathering, the content architecture, and the actual content development. The Ops Manager handled stakeholder alignment and executive buy-in.
Discovery: Figuring Out What Actually Mattered
The first step was figuring out what new hires genuinely needed to know in their first two weeks — and what could wait.
I started with the largest team and worked my way through all four departments. In each meeting, I asked two questions: what does a new person on your team need to know by the end of week two to be functional? And what are we currently teaching them in week one that they don't need yet?
The answer to the second question was the same everywhere: toolset training. Every new hire, regardless of role, was getting the same generalized walkthrough of the company's entire tech stack in week one. A technician and an account manager sat through the same sessions. The training was long because it tried to cover everything for everyone, and it was useful to nobody because none of it was tailored.
That was the structural fix. We moved all toolset training to week two and customized it by role. Week one became foundational: company-wide context, culture, processes. Week two became practical: the specific tools, workflows, and knowledge each role actually needed.
Rebuilding the Content
With the framework set, we rebuilt how the training was delivered.
Shortened the meetings. Every one-hour session got cut to 30 minutes. If it couldn't be covered in 30, it became two sessions or moved to video.
Replaced live sessions with video modules. The information that didn't require a live conversation became short video modules (15 minutes or less) hosted on an LMS. Self-paced. Standardized. Replayable. No more "it depends on who trains you."
Repurposed the freed-up time for relationships. Instead of filling calendars with information dumps, we introduced short Q&A sessions and 15-minute Meet & Greets with supervisors and leadership. The goal shifted from knowledge transfer to personal connection.
We figured out which content should be video versus live by asking a simple question: if you were going through this training again, would you rather watch a recording at your own pace, or talk to someone? The answer was obvious for most topics. The nuanced, relationship-driven stuff stayed live. Everything else became a module.
The Pushback
Not everyone was on board immediately. Some trainers argued that creating pre-built video content was a lot more work than just jumping on a call. They were right about the upfront effort. But they were looking at the cost of one onboarding cycle, not twenty.
Result
The redesign had measurable impact across all four teams:
- Ops Manager time cut from 6 hours to under 2 per onboarding cycle — the highest-cost resource freed first
- First solo ticket by week 3, down from week 4 or 5 under the old process
- Total training labor reduced 30–40% across all teams
Takeaway
Onboarding isn't a knowledge dump. It's the first product experience your employees have with your company. When you stop treating it like a calendar-filling exercise and start treating it like a designed experience, everything downstream improves.
One honest reflection: I should have assigned video content creation to a single person who was good at it. Instead, we distributed the work across multiple people. The quality was inconsistent, which meant rework and longer turnaround to get everything finalized. The content got there eventually, but a dedicated creator from the start would have saved us weeks.
If your onboarding process feels like a chore for everyone involved, the fix probably isn't a better schedule. It's a harder question: what are you teaching in week one that nobody needs until week three?
If this sounds familiar, I'd be happy to compare notes. Fixing broken processes is what I do.