The Job Description Problem — Why Organizations Don't Know What They're Hiring For
- Ebony Adomanis
- Apr 30
- 6 min read
Most organizations believe they understand the roles they are hiring for.
They write a job description. They post it. They interview candidates against it. They make a hire. They onboard. And then — gradually, quietly — the role becomes something the description never anticipated.
This pattern appears in all industries and organizational sizes, but is particularly noticeable in administrative and operational roles. The gap between what is expected in writing and what is actually delivered can be significant, creating opportunities to improve the entire function.
The job description says coordination.
The role requires systems management.
The job description says calendar support.
The role requires executive decision flow and stakeholder navigation.
The job description says "other duties as assigned."
The role absorbs everything the organization has not yet designed a structure for.
This is not a hiring problem. It is an infrastructure design problem. And it begins long before the candidate applies.
The data supports what many administrative professionals already know. According to the Global Skills Matrix 2026, released by the World Administrators Alliance, 43% of administrative professionals are working under job titles that do not reflect the reality of their role. Across the profession globally, there are more than 187 different job titles in use — and the problem is not just variety. The same title can represent completely different levels of responsibility and impact depending on the organization.
When the title does not match the work, everything downstream becomes misaligned: grading, compensation, development pathways, and performance evaluation. The gap is not anecdotal. It is measurable, and it is structural.
So the question becomes: how does this happen?
Who Writes the Description
In most organizations, administrative job descriptions are drafted by one of two people: an HR generalist working from a template, or a hiring manager who needs the position filled.
Neither is positioned to describe the operational function the role actually serves.
HR generalists write for compliance and comparability. They pull from classification databases, benchmark salary bands, and standardize language across the organization. The result is a description that is technically accurate and operationally incomplete.
Hiring managers write from urgency. They know what they need done tomorrow. They can list tasks. They can describe the immediate pain the hire will relieve. But they are rarely thinking about the operational system the role will inhabit — the dependencies, the cross-functional coordination, the informal authority the person will need to navigate, or the undocumented workflows they will be expected to learn and maintain.
And this is not really their fault. This is a result of the antiquated view of the administrative professional role as one of only task completion under direct supervision, instead of the strategic operational and administrative powerhouse the administrative professional career field has become.
What neither party typically examines — and most often does not understand — is the structural context of the role: where it sits in the flow of work, which systems it connects to, which decisions it routes, and what institutional knowledge it will be expected to carry. Because the system the organization runs on is not intentional.
The job description only scratches the surface, capturing just 40% of the true workload. The remaining sixty percent reveals itself gradually and informally, often leaving new hires to navigate these uncharted waters without the structural support they need. This disconnect highlights a gap in the hiring process that most organizations have not yet stopped to examine.
The Sixty Percent Problem
The work that lives outside the job description does not arrive all at once.
It accumulates.
A process that was never formally documented becomes the new hire's responsibility to learn and maintain — because they are the person closest to it. A coordination function that spans three departments becomes theirs by proximity. A reporting workflow that leadership depends on but has never examined becomes theirs because they are the one who made it work the first time.
Each addition is small enough to seem reasonable. The cumulative effect is a role that bears little resemblance to the one that was posted.
This is where scope creep becomes structural. Not because anyone intended it, but because the organization never designed the infrastructure to prevent it.
The job description did not account for the operational reality. So the person in the role absorbed the difference.
And because they absorbed it competently — because administrative professionals are exceptionally skilled at making complexity look manageable — the organization assumes the role is functioning as designed.
It is not. It is functioning because someone is compensating for a design gap.
What This Costs the Organization
The consequences of poorly designed role descriptions extend well beyond the individual in the role.
Turnover becomes structurally expensive. When someone leaves a role that has expanded far beyond its description, the organization discovers the true scope of what they were carrying. Replacing the person is not the primary cost. Replacing the institutional knowledge, the undocumented workflows, and the informal coordination pathways they maintained — that is where the real expense lives. And it is almost always higher than the cost of having designed the role accurately in the first place.
Onboarding becomes unreliable. A new hire trained against the job description is being trained against a fiction. The real onboarding happens informally, over months, as the person gradually discovers what the role actually requires. This creates a prolonged period of reduced capacity that the organization rarely accounts for — because it does not realize the gap exists.
Performance evaluation becomes disconnected. If the job description does not reflect the actual work, then performance metrics derived from that description are measuring the wrong things. The person is being evaluated on 40% of their contribution, while the other 60% — often the most operationally critical work — remains unmeasured and unrecognized.
Salary benchmarking becomes inaccurate. Compensation is typically tied to the described role, not the role actually performed. When the performed role has expanded into territory that would command higher compensation if it were formally recognized, the organization creates a structural equity problem — one that becomes visible only when the person advocates for themselves or leaves.
The Design Problem
The job description is not a standalone document. It is an expression of the organization's understanding of a function within its operating structure.
When that understanding is incomplete, the description becomes a starting point that the person in the role is expected to expand — without formal acknowledgment, without adjusted authority, and often without additional compensation.
This is not a failure of the individual. It is a failure of organizational design.
Specifically, it is a failure to examine three things before the description is ever written:
The operational context. Where does this role sit in the flow of work? What systems does it connect? What decisions does it route? What other roles depend on it?
The informal functions. What work is currently being performed by someone in this space that has never been formally documented or assigned? What institutional knowledge is required that does not appear in any handbook?
The structural capacity. What is the realistic scope of work this role can sustain over time without informal expansion? What happens when demand exceeds that scope — is there a defined pathway for escalation, or does the role simply absorb more?
Most job descriptions are written without asking these questions. And the result is a role that is structurally under-designed from day one.
What Redesign Looks Like
Fixing job descriptions is not about adding more bullet points. It is about changing the design process.
It means involving the people who currently perform or interact with the function — not just the hiring manager — in defining what the role actually requires. It means mapping the operational context before writing the description, so the role is designed to fit the system rather than being retrofitted after the fact.
It means distinguishing between tasks and functions. A task is "schedule the meeting." A function is "coordinate cross-departmental stakeholder availability, identify decision-maker priority conflicts, and structure the agenda to ensure critical items are resolved within the session." The description should name the function, not just the task.
And it means building in a review mechanism — a structured point, perhaps annually, where the described role is compared against the performed role and the description is updated to reflect reality.
This is not a human resources project. It is an operational infrastructure project. Because the job description is not just a hiring tool. It is a design document. And when the design is incomplete, the people in the role pay the difference.
The Structural Question
If your organization is experiencing chronic scope creep in administrative roles, high turnover costs in operational positions, or a persistent gap between what you hire for and what you need, the job description is a good place to start examining.
Not because the description itself is the problem.
Because the description reveals what the organization has and has not designed.
If the role your team is performing looks nothing like the role you posted, the gap is not a performance issue. It is a structural one — and it is worth examining before the next hire.
Comments