When a position becomes vacant, the organization usually sees a staffing problem. Work still needs to be done, capacity has disappeared, and a manager needs someone to replace the employee who left. The logic is understandable, particularly when the vacancy is disrupting operations. A requisition is opened, the existing job becomes the specification, and recruiting begins searching for someone capable of stepping into it. By the time candidates enter the process, however, the organization has already made several important decisions without necessarily recognizing them as decisions at all.
It has decided that the work should continue substantially as it exists. It has decided that those activities should remain bundled into the same role. It has decided that the capability represented by the position should continue to sit in the same part of the organization. And, perhaps most importantly, it has decided that replacing the employee is the appropriate solution to the capacity that disappeared. None of those conclusions may be wrong. The problem is that the vacancy itself often makes them appear self-evident.
Jobs have a way of acquiring permanence that the work underneath them does not. Titles, reporting relationships, job descriptions, compensation levels, and organizational charts give roles structural legitimacy. Once established, a position begins to feel like something the organization has rather than something the organization designed. Yet the role is ultimately a collection of choices about how work is divided, where decisions are made, which capabilities belong together, and how one part of the organization connects with another. Those choices may have been sensible when the job was created, but the conditions surrounding them can change substantially while the role itself remains recognizable.
Technology may remove routine elements of the work while increasing the importance of judgment, interpretation, or exception handling. Growth can transform an informal coordination responsibility into an enterprise dependency. A new strategy may require a function that historically optimized its own outcomes to work much more closely across organizational boundaries. Responsibilities can also accumulate for far less strategic reasons: a capable employee absorbs something because no one else owns it, a temporary workaround becomes permanent, or work remains in a position simply because it has always been there. Over time, a role can become an archive of organizational history rather than a deliberate statement about how the organization wants work performed today.
A vacancy temporarily disrupts that permanence. For a brief period, the work exists without being attached to an incumbent employee. That creates a rare opportunity to see the position differently. Leaders can ask whether all of the work still needs to exist, whether it still belongs together, whether the same part of the organization should own it, and whether the capability the business now requires is actually the capability represented by the departing employee's job. Once another person is hired, those questions become harder. Salary, career expectations, reporting relationships, and legitimate commitments to the employee become attached to the role again.
This is why organizations can make an excellent hiring decision and still make a poor organizational decision. The candidate may be highly qualified. The selection process may be rigorous. The employee may perform exactly as expected. Yet the organization may have invested successfully in a position that should have been redesigned, capability that should have been located somewhere else, or work that no longer deserves to be preserved in its current form. Traditional measures of hiring quality would show success because the wrong decision occurred before recruiting ever began.
The deeper risk is therefore not simply that organizations hire people for skills that may eventually become obsolete. It is that hiring can become a mechanism through which organizations continuously reproduce their existing design. Every replacement carries forward assumptions about work, structure, capability, authority, and investment. When those assumptions are rarely reopened, an organization can be trying to transform itself strategically while rebuilding yesterday's operating model one vacancy at a time.
The first question in a strategic hiring decision should therefore not always be “Who should replace this person?” In some cases, the more consequential question is “What should this vacancy become?”
The Role Is a Bundle of Organizational Choices
Once leaders stop treating the vacancy as the problem itself, the role underneath it becomes easier to examine. A job may appear to be a single unit because one person performs it, but most roles are actually bundles of work assembled through a series of organizational choices. Tasks are grouped together, responsibilities are assigned, decision authority is located, interfaces with other functions are established, and particular capabilities are concentrated in the position. Work-design research has long reinforced that jobs are designed configurations rather than naturally occurring units of work (Campion et al., 2005; Morgeson et al., 2010; Oldham & Fried, 2016), which is important because the configuration that made sense at one point in the organization's development may not remain the best configuration indefinitely.
The distinction becomes particularly important when a strong incumbent has shaped the position over time. Effective employees rarely perform only what appears in their original job descriptions. They develop relationships, accumulate institutional knowledge, solve problems others bring to them, take ownership of gaps, and become trusted for responsibilities that may have little connection to the original design of the role. Their success can actually make the underlying design harder to see because the individual integrates the work so effectively that the organization begins to associate everything the person does with what the position inherently requires.
When that employee leaves, leaders can unintentionally convert the person's accumulated contribution into the specification for the next hire. The organization may ask candidates to reproduce a combination of responsibilities that emerged through years of experience, circumstance, and individual strengths rather than through deliberate design. Requirements are added to capture everything the departing employee handled, and the search becomes increasingly focused on finding someone capable of replacing the person rather than examining whether the organization should reproduce the same concentration of work.
This can create a particularly misleading form of talent scarcity. A role may become extraordinarily difficult to fill, and the organization may conclude that the external market lacks people with the required combination of capabilities. Sometimes that is true. But an unusually difficult search can also be evidence that the organization has constructed an unusually difficult job. When a position requires deep functional expertise, enterprise influence, analytical capability, operational execution, cross-functional coordination, people leadership, and knowledge of highly specific internal processes, the problem may not be a shortage of exceptional candidates. The organization may be asking one person to hold together work that should no longer be concentrated in one place.
That possibility changes how leaders should interpret hiring difficulty. Instead of immediately lowering requirements, increasing compensation, broadening the search, or waiting for a rare candidate who matches the entire specification, leaders can ask what the specification itself reveals about the organization. Which capabilities genuinely need to coexist in the role? Which responsibilities could be located closer to where the relevant decisions are made? Which activities exist because the organization has not clarified ownership elsewhere? Which requirements reflect the future direction of the work, and which merely describe the person who previously succeeded in it?
The same analysis applies even when a role is relatively easy to fill. A position does not have to be dysfunctional to deserve reconsideration. If technology has changed the economics of part of the work, the organization may need less execution capacity and more judgment. If strategy requires greater integration across functions, a role designed primarily around functional expertise may need a different balance of capabilities and authority. If growth has increased complexity, informal coordination that once worked through personal relationships may need to become an explicit organizational responsibility. The question is not simply whether the existing job still works. It is whether its design continues to support where the organization is going.
This is where hiring becomes inseparable from organizational design. A decision to refill a role preserves more than headcount. It preserves a particular answer to questions about how work should be divided, where capability should reside, and how responsibilities should connect across the organization. A decision to redesign the role changes those answers. A decision to distribute the work across several positions changes them again. Even choosing not to replace the position is a design decision because the work must either disappear, move, or be performed differently.
Executives do not need to redesign every vacancy to recognize this reality. They do need to understand that the existing job description is evidence about how the organization has operated, not proof of how it should continue to operate. The distinction is small in language but significant in practice. Once the inherited role stops being treated as the unquestioned starting point, the vacancy can reveal choices that were previously hidden inside the position.
When Good Hiring Decisions Reproduce the Wrong Organization
The most difficult hiring risks are not always visible at the level of an individual requisition. A single replacement decision may be entirely rational. A team has lost capacity, the work still needs to be done, the role is familiar, and a qualified candidate is available. The manager is rewarded for restoring performance quickly, recruiting is measured on its ability to fill the position, and the organization experiences immediate relief when the vacancy closes. Nothing about that sequence necessarily feels strategically problematic.
The problem emerges when the same logic is repeated across the organization. One manager replaces a role because the work cannot wait. Another does the same thing in a different function. A third updates a job description slightly but preserves the essential structure of the position. Over time, hundreds of decisions are made by leaders who are each responding appropriately to local operating needs. Yet because those decisions are usually made within the boundaries of the existing organization, they tend to reproduce those boundaries as well. Functions retain the capabilities they already own, responsibilities remain attached to familiar roles, layers are rebuilt as positions reopen, and coordination mechanisms that may no longer serve the strategy are quietly restored.
The result can become a self-reinforcing organizational pattern. Previous design choices influence the decisions that follow because the existing structure becomes the default reference point for what the organization believes it needs. A role exists because the work was once organized that way, and because the role exists, future staffing decisions continue to validate that arrangement. The organization does not necessarily decide that the existing design is optimal. It simply keeps making decisions from within it.
This matters because many organizational transformations depend on changing precisely those patterns. A company may want decisions made closer to customers while continuing to refill managerial roles built around escalation and approval. It may want stronger enterprise collaboration while replacing positions whose goals and accountabilities remain overwhelmingly functional. It may invest heavily in automation while restoring jobs that were designed around manual coordination or transaction processing. It may say that a particular capability needs to become more distributed while hiring continues to concentrate that expertise in the same specialist group.
In each case, the strategy and the hiring pattern are moving in different directions. The contradiction can persist for a long time because individual hiring outcomes still look successful. The new employees are capable. Managers are satisfied. Time-to-fill may improve. New-hire performance may be strong. Retention may even be healthy. Traditional recruiting measures can therefore indicate that talent acquisition is working while the cumulative pattern of hiring is making a broader organizational shift more difficult.
This exposes an important distinction between selection quality and investment quality. Selection quality asks whether the organization chose the right person for the defined role. Investment quality asks whether the role and capability being funded are the right things for the organization to strengthen in the first place. The first question belongs primarily to talent selection. The second reaches into strategy, organizational design, workforce planning, and capital allocation.
This distinction also clarifies where recruiting effectiveness ends and organizational judgment begins. Talent acquisition can improve the quality of sourcing, assessment, and selection against an approved requirement. It cannot determine by itself whether the requirement represents the right work, capability, level, or organizational investment. Those choices belong upstream, where leaders decide what the organization should strengthen before the search begins.
Both matter because every hire creates more than labor capacity. It creates a continuing financial commitment and reinforces expectations about how work will be organized. Once someone is hired, the role acquires additional legitimacy. Managers build around it, workflows adapt to it, career paths may incorporate it, and future vacancies can inherit it as precedent. The cost of reconsidering the design therefore rises after the position is filled, even when the original decision was made for perfectly understandable reasons.
That is why workforce transformation can stall even when leaders are genuinely committed to change. The organization may redesign structures at the top, launch new technology, introduce new strategic priorities, and communicate a different operating philosophy, while everyday staffing decisions continue to replenish the system that existed before those changes. The resistance does not necessarily come from people opposing transformation. It can come from ordinary operating decisions that were never connected strongly enough to the transformation in the first place.
The executive implication is not that every hiring decision requires enterprise-level approval. That would create a different problem by adding delay and bureaucracy. The implication is that organizations need some way to distinguish between vacancies that simply restore necessary capacity and vacancies that represent a meaningful opportunity to reconsider work, capability, or structure. Without that distinction, the default process will usually favor reproduction because reproduction is faster, easier to explain, and less disruptive in the moment.
The strategic risk, then, is cumulative rather than transactional. An organization can make hundreds of good hiring decisions and still build the wrong workforce if each decision is optimized against assumptions the strategy is trying to change.
Not Every Vacancy Deserves the Same Decision
Treating a vacancy as a design opportunity does not mean every open position should trigger a formal review of structure, technology, capability, and workflow. That would make hiring slower without necessarily making it better. The more useful discipline is to recognize that vacancies differ in strategic significance. Some simply represent lost capacity in work that remains stable and well understood. Others occur in areas where the surrounding conditions have changed enough that automatic replacement would be a poor assumption.
The first signal is change in the work itself. If technology, regulation, customer expectations, growth, or strategy has materially altered what the role needs to accomplish, then the previous position may no longer be the right reference point. A job built around producing information, coordinating manual handoffs, or managing routine exceptions may require a very different configuration once automation or new systems change how that work is performed. The question is not whether technology can remove the job. It is whether the value of the role has shifted enough that the organization should reconsider where human judgment, expertise, and accountability now matter most.
A second signal is persistent difficulty around the role. Repeated hiring challenges, chronic overload, unclear ownership, excessive handoffs, or dependence on one highly experienced employee can indicate more than a talent problem. They can reveal that the work has been designed in a way that is difficult to sustain. When a role repeatedly requires an unusual combination of capabilities, relies heavily on informal influence, or absorbs responsibilities that belong nowhere else, the vacancy may be exposing a structural weakness that was easier to tolerate while a strong incumbent was compensating for it.
A third signal is misalignment with the direction of the organization. Leaders should pay particular attention to positions located in parts of the business that are being transformed. If the organization is changing its operating model, redistributing decision authority, consolidating capabilities, increasing cross-functional integration, or shifting how value is created, then refilling roles against the old design can undermine those changes. A vacancy in a stable environment may warrant straightforward replacement. A vacancy inside a changing system deserves a different level of scrutiny because the organization has an opportunity to align staffing with the future state before another long-term commitment is made.
The significance of the role also matters. Some positions carry disproportionate influence over decisions, coordination, customer outcomes, institutional knowledge, or the development of others. Replacing those roles should involve more than confirming that the previous responsibilities still exist. Leaders need to consider whether the position still represents the right concentration of authority and capability for the organization they are trying to build. The higher the role's leverage over how work moves through the system, the more consequential the design decision embedded in the vacancy becomes.
This does not require a complicated new process. It requires a better threshold for when leaders should stop and look more closely. The organization should be able to distinguish between a vacancy that needs to be filled and a vacancy that needs to be understood before it is filled. That distinction creates room for judgment without turning every staffing decision into bureaucracy.
The practical value is that it changes the sequence. Instead of beginning with the assumption that the old job should be reproduced and then asking who can perform it, leaders first test whether the work, role, and capability still make sense together. Only then does recruiting begin against a requirement the organization has deliberately chosen to preserve or redesign.
What Great Organizations Do Differently
Great organizations do not treat every vacancy as an automatic signal to replace what was lost. They recognize that some openings simply require capacity to be restored, while others create a temporary opportunity to reconsider the work, capability, and organizational assumptions embedded in the role. The difference is not that great organizations redesign every position. It is that they are more deliberate about deciding when replacement is appropriate and when the vacancy deserves a closer look.
That discipline starts before recruiting begins. Instead of opening a requisition and using the existing job description as the unquestioned specification, leaders first consider whether the role still reflects what the organization needs. They examine whether the work has changed, whether technology has altered how that work should be performed, whether responsibilities still belong together, and whether the capability represented by the role matches the direction of the business. In many cases, the answer will still be to refill the position. The distinction is that the organization reaches that conclusion deliberately rather than inheriting it from the previous design.
Great organizations also separate replacement need from capability need. A vacancy identifies the capacity and experience that disappeared, but it does not automatically define what the organization should invest in next. Leaders consider whether the next hire should restore the same capability or strengthen something the organization will need more of in the future. That may lead to a similar role with different expectations, a redistribution of responsibilities, a stronger emphasis on a future capability, or a decision to build the capability elsewhere. The vacancy becomes an investment decision rather than simply a recovery decision.
They are also more willing to question difficult-to-fill roles rather than assuming the labor market is always the problem. When a position repeatedly requires an unusual combination of capabilities, depends heavily on informal influence, or accumulates responsibilities that do not naturally belong together, great organizations examine whether the design itself is creating scarcity. Instead of continuously increasing compensation, broadening the search, or waiting for an increasingly rare candidate, they ask whether the work has been bundled in a way that makes the role unnecessarily difficult to sustain.
Great organizations pay particular attention to vacancies inside areas undergoing change. When a function is being transformed, technology is altering the work, decision authority is shifting, or the operating model is evolving, the old position carries greater risk as the default template for the next hire. Leaders recognize that refilling these roles without reconsideration can quietly rebuild the structure the broader transformation is trying to change. Hiring decisions therefore become one of the mechanisms through which future-state design is either reinforced or undermined.
They also look beyond the individual requisition. A single replacement may have little strategic consequence, but repeated decisions create patterns. Great organizations consider what happens when the same staffing logic is applied across dozens or hundreds of vacancies. They ask whether those decisions are gradually increasing the capabilities the strategy requires or simply restoring the organizational configuration that already exists. This is especially important because each local decision can appear entirely reasonable while the cumulative effect moves the organization in the wrong direction. The article already establishes this distinction between strong individual hiring outcomes and weaker broader investment choices.
Perhaps most importantly, great organizations preserve judgment. They do not solve the problem by adding a cumbersome approval process that forces every vacancy through an enterprise redesign exercise. That would replace automatic hiring with automatic bureaucracy. Instead, they create enough discipline to recognize when the significance of the vacancy warrants a different conversation. Stable work with clear requirements can move quickly. Roles affected by strategic change, persistent design problems, changing capability requirements, or disproportionate organizational influence receive greater scrutiny.
The result is not slower hiring. It is more deliberate investment.
Great organizations still move quickly when the decision is straightforward. But when the vacancy contains a meaningful choice about work, capability, structure, or future direction, they make that choice before recruiting converts yesterday's role into tomorrow's commitment.
1. If this role did not already exist, would we create it in the same form today?
This question forces leaders to separate current need from historical precedent. A position can feel indispensable simply because the organization has learned to operate around it. Reframing the role as if it were being designed for the first time makes it easier to see whether its responsibilities, level, reporting relationship, and scope still reflect what the business requires. If the answer is no, the vacancy should not automatically become a search for the closest possible replacement.
2. Which parts of the work reflect future business requirements, and which are being preserved mainly because they have always been there?
Most roles contain a mixture of essential work, legacy activity, informal responsibilities, and tasks that accumulated over time. Leaders should distinguish between work that will matter more in the future and work that persists mainly through habit. This is especially important when technology, strategy, growth, or operating-model changes have altered where value is created. The objective is not to strip the role down mechanically, but to understand which parts deserve continued investment.
3. What capability should this vacancy add to the organization, not simply restore?
Replacement thinking focuses on recovering what was lost. Strategic hiring asks whether the vacancy creates an opportunity to strengthen something the organization will need more of. That may mean greater analytical judgment, stronger enterprise coordination, deeper technical expertise, broader commercial understanding, or a different form of leadership capability. The point is not to chase whatever skill is fashionable. It is to ensure that the next investment increases the organization's ability to execute the strategy it is moving toward.
4. Does all of this work still belong together, in this role, in this part of the organization?
A vacancy can expose work that has been bundled together for reasons that are no longer visible. Some responsibilities may belong closer to the customer, some nearer to a decision authority, and others within a shared capability or specialist team. If leaders never reopen that question, the organization can continue to reinforce inefficient handoffs, excessive concentration of expertise, or unclear ownership simply because one person previously carried the entire bundle successfully.
5. If we repeated this decision across every similar vacancy, what organization would we be building?
This is the question that moves the discussion beyond a single requisition. A replacement decision that seems reasonable in isolation can become strategically consequential when multiplied across a function, geography, or enterprise. If every similar opening were filled in essentially the same way, would the organization become more aligned to its future strategy, or would it become a more efficient version of its current design? Executives should be especially cautious when the cumulative pattern of hiring is reinforcing assumptions that the broader transformation agenda is trying to change.
Taken together, these questions are not meant to make hiring slower. They are intended to make the decision that precedes hiring more deliberate. The goal is to distinguish between roles that genuinely need to be restored and vacancies that create an opportunity to reshape work, capability, or organizational design before another long-term investment is made.
Hiring is usually treated as the point where talent strategy becomes operational. A role is approved, a requisition is opened, candidates are evaluated, and the organization selects the person believed most capable of performing the work. But by the time that process begins, one of the most important strategic choices may already have been made: the organization has decided what work it intends to preserve.
That decision deserves greater attention because a vacancy sits at the intersection of talent, organizational design, and investment. Replacing a role means more than restoring capacity. It means recommitting to a particular configuration of responsibilities, a particular location for capability, and a particular way of organizing work. In stable conditions, that may be exactly the right decision. In changing conditions, however, automatic replacement can make the organization more efficient at reinforcing assumptions it should be reconsidering.
The strategic value of a vacancy therefore comes from the temporary freedom it creates. For a brief period, the work is no longer attached to an incumbent, and leaders have an opportunity to examine the role before rebuilding it. That does not mean every vacancy should produce a redesign. It means every meaningful vacancy should be understood as a choice rather than a foregone conclusion. The discipline is simple: do not allow yesterday’s job to decide tomorrow’s organization by default. A vacancy tells you what the organization has lost. A strategic hiring decision determines what the organization chooses to rebuild.
Supporting Research
- Campion, M. A., Mumford, T. V., Morgeson, F. P., & Nahrgang, J. D. (2005). Work redesign: Eight obstacles and opportunities. Human Resource Management, 44(4), 367–390.
- Morgeson, F. P., Dierdorff, E. C., & Hmurovic, J. L. (2010). Work design in situ: Understanding the role of occupational and organizational context. Journal of Organizational Behavior, 31(2–3), 351–360.
- Oldham, G. R., & Fried, Y. (2016). Job design research and theory: Past, present and future. Organizational Behavior and Human Decision Processes, 136, 20–35.
