Sergio Castagna
Scarcity is not only a market signal
The language of talent shortage has become one of the defining explanations of corporate frustration. Companies struggle to find enough engineers, salespeople, data specialists, technicians, managers or operators with the right combination of skills, judgement and adaptability, and the conclusion is often that the market has failed to provide what organisations need.
This conclusion is sometimes correct. Certain skills are genuinely scarce, some technologies evolve faster than formal education systems can adapt, and some sectors require levels of expertise that cannot be produced quickly, however attractive the salary or compelling the mission. To dismiss the shortage of talent as a managerial fiction would be as simplistic as accepting it as a complete explanation.
But the more interesting question is not whether talent is scarce. It is what organisations do when it is.
A shortage of talent is usually interpreted as a failure of supply: not enough people, not enough skills, not enough experience, not enough readiness. Yet it can also be read as an organisational signal, a sign that the current system of work is no longer capable of converting available skills into the level of performance the organisation now requires.
History suggests that moments of talent scarcity rarely reward those who merely search longer, pay more or compete harder for the same limited pool of individuals. They reward organisations able to reconsider the system in which talent is expected to create value. When the available skills no longer seem sufficient for the ambition, the best organisations do not simply intensify the search. They redesign the work.
Three historical answers to the same constraint
Ford, Toyota and Apollo offer three distinct answers to this problem. Ford standardised. Toyota learned. Apollo integrated. Each, in its own context, transformed a constraint of human capability into an innovation in the organisation of work.
Ford's achievement was not simply to employ more workers. It was to reduce the dependence of automobile production on scarce, all-round craftsmanship by embedding part of the intelligence of the work into the system itself. The moving assembly line did not eliminate skill; it redistributed it. What had previously resided largely in the hands of highly capable individuals was partly transferred into sequence, tooling, process and repetition.
This was not merely an industrial technique. It was a new relationship between labour, complexity and output. The car could become a mass product because the work required to produce it had been decomposed, ordered and made reproducible. A system was designed so that performance no longer depended on every worker being able to understand or execute the whole.
The contemporary equivalent is not necessarily a factory line. It may be a clearer operating model, better tooling, stronger process architecture, or a more deliberate decomposition of complex work into components that can be taught, measured and improved. When an organisation cannot find enough people capable of carrying an entire burden, one response is to ask whether the burden itself has been badly distributed.
Yet Ford also reveals the limits of standardisation when it is treated as the whole answer. A system can become efficient and still be brittle. It can reduce dependence on rare skills while creating work that is narrow, repetitive and ultimately unattractive. Standardisation solves one problem, but if it is not accompanied by learning, it risks becoming a form of rigidity.
That is where Toyota adds a second and more modern lesson. If Ford showed the power of standardisation, Toyota showed that standardisation without learning is incomplete. The Toyota Production System did not treat the organisation as a machine to be optimised once, but as a system capable of continuous improvement. Its strength lay not only in process discipline, but in the routines through which problems were surfaced, knowledge was shared, and small improvements accumulated into structural advantage.
Toyota's lesson is particularly relevant in an economy where the half-life of skills is shortening. In many fields, the idea of hiring someone whose knowledge will remain sufficient for years has become increasingly unrealistic. Technologies change, markets shift, tools evolve and customers raise their expectations. In such an environment, the decisive capability is not only the capacity to recruit talent, but the capacity to make the organisation learn faster than the problem changes.
This is a more demanding ambition than hiring well. It requires standards that can evolve, managers who can teach, teams that can expose problems without fear, and processes that convert experience into institutional knowledge. The value is not only in the people the organisation employs, but in the quality of the system through which their intelligence is developed and compounded.
Apollo offers a third lesson, suited to a different form of scarcity: the scarcity created by complexity itself. The moon landing is often remembered as a triumph of exceptional individuals, and it certainly required them. But genius alone did not put a man on the Moon. The programme depended on the ability to coordinate thousands of specialised contributors, align contractors and agencies, manage interfaces, test assumptions, and turn dispersed expertise into a coherent system.
Apollo's challenge was not only to possess talent, but to integrate it. Engineers, mathematicians, pilots, manufacturers, suppliers and public institutions had to operate inside a structure where no single person could understand, let alone control, the whole. The scarce resource was not merely expertise; it was the organisational capacity to make expertise work together.
This may be the most relevant lesson for today's companies. Artificial intelligence, digital transformation, international expansion and new business models rarely fail because no capable individuals exist anywhere in the system. They often fail because those capabilities remain fragmented. The data expert is disconnected from the commercial reality. The product team moves faster than the operating model. The finance function measures what the business can no longer afford to optimise. The organisation has talent, but not integration.
Ford shows standardisation. Toyota shows organisational learning. Apollo shows the integration of complex expertise.
Together, they suggest that talent shortages should not only be interpreted as failures of supply. They can also be read as signals that the current design of work has reached its limits.
The organisation as a talent multiplier
The question, therefore, is not only where to find more talent. It is what kind of system would allow the talent already available, inside and outside the organisation, to create more value.
This distinction matters because talent is not self-executing. It does not become useful simply by being hired. It must be recognised, organised, developed and connected to work that has been designed intelligently enough for its value to appear. A brilliant individual in a confused system will often produce less than an average individual in a well-designed one. Conversely, a strong organisation can amplify capabilities that the market, or even the individuals themselves, may have underestimated.
This is not an argument against talent. It is an argument against treating talent as if it operated independently from the systems around it. The most capable people still need context, clarity, tools, interfaces, standards, feedback loops and institutions that allow their judgement to travel beyond their own effort. Without such systems, talent remains local. With them, it becomes organisational capacity.
That is why the most durable answer to talent scarcity may be less dramatic than the language of crisis suggests. It is not simply to compete harder for the same limited pool of people. It is to build organisations in which scarce talent is amplified by design.
The lesson of history is not that talent does not matter. It is that, when talent becomes scarce, organisation matters more.