A leader identifies a capability the organization needs.
Maybe it's data analytics. Project management. AI expertise. Process improvement. Change management. A particular industry specialization. Experience implementing a certain technology.
The need is legitimate, so the organization does what organizations naturally do.
It starts looking outside.
A job gets posted. Recruiters begin searching. Leaders ask their networks for referrals. Perhaps a search firm gets involved. Months can pass while everyone talks about how difficult it is to find the right talent.
Meanwhile, somewhere else in the organization, an employee may already know how to do much of what everyone is searching for.
Nobody knows it.
That's an interesting problem.
Organizations invest enormous amounts of money attracting talent, yet many have surprisingly limited visibility into the capabilities of the people already on their payroll.
They know employees' job titles. They know where they report. They know what positions they were hired to perform.
But do they actually know what their people can do?
Those are not necessarily the same thing.
A Job Title Tells You Less Than You Think
Job titles are useful organizational shorthand.
When someone says “financial analyst,” “HR manager,” “operations director,” or “marketing specialist,” we immediately form a general picture of what that person probably does.
But titles are containers.
People are much more complicated.
The employee sitting in Finance may have led a major technology implementation at a previous employer. Someone in Operations may have a background in data analytics. A marketing employee may be an excellent project manager. An HR professional may have significant merger integration experience. An administrative employee may know more about a particular customer process than almost anyone in the company.
None of that necessarily appears in the employee's current title.
Some of it may not appear anywhere the organization routinely looks.
That's because most organizations are designed to track positions rather than capability.
We know where the employee sits.
We may know surprisingly little about what they could contribute somewhere else.
We Hire the Resume and Then Forget It
Think about how much information organizations collect during recruiting.
Candidates submit resumes containing years of experience, previous positions, projects, certifications, accomplishments, industries, technologies, and specialized skills.
Interviewers spend hours exploring that background.
Then the employee gets hired.
A few years later, the organization often knows them primarily by the job they're doing now.
The resume that helped them get hired may be sitting in an applicant tracking system nobody has looked at since their first day.
Meanwhile, the employee continues learning.
They complete certifications. Lead projects. Pick up skills outside their formal role. Volunteer for community organizations. Serve on boards. Develop expertise through hobbies or side interests. Work with technologies that didn't exist when they were hired.
The organization knows some of this.
Managers know some.
Coworkers know some.
The employee knows all of it.
But the enterprise rarely has a complete picture.
So when a new capability is needed, leaders look outward because external talent is often easier to search than internal capability.
There is something slightly ironic about that.
We may know more about candidates we've never met than employees we've been paying for ten years.
Organizational Structure Can Hide Talent
Traditional organizational structures make the problem worse.
Departments are designed to create clarity and accountability. That's important. But they also create boundaries around how people are perceived.
Finance people belong to Finance.
Technology people belong to Technology.
Operations people belong to Operations.
Once someone is placed inside a particular organizational box, leaders outside that box may have very little visibility into them.
The larger the organization becomes, the more pronounced this can be.
An executive may say, “We don't have anyone with that experience,” when what they really mean is, “I don't know anyone with that experience.”
Those statements sound similar.
Strategically, they're very different.
The first describes a capability gap.
The second describes an information gap.
Before spending months and considerable money solving the first, it might be wise to rule out the second.
Your Best Candidate May Not Look Like the Job Description
There is another complication.
Even when organizations search internally, they often look for someone who already resembles the position they're trying to fill.
If the opening is for a director, we search for another director. If the job requires five particular skills, we search for someone who can demonstrate all five. If the person has spent their career in another function, we may assume they aren't qualified.
That's understandable.
It's also how organizations can overlook adjacent capability.
Suppose an employee possesses 70 percent of what a future role requires and has repeatedly demonstrated the ability to learn quickly. The organization could invest in developing the remaining 30 percent.
Instead, it spends six months looking externally for someone who already possesses 100 percent.
Then the external candidate arrives and spends another six months learning the organization.
Which option was actually faster?
There isn't one answer. Some capabilities genuinely need to be purchased from outside, particularly when the organization needs expertise it simply doesn't have.
But “not ready today” and “not capable of becoming ready” are very different judgments.
Organizations that can't distinguish between them may be overlooking significant internal talent.
Capability Doesn't Always Need to Become a New Job
This is where the conversation gets even more interesting.
When organizations identify a capability need, the default response is often to create or fill a position.
But perhaps the organization doesn't need an entire new job.
Maybe it needs a capability for six months.
Perhaps it needs someone to contribute 20 percent of their time to a strategic project. Maybe a cross-functional team needs a particular expertise. Perhaps an employee could temporarily rotate into another function. Maybe two people together possess the combination of capabilities the organization is trying to find in one external hire.
This requires thinking about talent somewhat differently.
Instead of asking only, “Who occupies this job?” we begin asking, “Where does the capability need to flow?”
That's a much more flexible way to think about a workforce.
It also reflects how work is increasingly happening. Strategic problems rarely remain neatly inside functional boundaries. A transformation project may require technology, operations, finance, change management, communication, and customer expertise simultaneously.
The organization may already employ all of those capabilities.
The problem is getting them into the same room.
Managers Can Accidentally Become Talent Gatekeepers
Internal capability also runs into a very human organizational issue.
Managers don't like losing good people.
That's understandable.
If someone is reliable, highly capable, and knows the work exceptionally well, a manager may not be thrilled to see them move to another department or spend part of their time on an enterprise project.
The manager experiences the loss immediately.
The organization experiences the benefit somewhere else.
This creates an interesting tension.
What's best for the department may not always be what's best for the enterprise.
An organization can say it values internal mobility while unintentionally rewarding managers for holding onto their strongest employees.
Employees learn this quickly.
They stop expressing interest in opportunities. They apply for jobs quietly. Or they conclude that moving outside the company is easier than moving inside it.
Then the organization loses the capability entirely.
There's a certain absurdity in watching an employee leave for a better opportunity elsewhere while another department in the same company is paying a recruiter to find someone exactly like them.
Yet it happens.
Hidden Talent Creates a Retention Problem Too
Capability visibility isn't only about filling jobs faster.
It's also about retention.
People want to use what they know.
An employee may have valuable expertise that has little opportunity to surface in their current role. If nobody asks about it, recognizes it, or creates opportunities to use it, that capability gradually becomes invisible.
The employee may eventually conclude that the organization doesn't see what they can contribute.
Another employer might.
This is one reason career conversations should probably go beyond, “Where do you want to be in five years?”
A more useful conversation might explore what the employee knows how to do that the organization isn't currently using.
What kind of problems do they enjoy solving? What experience from earlier in their career rarely gets used now? What have they learned recently? What kind of work would they like more exposure to?
Managers may discover capabilities they didn't know existed.
And employees may discover opportunities they didn't know the organization had.
AI Makes Skills More Visible—and More Difficult to Define
AI is accelerating this conversation because jobs themselves are changing.
As technology takes over portions of existing work, the combination of capabilities required in a role can shift surprisingly quickly.
A position that once emphasized production may increasingly require judgment. A role built around gathering information may shift toward interpreting it. Employees may need stronger business understanding, technology fluency, critical thinking, communication, or problem-solving ability even though their job title remains unchanged.
That makes relying exclusively on traditional job architecture increasingly difficult.
Two employees with the same title may possess very different capability portfolios.
And two employees with completely different titles may have more overlapping skills than anyone realizes.
AI can potentially help organizations identify those patterns, but technology isn't the entire answer.
A beautifully designed skills database filled with outdated information is still an outdated database.
Employees need reasons to keep information current. Managers need to use it. Leaders need to think beyond departmental boundaries.
Otherwise, we've simply created another system containing information nobody looks at.
Don't Turn Everyone Into a List of Skills
There is a caution here.
As organizations become more interested in skills-based workforce planning, it's tempting to reduce people to inventories.
Employee A has these twelve skills.
Employee B has these eight.
Search the database, find the skill, assign the person.
Human capability doesn't work quite that neatly.
Experience matters. Context matters. Judgment matters. Motivation matters. The ability to apply a skill in one environment doesn't automatically mean someone can apply it equally well in another.
And employees aren't interchangeable pieces that can simply be moved wherever an algorithm identifies a match.
The purpose of better capability visibility isn't to turn people into searchable inventory.
It's to improve organizational decision-making.
Leaders should have a better understanding of what the workforce can actually do, where critical capability is concentrated, what can be developed, and where genuine gaps exist.
That's intelligence, not inventory.
External Hiring Still Matters
None of this is an argument for filling every position internally.
Organizations need outside talent.
External hires bring capabilities that may not exist internally. They bring different experiences, perspectives, networks, and knowledge from other organizations and industries. Sometimes the fastest and smartest way to acquire a capability is simply to hire it.
The danger is assuming external hiring is necessary before understanding internal supply.
A good workforce decision should be able to answer both sides of the equation.
What capability do we need?
And what capability do we already have?
Only then can leaders intelligently decide whether to build, buy, borrow, automate, redeploy, or combine resources in some other way.
Without the second question, the organization is planning with half the information.
Look Beyond the Usual Suspects
Every organization has people who become known as high performers.
Their names surface when special projects appear. Executives know who they are. Managers recommend them. They receive development opportunities that create even greater visibility.
That's generally deserved.
But capability can exist outside the usual talent circles.
A quieter employee may have extraordinary expertise. Someone whose performance is solid but not spectacular in their current job may thrive in different work. An employee in a support function may understand an operational problem better than the people formally assigned to solve it.
Talent visibility and talent capability aren't always the same thing.
If organizations continually give opportunities to the people who are already visible, they learn more about those employees while everyone else remains comparatively unknown.
Eventually, leadership can mistake familiarity for the full extent of the talent pool.
Before You Say “We Don't Have the Talent”
Executives regularly hear some version of this sentence:
“We don't have the talent we need.”
Sometimes that's absolutely true.
The strategy requires capabilities the organization hasn't developed. The labor market may be tight. Technology may have changed faster than the workforce. New business opportunities may require expertise nobody internally possesses.
Those are real workforce challenges.
But before accepting that conclusion, there's another question worth asking.
How do we know?
Do we understand the experience employees brought with them when they joined?
Do we know what they've learned since?
Can we see capabilities outside their current job descriptions?
Do managers share talent across organizational boundaries?
Can employees find internal opportunities without leaving the company?
Do we distinguish between someone who lacks a capability today and someone who could develop it relatively quickly?
Most importantly, when a new business problem emerges, can the organization identify who already knows something about solving it?
If the answer to those questions is unclear, the organization may have a talent shortage.
Or it may have a talent visibility problem.
Those require very different solutions.
The next time a leader says, “We need to go find someone who can do this,” it may be worth looking around before looking outside.
Because the talent you need could already be working for you.
You just may not know it yet.
