A job title is a guess dressed up as a decision. It assumes the shape of a solution before anyone has properly examined the problem.
When a business identifies a gap, the instinct is almost always to translate it into a job title. There is too much marketing work, so the gap becomes “we need a Marketing Manager.” There is too much admin, so the gap becomes “we need an Executive Assistant.” This translation feels efficient, but it quietly narrows the range of solutions under consideration before the actual shape of the work has been examined at all.
The Problem: A Title Assumes the Answer Before the Question Has Been Asked
A job title bundles together a set of assumptions, seniority, scope, full time commitment, that may or may not match the actual work generating the pressure. “We need a Marketing Manager” assumes the gap is best filled by one full time, mid to senior person covering the whole breadth of marketing work. It might be. It might just as easily be two days a week of senior strategic input plus a separate block of hours for content execution, a structure no job posting titled Marketing Manager would naturally produce.
The title is not neutral. It is already a decision, made before the actual volume, seniority, and shape of the work has been honestly mapped, and it quietly forecloses other structures that might fit the real gap better.
Why It Happens: Titles Are the Vocabulary Everyone Learned First
Job titles are the shared language most people learned for describing work, long before they learned to describe workload directly. Ask someone to describe a gap in their team, and the fastest, most natural response is a title, because that is the vocabulary immediately available. Describing the actual shape of the work, its volume, its variability, the level of judgement it requires, takes more deliberate effort, and under time pressure, the easier vocabulary usually wins.
There is also a social dimension. A job title is something that can be posted, searched, and compared against a market rate, and using standard vocabulary makes a hiring process easier to run through conventional channels. Describing a genuinely specific, non-standard workload is harder to standardise, even when it produces a more accurate solution.
What Building Around Workload Actually Looks Like
Starting with workload instead of a title means asking a different set of questions before reaching for a job description. What specifically needs to happen. How often. How much of it requires senior judgement versus straightforward execution. How consistent is the volume across weeks and months. Only once these questions have honest answers does it make sense to ask what structure, and what title if any, actually fits.
This reordering surfaces options a title-first approach tends to miss entirely. A business assuming it needs a full time Operations Manager might, once the actual workload is mapped, discover the real need is a blend, a day a week of senior financial oversight, a day and a half of marketing strategic input, and a more substantial, near daily volume of operational execution, a structure that bears no resemblance to a single Operations Manager job posting, and serves the actual gap considerably better.
It also protects against the reverse mistake, assuming a gap is smaller or more generalist than it actually is. A business that has been informally patching together admin support might discover, once the real volume is mapped honestly, that the workload genuinely justifies a dedicated, full time hire, not the few scattered hours it had been treating the gap as requiring.
Practical Takeaways
When a gap is identified, resist writing a job title as the first step. Write down the actual work instead, what needs to happen, how often, at what level of judgement, and let the structure follow from that description rather than preceding it.
Separate volume from seniority explicitly. A common source of mismatch is conflating “how much work” with “how senior a person,” when these are genuinely different questions that can point toward different structures entirely, sometimes a blend of both.
Treat a job title, once you arrive at one, as a label applied after the structure has been worked out, not a starting assumption that shapes the structure before it has been examined.
Revisit workload-based structures periodically against what actually happened, since the real shape of a gap often becomes clearer only after work has been underway for a while, and a structure built on an early guess deserves to be checked against real evidence, not left in place purely by default.
Frequently Asked Questions
Isn’t a job title necessary at some point anyway, for hiring or for the org chart?
Often, yes, but the point is sequencing. A title applied after the actual workload has been mapped tends to fit the real need considerably better than one assumed at the outset, even if a title eventually gets attached to the resulting structure.
Does this approach take longer than just posting a job?
The upfront diagnostic step takes some deliberate time, but it is usually faster overall than the alternative: hiring against an inaccurate title, discovering the mismatch months later, and going through a difficult correction process.
Does this work for senior or executive roles too, not just operational ones?
Yes, and arguably it matters more at senior levels, since a poorly matched senior hire is more expensive and slower to correct than a poorly matched junior one. Mapping the actual volume and shape of senior-level decisions before assuming a full time executive title is needed often reveals a fractional structure fits better.
How does a business map workload if it has never tracked this kind of detail before?
Even an honest, informal estimate, tracking roughly how much time is currently being spent on a given kind of work by whoever is currently doing it, usually reveals more than assumed. It does not need to be a formal system to be useful, it needs to be honest.
What’s the biggest risk of skipping this step and going straight to a job title?
The biggest risk is building a structure shaped by convention rather than by the actual gap, which tends to produce either wasted cost on unused seniority, unused hours, or a persistent mismatch that never quite resolves the pressure that prompted the hiring decision in the first place.
Start With the Work, Not the Word for It
A job title is a convenient shorthand, and shorthand is exactly what makes it risky as a starting point. The businesses that build the most efficient teams are the ones that describe the actual work first, and let the structure, and eventually the title if one is needed, follow from that description rather than precede it.
Talk to our team about mapping the real shape of your next gap before you write a single job title.