Finding a Unicorn Shouldn’t Be Your Succession Plan
Written by Damien Richburg
What a 22-year payroll veteran’s retirement revealed about institutional knowledge, outdated processes, and the challenges of replacing experience.
For 22 years, Kathy made sure people got paid.
She was a key member of a small payroll team supporting a large organization. During her tenure, the company grew, its workforce expanded, and the demands on payroll became increasingly complex.
Through it all, Kathy kept things running.
Then she decided to retire.
The organization celebrated her years of service, wished her well, and began looking for someone to take her place.
That’s when they discovered just how difficult replacing her would be.
The Work Behind the Work
Over two decades, Kathy had become responsible for far more than anyone fully appreciated.
There were processes she understood, exceptions she knew how to handle, and responsibilities that had gradually become part of her daily routine as the organization evolved.
When something needed attention, Kathy handled it. If a problem appeared, she knew where to look. When the business changed, she found ways to keep payroll moving.
And because the work kept getting done, there was little reason for anyone to question what was happening behind the scenes.
Until Kathy wasn’t going to be there anymore.
Now the organization needed to understand not only what she did, but how she did it, why she did it that way, and what would happen if those activities stopped.
That’s a much bigger exercise than writing a job description.
Organizations that plan for succession tend to uncover this kind of institutional knowledge long before a retirement announcement arrives, and building team depth through succession planning explains how to start.
When the World Changes Around a Job
There was another complication.
The payroll profession had changed considerably during Kathy’s tenure.
Technology had advanced. Systems had become more sophisticated. Processes that once required significant manual effort could increasingly be automated or managed through integrated platforms.
But Kathy had developed an effective way of accomplishing the work using the tools and knowledge she already possessed.
She didn’t necessarily need to learn every new system to continue delivering the results the organization expected.
That wasn’t a failure on her part.
She had been asked to keep payroll running, and she did.
The challenge appeared when the organization needed someone else to do it.
They were searching for a professional who understood modern payroll practices but could also navigate processes that had developed over more than two decades.
Some of those processes required skills newer payroll professionals rarely needed anymore.
And some of the capabilities candidates brought to the table weren’t reflected in the company’s existing approach.
The organization wasn’t simply replacing an employee.
It was trying to replace 22 years of accumulated knowledge, judgment, and adaptations to a business that had grown around her.
We Found the Unicorn
My team had the opportunity to work on this search.
And we found someone.
A person with the unusual combination of experience, technical knowledge, and adaptability needed to step into that environment and keep things moving.
I’m proud of that outcome.
But the experience reinforced something I think business leaders need to consider.
Unicorns are rare for a reason. They should be the exception, not the foundation of your hiring strategy.
The fact that we could find someone capable of navigating that environment didn’t mean the organization should continue depending on such an unusual combination of skills.
The hire addressed the immediate need.
The larger opportunity was to make the organization less dependent on finding another person just like Kathy.
Roles that depend on one rare combination of skills are a big part of the reason some roles are so much harder to fill than others, and what actually fixes the problem.
The Work That Comes After the Hire
I see two important priorities coming out of a situation like this.
First, make the knowledge part of the organization, not just the individual.
Teams need to document critical processes in a way that someone unfamiliar with their history can understand.
Not simply a checklist of tasks.
People need to understand what happens, why it happens, what exceptions exist, and what decisions need to be made when things don’t go as expected.
And that documentation needs to reflect how the work is actually performed.
A process sitting in a folder that nobody follows doesn’t provide much protection.
The goal is continuity, so the organization can grow, change, and transition responsibilities without depending on one person’s memory.
Second, question whether the process still makes sense.
Just because something has worked for 22 years doesn’t mean it’s the best way to do it today.
Leaders should examine manual processes. They should evaluate repetitive activities for automation. Redundant steps should be identified, and systems should be optimized to support the size and complexity of the organization.
That doesn’t mean automating everything.
Some activities require judgment, experience, and human oversight. Those are precisely the capabilities organizations should be protecting and developing.
But there’s little value in asking highly capable people to spend their time maintaining unnecessary complexity simply because that’s how the work has always been done.
Especially when the organization expects to continue growing.
Developing people from within is one of the most practical ways to spread that knowledge, and building an internal talent pipeline shows what that looks like in practice.
A Successful Hire Doesn’t Always Mean the Problem Is Solved
This is where I think recruiting can provide value beyond introducing qualified candidates.
The hiring process forces organizations to examine what they need, what the market can provide, and whether those two things are aligned.
Sometimes that examination confirms the original requirements.
Other times, it reveals that the position has evolved beyond its original design.
Or that the organization has become dependent on knowledge it hasn’t documented.
Or that the systems supporting the work haven’t kept pace with the business.
Finding the right person matters.
But so does understanding the environment you’re asking that person to succeed in.
Otherwise, you may make a great hire today while leaving the same underlying challenge for someone to solve five or ten years from now.
When a position has quietly outgrown its original design, the hidden cost of unclear roles shows where hiring decisions start to break down.
What Kathy Really Left Behind
I don’t see Kathy’s story as one about outdated skills or an employee who should have done things differently.
For 22 years, she helped an organization navigate growth while keeping one of its most important functions operating.
That’s meaningful.
But her departure revealed how much the organization had come to depend on her individual knowledge and the processes she’d developed along the way.
Fortunately, we were able to find someone with the rare combination of skills needed to step in.
Not every organization will be so fortunate.
And even when you are, finding that person shouldn’t be the end of the conversation.
It should be an opportunity to understand what made the search so difficult in the first place.
Finding the unicorn solved the hiring problem.
Building an organization that doesn’t need another one solves something much bigger.
Related Articles