A Vacancy Is Not a Job Description

An employee leaves, and the apparent management task is to find a replacement. The budget exists, the title is familiar, and unfinished work creates pressure to act. Yet a vacancy establishes only that someone is gone. It does not establish that the same job should exist in the same form. For CEOs and hiring managers, that distinction separates filling a seat from deciding how the business should operate.

A job can accumulate responsibilities for reasons unrelated to its original purpose. An employee may absorb a neglected process, become the default contact for a difficult customer, or keep a reporting routine alive because nobody has decided to end it. These are plausible ways work attaches to a person rather than a role. Replacing that person without examining the bundle turns accumulated obligations into a permanent staffing requirement.

The first question is therefore not what kind of candidate could do everything the departing employee did. It is which outcomes still need an owner. That requires separating essential work from inherited activity, and formal accountability from informal assistance. A report that informs no decision should not automatically survive inside a new job description. Nor should a recurring workaround become a required competency merely because its previous owner handled it.

This review can expose a choice leadership would otherwise leave to recruiters. A position that combines conflicting demands may need a narrower mandate, a different reporting line, or support from another function. Work might also belong with an existing team, provided capacity and accountability move with it. None of those choices is automatically better than replacement. The point is to make them explicitly, rather than preserve an arrangement by default.

There is a danger in using role redesign as a polite name for adding work to everyone else. Eliminating a vacancy does not eliminate the obligations attached to it. If leaders redistribute those obligations, they must identify what recipients can stop doing or what additional capacity they will receive. Otherwise, an apparent efficiency is simply an unacknowledged claim on employees’ time, with priorities left unresolved.

For a role that remains necessary, the next task is to distinguish entry requirements from knowledge that can be learned. Familiarity with internal terminology, personal relationships, and unwritten procedures can make an incumbent appear uniquely qualified. But those advantages do not necessarily define the underlying job. Requiring a new hire to arrive with their equivalent can narrow the search around yesterday’s arrangement instead of tomorrow’s needs.

That distinction also improves the logic of assessment. Candidates should be evaluated against the decisions and responsibilities the role will actually carry. If success requires resolving competing priorities, an interview focused only on technical fluency leaves an important question unanswered. If the role has no authority to settle those conflicts, selecting a persuasive candidate does not repair the design. Hiring cannot substitute for granting the authority needed to deliver the promised result.

Managers also need to explain the revised role to the people around it. A clear job description offers little protection if colleagues continue directing every old request to the new employee. Boundaries become credible when leaders specify where excluded work now belongs and support those boundaries when challenged. Without that follow-through, the organization can reconstruct the previous job through everyday requests, regardless of what the hiring process established.

For CEOs, the useful oversight is not approval of every replacement. It is a requirement that managers distinguish continuity from necessity. Time-sensitive coverage can proceed while the permanent role is examined; an urgent customer obligation need not become an argument for preserving every historical task. The decision should make visible what must continue immediately, what deserves redesign, and who is accountable during the transition.

A successful replacement is not necessarily someone who recreates the predecessor’s methods or absorbs the same loose ends. It is someone whose responsibilities make sense, whose authority matches those responsibilities, and whose surrounding team understands the division of work. A vacancy creates disruption, but it also creates a decision point. Leadership adds value by deciding what the job should become before asking someone new to succeed in it.