The most valuable person in your organisation is probably the quietest

A question lands in the team channel at 10:40 on a Tuesday. Nobody answers it there. Within a few minutes, three people have messaged the same colleague directly: the one who has sat near the window for six years, rarely speaks in meetings and has never presented at an all-hands meeting. She replies to each in a line or two, and the problem goes away.

Ask anyone on that team who knows the most about the subject and they will say her name without thinking. Now look her up in the HR system. Her title is the same as eight other people's, her last review called her "solid", and her skills field is empty or three years old. The organisation depends on her every week and has no record that it does.

Many HR, L&D and delivery leaders will recognise this, and some have lost such a person without knowing why nobody saw her sooner. Finding hidden talent starts with two reasons it stays hidden: expertise is hard to see, and the way organisations measure people makes it harder.

Expertise looks like ease

The first reason is about what good work looks like from the outside. When someone knows a system well, they spot the weak point early and fix it quietly, so nothing breaks. Picture the engineer who reads a deployment plan on Monday, says "that migration will lock the billing table" and gets it reworked. The outage never happens, so nobody writes it up.

In a study of why process improvement programmes fail, MIT's Nelson Repenning and John Sterman found that organisations stuck on fire-fighting end up rewarding and promoting the people who rescue troubled projects, while the work that prevents the trouble goes unrecognised. The title of their 2001 paper in California Management Review comes from an engineer they interviewed: Nobody Ever Gets Credit for Fixing Problems that Never Happened.

That is why real expertise so often looks like nothing. The more fluent someone is, the less effort shows, so a manager reviewing the year sees a calm person with a quiet calendar.

Our systems reward what they can see

The second reason is the tools organisations use to judge people. Each one rewards something other than knowledge, and four of them stand out.

Facetime

Research by Kimberly Elsbach and Daniel Cable, published in MIT Sloan Management Review in 2012, found that people seen at work during normal hours are judged as more dependable, and people seen early or late are judged as more committed, often without the person judging noticing they are doing it. The expert whose best work is a two-line message gets no credit for it, while a colleague seen staying late is read as dedicated.

Visible passion

Harvard Business School research led by Jon Jachimowicz, reported in 2024, found that supervisors are more likely to see extroverted employees as passionate than introverted ones, even when both report similar motivation for their work, because extroverts show their feelings more openly. A calm expert can read as less committed than a more animated colleague.

CVs and reviews

A CV records titles and tenure, and a review records what a manager noticed this year. Neither asks what someone knows, so skills picked up on the job rarely appear. A 2024 World Economic Forum report, drawing on PwC data from 2023, found that 58% of workers believe they have skills that are not clear from their qualifications or job history.

AI inference on activity data

Some tools infer skills from the trail people leave in documents, tickets and code commits. The expert who answers in a two-line message leaves almost none, so the blind spot repeats at scale.

Each of these is a reasonable proxy for something hard to measure. Together they paint a picture in which the loudest, longest-serving and most active people look the most capable. The quiet expert is missing from the data because the system asked her what she knew once, years ago, and never again. The fault lies in how skills systems are designed, which is the argument of the first article in this series: skills data is broken, but not for the reason you think.

What hidden talent costs

When capability is there but unseen, the cost shows up in three places.

The first is the go-to people themselves. If everyone quietly knows who to ask, those few people absorb a growing share of everyone else's questions on top of their own work. Writing in Harvard Business Review in 2016, Rob Cross, Reb Rebele and Adam Grant reported that 3 to 5% of employees generate 20 to 35% of value-added collaborations, and that the colleagues most in demand had the lowest engagement and career satisfaction, with burnout and turnover a real risk. When they leave, their knowledge goes with them.

The second is people whose skills go unused. Gartner's 2024 research found that 1 in 3 employees believe they could have a bigger impact in another role.

Someone who can do far more than their role asks, and sees no sign that anyone knows, is likely to start looking elsewhere. LinkedIn's 2022 Workplace Learning Report found that employees who feel their skills are not being put to good use are 10 times more likely to be looking for a new job. More of the research is collected in our skills statistics playbook.

The third is the cost a CFO will notice first: hiring for skills the organisation already has. If nobody can find the internal candidate, the role is filled from outside, with the fees, the longer ramp-up and a colleague who was passed over. Organisations that work from skills do better here: Deloitte's 2022 research found that skills-based organisations are 107% more likely to place talent effectively. It is a survey, so it shows an association and can't prove that being skills-based causes the result, but it points the same way.

What 55,000 civil servants showed

The clearest sign that the capability is there comes from what happens when an organisation stops guessing and asks its people. When Nigeria's Federal Civil Service did that, it found that capability across the civil service was higher than leaders had assumed. Under Project PASGA, delivered by MuchSkills partner Phillips Consulting, 55,000 civil servants across 46 ministries mapped their skills in MuchSkills.

Project PASGA, Nigerian Federal Civil Service

Job grades and the records on file could see only part of that capability, and it took people describing their own skills to show the rest. These figures come from one MuchSkills deployment, so treat them as one organisation's result. The full story is in the case study on how 55,000 civil servants mapped their skills.

How to identify hidden talent in your organisation

To identify hidden talent in your organisation, stop inferring it from titles and activity. Ask people what they know, make the answers visible to colleagues and keep them current. In practice that comes down to four habits.

Ask people what they know

Let people describe their own skills on a clear scale, including skills that have nothing to do with their job title. It also helps to ask how much they want to use each skill, because the expert who is tired of a topic and the one who wants more of it need different work.

Make it visible to colleagues

A profile only HR can see changes nothing. When colleagues can search it, the right person gets found for the right piece of work. Visibility also keeps the answers honest. Daniel Nilsson, CEO and co-founder of MuchSkills, puts it simply: "Transparency is the best data quality mechanism."

Notice who others go to

Ask teams who they turn to for help on a given topic. Names that come up repeatedly are a signal no review will show you.

Keep it current

A stale skills record misleads the people who rely on it. It stays accurate only if people have a reason to update it, such as being found for work they want to do.

None of this is instant. Self-described skills need a clear scale, and colleagues who can see them, before leaders will trust them. MuchSkills calls this approach Employee-Up. It works without extra monitoring, because the people a record describes get something back from keeping it up to date. Read more about how the Employee-Up approach works.

A question to take back

Think of the person in the opening, the one the whole team asks first. If she resigned on Friday, how long would it take your organisation to learn what she knew, and who would you ask to find out?

If the honest answer is that you would find out after she had gone, the gap sits in what your systems are able to see, and that is something you can redesign. If you would like to see how that works with your own teams, book a demo.