هر جای خالی، مجوز استخدام نیست؛ اول مسئله کار را پیدا کنید

An empty seat becomes visible, pressure rises, a hiring request is filed, and everyone behaves as if the cause has been identified. But a vacancy is only a signal, not a diagnosis. Organizations are usually quicker to notice an empty chair than to notice ambiguous work, a disorderly role, or excess priorities.

When a manager says, “We are short one person,” the right question is not, “When should we post the opening?” The right question is, “Which specific output is not being produced because what capacity or capability is missing?” If the answer is unclear, hiring is not a solution; it merely brings another person into existing ambiguity.

Saying no to an immediate hire is not opposition to growth. It is opposition to the lazy assumption that every operating pressure should be treated by adding headcount. A new employee requires recruiting, onboarding, coordination, and management, and if the core issue remains unresolved, the organization simply replicates the same disorder with more capacity.

A hiring request often appears when a team is under pressure. That pressure is real, but pressure does not automatically prove a shortage of people. Low-value work may not have been removed, decisions may be delayed without reason, inputs may be incomplete, or accountability may be dispersed across several roles.

Hiring in this situation can become an expensive painkiller. It may distribute the pressure for a while, but it leaves the cause untouched. The organization then faces the same bottleneck, a new role, higher fixed costs, and a person who must find a way through existing disorder from day one.

The starting point is to define the output. Not a list of activities, not a job description full of vague verbs, and not a phrase such as “support the team.” The manager must be able to state what observable result the role will deliver, at what quality level, in what cycle, and for which stakeholder.

If the output is unclear, the required capacity is unclear too. You cannot claim that “we need an analyst” when it is not clear which decision the analysis is meant to make better, faster, or more reliable. A job title is not a problem diagnosis; sometimes it is merely a neat label on a messy need.

Consider a hypothetical team that files a hiring request to respond to customer inquiries. Before approval, it must be clear where the problem sits: Are requests arriving incomplete? Are approvals circulating across departments? Are repeated responses being produced manually? Or does essential work genuinely exceed the team’s capacity?

These are four different problems, not one generic vacancy. Incomplete inputs are a process-design problem. Circulating approvals are a decision-rights problem. Repeated responses are a work-standardization problem. Only in the fourth case, and only after review, might additional capacity be an appropriate response.

After defining the output, dissect the work itself. Which activities directly contribute to the output? Which tasks are merely organizational habits? What is repeated because of missing decisions, rework, or useless reporting? Until these questions are answered, a hiring request resembles ordering a tool before understanding the problem.

A simple and demanding test is needed: If the new person starts tomorrow, exactly what work will they take from whom? If the answer is, “They will help wherever needed,” the role has not been designed yet. An organization that cannot identify transferable work probably does not know what it is paying for.

The next step is removal and simplification. Before adding capacity, the manager should specify which work will stop, which steps will be shortened, and which demands will no longer be accepted. This part is unpopular because it forces the manager to confront accumulated priorities.

Hiring in order to preserve everything is often a more respectable-looking form of failure to prioritize. If every request, report, meeting, and approval path remains sacred, no number of new employees will be enough. Capacity is not infinite; the cost of ignoring that fact simply tends to appear later.

The organization must then distinguish a capacity gap from a skill gap. If the work is clear, necessary, and properly designed but exceeds the team’s available time, the problem is probably capacity. If time exists but the team lacks the ability to exercise judgment, analyze, negotiate, lead people, or use a critical tool, the problem is capability.

These do not require identical remedies. A capacity gap may call for hiring, redistributing work, or reducing demand. A skill gap may be addressed through targeted development, temporary support from a specialist, redesigned responsibilities, or a change in the role’s level. Hiring a new person for both problems is not precise; it is simply familiar.

Do not romanticize internal options. Internal promotion without assessing capability merely moves a person to a point where failure is more likely. But ignoring internal options is not a sign of maturity either; it often shows that the organization lacks a clear view of its skills, growth capacity, and succession possibilities.

Role redesign also deserves serious attention. Many roles are built through an accumulation of historical tasks: some execution, some coordination, some reporting, and several vague responsibilities that no one else owns. Such a role is unsuitable for hiring because it lacks success criteria and turns the new employee into a dumping ground for disorder.

A hireable role needs boundaries. It must be clear which decisions it owns, which inputs it receives, which roles it depends on, what lies outside its responsibility, and how success will be observed. A long job description does not necessarily create a clear role; sometimes it merely decorates ambiguity with more words.

For a traceable decision, turn the hiring request into a decision memo. Record the expected output, the work removed or simplified, the verified bottleneck, the type of gap, the internal options considered, the proposed role design, and the consequence of not deciding. This document is not meant to create another bureaucratic layer; it is meant to prevent everyone from telling a different story about the problem.

The option of “do not hire yet” must also be real in that memo, not a theatrical threat. Sometimes the right choice is to fix the process first, reduce priorities, or build a capability within the team and then reassess capacity. But if essential work is clear, waste has been removed, and a capacity or skill shortage is observable, extending the review merely transfers pressure to the team. Before approving a hire, separate the vacancy from the actual problem; you may still decide to hire, but at least you will know what you are hiring to solve.