Capability Hoarding: Your Company Has the Skills It Needs — It Just Can't Find Them

A fintech company spends four months and a recruiter's fee hiring a data engineer with Kafka experience. On her second week, she discovers that someone in the risk team built the company's first Kafka pipeline three years ago, and a QA analyst runs a Kafka study group on weekends. Nobody in talent acquisition knew. The capability was never missing. It was hidden.

What we mean by capability hoarding

We use 'capability hoarding' to describe the organisational condition where skills and know-how exist inside a company but are unavailable where needed — because they are invisible, locked inside a team, or deliberately held back. It is a cousin of talent hoarding: talent hoarding traps people; capability hoarding traps what they know. The term is ours, but each part of the mechanism is well studied.

Three research streams behind it

Why this matters more now

The World Economic Forum's Future of Jobs Report 2025 estimates that around 39% of workers' core skills will change by 2030. When skill needs move that quickly, external hiring cannot keep up on cost or speed. Companies that can see and redeploy the capabilities they already have gain a structural advantage. Those that cannot will keep paying market premiums for skills sitting in their own org chart.

Five signs your company hoards capabilities

• New hires regularly discover internal experts after they join
• Skills data comes only from job titles or outdated CV uploads
• Project staffing happens by who the manager already knows
• Internal experts are rarely thanked or credited for helping other teams
• The same problems are solved separately in multiple departments

How to unlock hidden capability

Limits and caveats

• Skills inventories decay quickly; without upkeep they become another hidden store of outdated data.
• Not every hidden skill should be redeployed — people may not want to use a skill they no longer enjoy.
• Internal marketplaces need manager buy-in, or they trigger talent hoarding instead.

Why knowledge gets stuck

Gabriel Szulanski (1996) studied the transfer of best practices inside companies and called the problem 'internal stickiness'. Surprisingly, the biggest barriers were not motivation. They were the receiving team's lack of absorptive capacity, causal ambiguity — nobody could explain exactly why the practice worked — and a difficult relationship between the source and the recipient. Capabilities get stuck even when everyone wants to share them.

Sometimes the stickiness is deliberate. Connelly, Zweig, Webster and Trougakos (2012) defined 'knowledge hiding' as an intentional attempt to withhold knowledge a colleague has asked for. They identified three forms: evasive hiding (promising to help and not doing it), playing dumb, and rationalised hiding (explaining why you cannot share). Low trust and competitive climates make hiding more likely.

The weak-tie problem

Morten Hansen (1999) showed that weak ties between business units help teams find useful knowledge quickly, but strong ties are needed to transfer complex knowledge. A company can know that someone somewhere has solved a problem and still be unable to use the solution, because it takes a close working relationship to pass on know-how that is not written down.

Building a skills map that people actually use

1. Start with critical skills only — the 20 to 30 capabilities the strategy depends on — rather than a catalogue of thousands.
2. Use evidence, not self-rating alone: projects delivered, certifications, peer endorsements.
3. Make it useful to employees: profiles should lead to projects, gigs, and roles, or people will not update them.
4. Review quarterly: skills maps go stale quickly.

Rewarding reuse

• Recognise people whose methods are adopted by other teams.
• Count mentoring and internal training in performance reviews.
• Let teams borrow experts for short, funded gigs without long approval chains.
• Celebrate 'we reused' stories as loudly as 'we invented' stories.

• Critical skills are defined and mapped.
• Employees can find experts outside their team within a day.
• Sharing knowledge counts in reviews.
• Short internal gigs can be approved quickly.

Worked case: the only person who understood billing

For six years, one operations lead has been the only person who fully understands how the billing system handles refunds, discounts and tax. Nothing is written down. When she takes two weeks of leave, refunds pile up. When she is asked to document the process, she says she is 'too busy' — and she is. But she also knows that this knowledge is why she is protected in every reorganisation.

Both points are reasonable from where she stands. The company has made her knowledge her job security, so sharing it feels like giving it away. The fix is not to blame her. It is to make sharing the safer choice.

How to make sharing safe

1. Say clearly that documenting critical knowledge will be recognised in her review and pay.
2. Give her protected time — for example, half a day a week for a set period — to teach a named second person.
3. Give her a new, visible responsibility once the knowledge is shared, so she is not left with less to do.
4. Measure success as 'two people can do it', not 'a document exists'.

A simple key-person risk map

Common mistakes

• Asking for documentation without giving time to write it.
• Rewarding heroes who fix crises, but not people who prevent them.
• Running layoffs that remove the people who shared knowledge and keep the people who hoarded it — which teaches everyone the wrong lesson.

What each role can do

• Leaders: list your ten most important processes and name the backup person for each.
• HR: add 'knowledge shared' to promotion criteria for senior roles.
• Managers: rotate who handles critical tasks, even when it is slower in the short term.