For a while, our hiring reports looked pretty good.
We had open positions.
We found candidates.
Offers were accepted.
New people started.
Every month, we could point to a number and say:
“We hired 18 people.”
That sounded like progress.
Then someone asked a much less comfortable question:
“How many of those 18 people are still here?”
We didn’t have the answer ready.
Once we found it, the way we measured hiring changed.
We Were Measuring the Beginning of the Story
Our old hiring number answered one question:
How many people started?
That’s useful.
But it doesn’t tell me whether those hires solved the problem that caused us to recruit in the first place.
Suppose we need five people.
We hire five.
Three leave quickly.
We hire three replacements.
If I only count hiring activity, I can report eight successful hires.
Operationally, however, I’m still trying to stabilize five positions.
Those are two very different stories.
We Added a 30-Day View
We started simply.
For every group of new hires, we asked how many were still with us after approximately 30 days.
Immediately, differences appeared.
Some teams retained almost everyone.
Other areas consistently lost people early.
That was far more interesting than the total number of hires.
Then We Looked at 60 and 90 Days
Thirty days told us about the earliest part of the experience.
Sixty and ninety days gave us a wider picture.
A person might get through the first few weeks and then decide the role isn’t right.
Maybe the actual schedule becomes clearer.
Maybe workload changes after training.
Maybe expectations increase.
Maybe the relationship with the manager becomes more important.
By looking at several checkpoints, we could see when the problem was appearing.
One Department Looked Great Until Day 60
This was one of the biggest surprises.
The department had no obvious recruiting problem.
Candidates accepted offers.
People started.
The first few weeks usually went fine.
Then departures increased.
That told us something.
The problem probably wasn’t simply attracting candidates.
Something was happening after they arrived.
So we stopped asking recruiting to solve it alone.
We Compared Hiring Source With Retention
Another interesting question was:
“Where are our longer-lasting hires actually coming from?”
We had always looked at which sources produced the most candidates.
That’s not necessarily the same as producing the best match.
A source generating 100 applicants can look impressive.
But if another produces 20 candidates who are much more likely to stay, volume alone doesn’t tell the full story.
We started caring more about what happened after the hire.
We Found a Position That Was Constantly Being Refilled
At first glance, the position didn’t stand out.
There was usually someone in it.
But when we reviewed the history, we realized we’d hired for essentially the same seat several times.
That meant our hiring team had repeatedly succeeded at filling the vacancy.
The organization had repeatedly failed to keep it filled.
That’s an important distinction.
We Calculated the Rehiring Loop
I started thinking about positions in terms of cycles.
Healthy pattern
Vacancy → hire → stable employee.
Expensive pattern
Vacancy → hire → early departure → vacancy → hire → early departure.
The second pattern creates work everywhere.
Recruiting starts again.
Managers interview again.
Someone handles the administrative steps again.
Coworkers help another new person again.
Training restarts.
Productivity resets.
A position can quietly consume a huge amount of organizational energy without ever appearing completely vacant for very long.
Job Titles Weren’t Enough
Another mistake was grouping everything under broad titles.
Two people could technically have the same title while experiencing very different jobs.
Different location.
Different manager.
Different shift.
Different customer volume.
Different workload.
Different team.
Once we added more context, several patterns became much clearer.
Manager Became an Important Data Point
We were careful with this.
Turnover by manager can easily become an unfair ranking system.
That’s not what we wanted.
Instead, we used it as a diagnostic question.
If two managers oversee similar roles but their early-retention patterns are dramatically different, I want to understand why.
Maybe one has developed an excellent first-week routine.
Maybe one team has a different workload.
Maybe the schedules aren’t comparable.
Maybe one manager needs additional support.
The number tells me where to investigate.
It doesn’t automatically tell me who to blame.
We Asked What Candidates Were Told
This became one of my favorite parts of the review.
We compared the recruiting conversation with the actual job.
Did candidates understand the schedule?
Did they understand the pace?
Did they understand physical requirements where relevant?
Did they know what a normal day looked like?
Were we selling the opportunity so aggressively that we were avoiding the difficult parts?
A candidate who understands the reality and still accepts may be a better match than someone who discovers the reality during week two.
We Started Talking About “Expectation Debt”
That’s the term I use for information we avoid explaining early because we don’t want to discourage someone.
Eventually, the truth arrives anyway.
The schedule is still the schedule.
The workload is still the workload.
The difficult customer situations still exist.
The job still requires whatever it requires.
If we hide those realities during hiring, we’re not eliminating them.
We’re delaying the conversation until after we’ve invested time in bringing someone into the company.
Early Departures Became Their Own Category
We stopped treating every departure identically.
Someone leaving after six years and someone leaving after six weeks may tell us very different things.
Early departures made us examine:
- Recruiting expectations
- Selection decisions
- First-week experience
- Training
- Manager communication
- Scheduling
- Role clarity
Longer-term departures could point toward completely different issues.
Separating them made our analysis much more useful.
We Looked for Cohorts
Instead of mixing everyone together, we started grouping hires.
For example:
People hired in January.
Then we followed that group.
How many remained after 30 days?
60?
90?
We could compare that with February or March.
Now we could see whether changes we made were actually associated with a different result.
One Improvement Looked Small but Mattered
A manager changed how they described the first month during interviews.
Nothing dramatic.
Candidates received a more realistic explanation of the schedule, workload, and learning period.
The number of people accepting offers didn’t suddenly explode.
That wasn’t the goal.
What mattered was whether the people who accepted had a clearer idea of what they were joining.
Sometimes better hiring means fewer surprises, not more candidates.
Trion Solutions Can Add Context Beyond the Recruiting Number
An HR relationship such as Trion Solutions can be useful when a company wants to look beyond simply filling positions.
Hiring touches several parts of the organization.
Recruiting.
Management.
Workplace expectations.
Documentation.
Retention.
Employee relations.
Looking at those pieces together can reveal that what appears to be a recruiting problem actually begins somewhere else.
But the company has to bring meaningful information to the conversation.
“Hiring is difficult” is broad.
“We’re losing a disproportionate number of people in this position between days 45 and 75” gives us something much more specific to investigate.
Our Hiring Scorecard Became More Useful
I don’t need fifty metrics.
I’d rather have a small number that lead to good questions.
New Hires
How many people started?
30-Day Retention
How many remained?
60-Day Retention
Where do we begin seeing departures?
90-Day Retention
Are hires becoming stable members of the team?
Repeat Vacancies
Which positions keep reopening?
Early Departures by Area
Are certain locations, roles, shifts, or managers showing patterns?
Expectation Gaps
What do departing employees say surprised them about the actual job?
That’s already enough to change the conversation.
We Stopped Celebrating a Filled Position Too Early
I still think filling an important vacancy deserves recognition.
Recruiting can be difficult.
Finding the right person takes work.
But now I see the start date as a milestone rather than the finish line.
The real question is whether we’ve created a good match between:
Person → role → expectations → manager → workplace.
That takes time to reveal itself.
The Number 25 Can Mean Two Completely Different Things
Imagine two companies each report:
“We hired 25 people this quarter.”
Company A needed approximately 25 people and most of them remained.
Company B needed 12 people but repeatedly replaced early departures.
Same hiring number.
Completely different operational reality.
That’s what our old reports were hiding from us.
They weren’t wrong.
They were incomplete.
Now I Ask What Happened After the Hire
Whenever someone shows me hiring volume, my next questions are predictable.
How many stayed?
Where did people leave?
When did they leave?
Are we repeatedly hiring the same position?
What did those people expect when they accepted?
What changed after they started?
Those questions turned hiring from a counting exercise into something much more useful.
Because our goal was never actually to hire as many people as possible.
Our goal was to build teams that didn’t require us to start the same search again a few weeks later.