How to Actually Spot and Develop Untapped Ability in Your Team

Most managers and creative leads have the same problem. They're looking at the same five people for everything while everyone else stays silent. The usual advice is "just ask people what they want to do." That works about as well as you'd expect. People don't know what they're good at until they've done it at least once. And they won't volunteer for something that doesn't look like a promotion or a pay raise. I've seen this play out in engineering orgs, marketing teams, and content production shops. The pattern is always the same. Someone has a skill nobody knows they have. It shows up in small ways first — a spreadsheet they built that solved a recurring problem, a way of explaining things that makes meetings half as long, a side project they mentioned once and then never talked about again.

Unleashing Susan Babeys Hidden Talent The Multifaceted Genius You Need To Know

The core idea here is straightforward. You need a system that surfaces what people can do without relying on self-reporting. Self-reporting is unreliable because most people underestimate themselves or confuse interest with ability. A software developer might love writing documentation but not realize that writing clean docs is actually a rare and valuable skill. A designer might casually redo a layout in an hour and never consider that speed and visual judgment are marketable talents. What I use is a combination of three things. Observation, low-stakes trials, and structured reflection. They sound basic because they are. The trick is doing them consistently instead of waiting for a performance review cycle. Here's how the observation part works in practice. Keep a running note, just a simple text file or a shared doc where you jot down moments that stand out. Not performance feedback. Specific moments. When someone fixed something nobody else could see. When they explained a concept in a way that made the room quiet. When they volunteered to redo work that wasn't their problem. These moments matter more than annual ratings. They are data points. I've found that after about six weeks of collecting these notes, patterns become obvious. The person who always reorganizes shared drives has operational instinct. The one who always catches tone issues in copy has editorial judgment. The one who quietly mentors junior staff has teaching ability. Once you identify a pattern, the next step is a low-stakes trial. This is where most people fail because they either don't try or they throw the person into the deep end immediately. Neither approach works. You need a test that costs almost nothing if it fails but reveals a lot if it succeeds. For example, I once had a team member who kept building automated reports in her spare time. I noticed she was the person everyone asked when Excel broke. Instead of just praising her or giving her more of the same data entry work, I asked her to build a single dashboard for a project that was already happening. Not a big project. One dashboard, two weeks, no pressure. She shipped it in four days. It turned out her hidden talent was data visualization and stakeholder communication through dashboards. She'd never considered herself a "data person" because she didn't come from an analytics background. But the skill was there. We reassigned her to a role that used that talent daily. Productivity went up, engagement went up, and we stopped losing people to burnout from doing work they weren't suited for. The structured reflection piece is where the process gets formal enough to scale. Every quarter, have each person fill out a simple form that asks three questions. What work did you lose track of time doing this quarter? What problem did you solve that surprised you? If you could take on one new type of project, what would it be? The answers to these questions are more honest than anything in a standard self-assessment because they force specific instead of generic "I'm a team player" answers. I've also learned what doesn't work through painful experience. One approach I tried was running personality assessments like Myers-Briggs or StrengthsFinder and then assigning people based on results. That was a mistake. Those tools measure how people think, not what they can do. A high "strategic" score doesn't mean someone can actually build strategy. It means they like thinking about the future. The correlation between assessment scores and actual workplace performance is weak enough that relying on them for talent allocation is basically guesswork. Another pitfall is assuming hidden talent equals hidden interest. Some people have abilities they don't enjoy using. I once identified someone with exceptional writing ability who only used it because they enjoyed technical documentation. When I pushed them toward content marketing, they hated it. The talent was real but the fit was wrong. The workaround was simple. I asked about enjoyment separately from ability. Can you do this? Do you want to do this? Those are two different questions and people often conflate them. The limitations of this approach are real. It doesn't replace good hiring practices. It doesn't help if the organizational structure doesn't allow for role flexibility. And it won't surface anything if people are genuinely disengaged or burned out — in those cases, the hidden talent might be buried under exhaustion rather than lack of opportunity. I've also found that this method is less effective in very large teams where you can't reasonably observe fifty people directly. In those cases, you need to delegate the observation task to team leads with clear criteria instead of trying to do it yourself. If you're working with limited resources, start with the observation notes and the quarterly reflection form. Skip the personality assessments and the elaborate tracking systems. The simplest version of this process still catches most of the talent that would otherwise go unnoticed. You just need to pay attention consistently.