Most hiring mistakes happen before you post the job
Why role design matters more than job descriptions, and how it shapes who you actually hire.
Why role design matters more than job descriptions, and how it shapes who you actually hire.
A gap emerges: someone leaves, the business grows, or you're launching something new. Instinctively, you jump to defining the vacancy. Maybe you open a document, ask an AI to draft a job description, or consult HR. But you often land in the same spot: with a role description that may not reflect what your business truly needs.
That is the problem. Not the description itself, but the assumption that the description is where you should start.
"The hiring mistake nobody talks about is made before anyone reads a single CV, before the job is even posted."
What is missing in most hiring processes is not a better template or a more experienced recruiter. It is role design. And role design cannot happen without first understanding the process that the role exists to serve.
The job description trap
A job description simply describes a vacancy. It tells you what the last person did, what a competitor posts, or what AI generates from a title. At best, it's a rough approximation of the role's function. At worst, it attracts candidates who look good on paper but underperform in reality.
The reason is structural. A job description works backwards from the label, such as "Operations Manager", "Senior Accountant", or "Head of Sales", and fills in competencies, responsibilities, and requirements assumed to belong to that label. The process the role operates within, the tasks that process requires, and the skills those tasks demand are rarely examined. They are assumed.
AI makes this even trickier. When you ask a model to write a job description, it pulls from thousands of similar postings. What you get is a statistically average version of the role, not what your business specifically needs.
What does role design actually mean?
Role design begins one level upstream. Before the role, there is a process. Before the process, there is a business function. The logical chain runs in one direction only, and it produces far more than a list of competencies.
Each layer is delivered from the one before it. None can be assumed.
When you map a process, really break it down, step by step, you see exactly what each stage requires. Not generalities, but specifics: What decisions happen here? What information is needed? What does great execution look like? These questions build a task profile tailored to your business, processes, and current growth stage.
From that task profile, three things emerge simultaneously:
- the required skills,
- the tools the person will use at each step,
- and the points in the process where the role crosses into other functions.
Each of these is a distinct hiring dimension, and each produces a distinct set of interview questions.
Skills: what the tasks actually require
Skills from task analysis are specific, not generic. You're not just seeking someone with "strong analytical skills." You want someone who can read summary-level financial data, spot variances, form hypotheses, and explain findings to non-finance colleagues, because that's what step four of your monthly reporting process actually demands.
This specificity changes the interview entirely. Instead of asking "Are you comfortable with financial reporting?", you ask: "Walk me through how you would approach a situation where your numbers tell a different story than the operational team believes." The task profile makes the question obvious. The job description never would.
Tools: mapping the software layer
Every process step runs on something: a CRM, a project management platform, an accounting system, or even a tangle of spreadsheets held together by institutional memory. Most hiring treats tool familiarity as a checkbox, "proficient in X," without connecting it to what people actually do with those tools at each process stage.
Process mapping resolves this precisely. When you can see that step three requires the person to build and maintain a pipeline report in your CRM, reconcile it against finance data in your ERP, and present a weekly summary to the management team, you can ask targeted questions: how they approach data integrity across systems, how they structure reports for non-technical audiences, what they do when the numbers from two platforms disagree.
These are not general questions about software knowledge but task-specific probes that reveal whether the candidate has operated at the level your process demands. The tool list from your process map is the input. The interview questions write themselves.
Coordination: where the role touches the organisation
Process mapping does something that no job description captures: it shows you exactly where the role crosses functional boundaries. Every step that requires input from another team, manager sign-off, handoff to a downstream function, or alignment with an external stakeholder is a coordination point. And coordination points reveal something critical about the person you need, not their technical skills, but their behavioural profile.
A role with five internal coordination points per week needs someone who thrives in ambiguity, communicates proactively, and builds relationships across teams. A role that mostly stays in its own lane until a single formal output requires a different personality, someone who can sustain focus and quality without constant feedback.
Neither profile is better. Both are right for different process architectures. The point is that you cannot know which you need without first mapping the process. And without that knowledge, culture fit becomes guesswork, an impression formed in an interview room rather than a conclusion drawn from operational reality.
The accountant problem
The obvious objection is the standard role. An accountant is an accountant. Surely these roles are well-defined enough that the process analysis is unnecessary?
Consider two businesses, both hiring for the position of "Senior Accountant."
The first is a twelve-person business where the person owns the entire financial operation: monthly close, payroll, supplier relationships, cash flow forecasting, and board-level reporting, largely independently, with direct input to the founder.
The second is a 200-person business with a finance team, where the accountant handles a defined segment of the ledger within an established process, supported by a CFO and colleagues above and alongside.
Same job title. Completely different task profile. Different tools in use. Different coordination density. Different skills required. Different behavioural characteristics that will determine success. A generic job description for "Senior Accountant" will attract both types of candidates and give you no basis to distinguish between them in the interview. Process mapping makes the distinction explicit before you post a single word.
What this unlocks
Done right, role design delivers what job descriptions never can: a precise candidate profile tailored to your actual business, not a statistical average. It produces interview questions that probe real capability rather than rehearsed answers. It gives you a basis for comparison between candidates that is grounded in what the role actually requires, not what a title suggests. And it connects every hiring decision back to the process it is meant to serve, which is the only place where the value of a new hire can actually be measured.