A growing organization reaches a point where the work outruns the people. The response is nearly automatic. Open a role, write the description, find the person. It feels like the responsible move. Often it repeats the original problem at a higher salary.
Most hiring decisions in growing organizations are structural decisions in disguise. The role gets written to describe a pile of work. The function underneath the pile never gets defined. The new person arrives into the same confusion that produced the pile. The piece on operational architecture names the broader pattern of structure lagging scale. This piece looks at one place it surfaces, which is the moment a leader decides to hire.
What a Job Description Reveals
A job description is a record of what the organization has decided. Read one closely and it shows how far the decision went.
A role written as a list of tasks signals that nobody has decided what the function owns. The description reads like an inventory. Manage the calendar. Coordinate vendors. Draft the monthly update. Follow up on invoices. Support the team as needed. Each line is a task someone is doing now and wants to stop doing. The description gathers those tasks under one title and calls the result a job.
The description also shows who wrote it. A list assembled by the person leaving the work behind carries that person's view of the work, in the order they experienced it. It captures the sequence of their days and omits the logic underneath. The new hire receives a record of activity with no statement of purpose.
A defined function reads differently. It names an outcome the role is accountable for. It names the decisions the role makes without asking. It says what a good quarter looks like. Tasks appear underneath, as the means.
The phrase "and other duties as needed" carries the tell. When that phrase carries real weight, the function has no edges. Anything that falls between existing roles drifts into the new one, because nobody else owns it.
The Hire That Does Not Help
A capable person dropped into an undefined seat spends the first six months doing what the leader was doing, the way the leader was doing it. They inherit the same pile. They inherit the same missing decisions. Nobody told them what they own, so they ask. The questions route to the person who was supposed to be relieved.
The new hire often performs well on every visible measure. Tasks get done. Messages get answered. The leader still feels the weight, because the decisions did not move. The new person completes work and waits for direction on anything that requires judgment. The leader's calendar fills with the same questions in a new voice, and the recurring meetings added to manage them become a cost of their own. Meanwhile the leader pays twice. Salary goes to the new hire, and the leader's own hours go to supervising work they hoped to hand off.
Over time one of two things happens. The hire absorbs the confusion and begins to resent it. Or the hire leaves, and the organization concludes the person was the wrong fit. The seat gets reposted with the same description. The structure that produced the vacancy stays untouched.
You cannot hire your way out of a structure nobody has defined.
The Question That Comes First
One question comes before any posting. Can you describe what this person owns, what they decide, and what finished looks like?
Owning means being the single point of accountability for an outcome. Deciding means a defined range of calls the person makes without checking. Finished means a condition anyone could verify. If all three answers arrive as a sentence each, the function exists and a hire can fill it. If the answers arrive as a list of tasks, or as "it depends," or as a description of what the leader currently does, the gap is structural.
A structural gap has a recognizable signature. The leader can describe every task in detail. The boundary of the role stays vague. Ask where the role ends and the answer wanders.
The test costs nothing and runs in a single sitting. Sentences that form easily mean the function exists. Sentences that refuse to form mean it does not.
What Changes When the Function Exists First
When the function exists first, the hire changes character. A search for fit replaces the search for relief. The leader knows what the seat owns, so the interview can test whether a candidate can own it. Candidates can see the edges of the role, which means they can judge whether they want it.
The first six months change as well. The new person starts with a defined outcome and a defined range of decisions. Questions still arrive, and they concern the work itself. Relief reaches the leader because the decisions have a home.
The test is simple. Describe what the person owns, what they decide, and what finished looks like. Where the description holds, hire. Where it fails, the next move belongs to the structure.
How the seat connects to the roles around it, and where this hire falls against everything else the organization needs, is its own discipline. The three sentences come before any of it, and anyone can write them this week. A leader who reads a hiring need as a structural question begins with what the seat is, and the right person becomes easier to recognize.