Talent Strategy, Organisational Capability, Hiring vs Development, Build vs Buy, Leadership Development

There is a particular kind of hiring cycle that repeats itself in mid-sized businesses without anyone quite noticing the repetition. A gap opens up, sales isn't converting the way it should, a new market needs someone who understands it, a process keeps breaking. A job description gets written. Someone competent gets hired. For a while, the gap closes. Then, eighteen months or two years later, a version of the same gap reopens. Not identical, but recognisably the same shape. Sales conversion softens again. The next market expansion needs someone who understands it, again. The business hires again, for what looks like a new role but is, on closer inspection, the same capability it thought it had already built. This is not bad luck, and it is not a hiring failure in the usual sense. It is the result of a category error that most businesses make without realising it: treating a role as if it were a capability.
The organisational researchers Dave Ulrich and Dale Lake, in their 1990 study of what actually creates sustained competitive advantage inside firms, drew a distinction that is easy to state and hard to act on. A capability, in their framing, is not the same as individual competence.1 Competence lives in a person, their skills, their experience, their judgment. Capability lives in the organisation, in the systems, culture, and collective practice that allow that competence to be applied consistently, by more than one person, over time, regardless of who currently occupies the role. A brilliant salesperson is a competence. A sales organisation that can reliably develop brilliant salespeople, onboard them into a shared method, and maintain performance even as individuals rotate in and out, is a capability. Most businesses hire for the first and quietly assume, without ever deciding to, that the second will simply follow. It rarely does on its own. This is why the gap reopens. The business didn't build a capability the first time. It rented a competence, for as long as that person stayed, and when they left, were promoted, or simply plateaued, the underlying capability gap was still there, exactly where it had always been. It had just been temporarily obscured by one person's individual skill.
The talent researcher Claudio Fernández-Aráoz, whose work on executive search and hiring has been widely published in Harvard Business Review, has written extensively about why organisations gravitate toward hiring for immediate competence rather than for longer-term potential.2 Hiring for competence is faster to evaluate. A candidate's track record can be checked, their skills demonstrated, their fit against the role assessed with reasonable confidence in a matter of weeks. Hiring for potential, the raw capacity to grow into capability the business doesn't yet have, is slower to assess and carries more risk. It requires judgment about qualities that don't show up cleanly on a resume: curiosity, learning agility, the ability to adapt reasoning to unfamiliar situations. Under time pressure, and mid-sized businesses are almost always under some form of time pressure, the faster, lower-risk option wins by default. This is a locally reasonable decision made repeatedly across an organisation, and it is also precisely how capability gaps become permanent rather than temporary. Each individual hiring decision optimises for filling the role quickly. None of them, individually, is responsible for building the underlying capability. So nobody does.
Peter Cappelli, the Wharton management professor whose research on talent strategy has tracked how companies source capability, framed this as a build-versus-buy decision that most organisations never make consciously.3 Buying capability, hiring it in fully formed, is fast and visible. Building it internally, through structured development, stretch assignments, and deliberate succession planning, is slow and much harder to point to in a quarterly review. Cappelli's research found that businesses which lean heavily toward buying, hiring their way out of every capability gap, tend to become progressively worse at building, because the organisational muscle for development atrophies from disuse. The next gap gets filled the same way the last one was, not because it's the better answer, but because it is the only answer the business still knows how to execute. This creates a quiet, compounding cost. A business that has bought its way through every capability gap for a decade has a payroll full of competent individuals and very little organisational capability that would survive their departure. It looks fully staffed. It is not fully built.
Building rather than buying requires a different kind of patience than most hiring decisions get. It means hiring, in some cases, for potential rather than immediate fit, and accepting a longer runway before that person is fully productive. It means designing roles so that the knowledge and method involved can be taught and inherited, not just performed by whoever happens to be talented enough to figure it out on their own. It means treating the departure of a strong performer as a test of whether a capability was actually built, rather than as simply a vacancy to be refilled. None of this shows up as an immediate result. It shows up, if it works, as a business that stops needing to solve the same problem every eighteen months, because the problem was actually solved the first time, not just staffed.
The next time a critical role opens up, it's worth asking a question most job descriptions never address. Are we hiring to fill this role, or are we hiring to finally build the capability that keeps creating this exact vacancy. Most businesses have never had to answer that question honestly, because hiring for the role always feels like progress. It is. It's just not the same progress as building something that doesn't need to be rehired for, again, in two years.
Falgun has worked with founder-led businesses across telecom, hospitality, and premium consumer brands for 28 years. He writes from experience, not observation.
Falgun Mistry
Ideation People