Job Task Analysis: How to Write Accurate Role Profiles for Hiring and Development

Most job descriptions are either copies of the previous job description with minor edits, or wish lists written by a hiring manager in an hour. Neither reliably describes the work. Job task analysis is the discipline of understanding what a role actually involves before writing the hiring criteria and development expectations around it.

This guide covers how to conduct one, what to do with the output, and when it's worth the investment.

What Job Task Analysis Is

Job task analysis (JTA) is a systematic method for identifying and documenting the specific tasks, skills, and knowledge required to perform a role effectively. It answers:

• What does someone in this role actually do day-to-day, week-to-week?
• Which tasks are essential to the role and which are peripheral?
• What skills, knowledge, and behaviours enable strong performance?
• What distinguishes high performance from average performance?

The output is a role profile that can anchor hiring criteria, interview questions, performance expectations, and development plans - all built from the same foundation.

When JTA Is Worth the Investment

Not every role needs a full JTA. The investment is proportional to:

Hiring volume - roles you hire for frequently. Getting the criteria right for a role you fill ten times a year pays off faster than for one you fill once every three years.

Consequence of error - roles where wrong hires are expensive or high-stakes. Technical specialisms, leadership positions, client-facing roles.

New or significantly changed roles - where no accurate reference exists. If you're hiring for a role that didn't exist before or that has changed substantially (common in growing organisations or post-merger), you have no reliable prior job description to work from.

Persistent underperformance or high turnover - if a role keeps producing people who struggle or who leave, the job description is often part of the problem.

The Analysis Process

Step 1: Identify Your Sources

JTA draws from three sources:

Incumbents - people currently doing the job. They know what the work actually involves better than anyone. For an accurate picture, include both high performers and average performers - their accounts will differ, and the differences are informative.

Line managers - people who manage the role. They can describe what they observe, what they value, and where performance gaps most often emerge.

Outputs and artefacts - examples of real work: reports, project deliverables, client communications, code, whatever the role produces. Reviewing actual outputs often reveals tasks that people don't think to mention in interviews because they're so routine.

Use at least two or three sources for each role. Single-source JTAs reflect that source's perspective, not the role.

Step 2: Structured Observation (Where Possible)

For roles where it's practical, shadow a high performer for part of a day. What you observe will differ from what they report. People routinely underestimate the communication and coordination work in their roles, and overestimate the technical complexity.

This isn't always possible - senior leadership roles, remote work, client-facing roles with confidentiality concerns. In those cases, the interview methods below carry more weight.

Step 3: Structured Interviews

Ask incumbents and managers a consistent set of questions:

Task inventory: "Walk me through a typical week. What are the main things you spend time on?" Then: "Are there tasks you do monthly or quarterly that are important but don't come up week to week?"

Critical incidents: "Tell me about a situation in the last year when someone in this role handled something very well. What did they do?" And: "Tell me about a situation where someone in this role struggled. What was happening?"

Skill and knowledge requirements: "What does someone need to know to do this job well? What can you learn on the job versus what do you need to come in with?"

Performance differentiation: "What separates strong performers from average performers in this role? Not personality - what do they actually do differently?"

Take verbatim notes. You'll analyse the content afterward.

Step 4: Task Inventory and Rating

Compile all tasks mentioned across your sources into a master list. Remove duplicates and near-duplicates. Then rate each task on two dimensions:

Frequency - how often the task is performed (daily, weekly, monthly, occasionally, rarely).

Importance - how critical is the task to successful role performance? A task done rarely can still be high-importance if failure at it has significant consequences.

A simple rating scale (1-5 for each dimension) works well. Plot tasks on a frequency/importance matrix. The high-frequency, high-importance quadrant contains your essential tasks - these anchor your hiring criteria. Low-frequency, low-importance tasks can be noted but shouldn't drive selection decisions.

Step 5: Competency Mapping

From the critical task list, identify the underlying skills, knowledge, and behaviours required. Group related tasks under the competencies they require.

For example, a series of tasks involving written client reporting, stakeholder briefings, and cross-functional updates all draw on communication competence. Rather than listing forty individual tasks in a job description, you identify communication as a key competency and specify what it looks like at the required level.

This mapping connects the JTA to your competency framework (if you have one) and makes the output usable in hiring and development contexts.

Using the Output

Job Descriptions That Reflect Real Work

Write the job description from the task inventory and competency map, not from the previous job description. Structure it around:

• The three to five most important deliverables the role is accountable for
• The competencies required, with brief descriptions of what those competencies look like in practice for this role
• The essential requirements (skills and knowledge the person needs from day one) versus preferred (things they can learn)

Avoid: wish-list requirements that don't appear anywhere in your task analysis ("excellent strategic thinking" in a role with no strategic scope), credential requirements that aren't linked to specific task demands, and job title inflation.

Skills-Based Hiring Criteria

From the competency map, derive your interview questions, assessment exercises, and scoring rubrics. Each selection method should be traceable back to a task or competency identified in the analysis. If you can't explain why you're assessing something, you probably shouldn't be.

This is also your legal defensibility framework. Selection criteria built from JTA can be justified as job-related. Selection criteria built from convention, gut feel, or previous job descriptions often can't.

Development Plans Anchored in Role Reality

JTA output is useful beyond hiring. When a manager and an employee discuss development, the most useful starting point is the actual task demands of the role. Where is the person currently below the required proficiency on the essential competencies? What does development in that area look like in practice?

Development conversations grounded in specific task demands - "you're doing the routine data analysis well, the gap is the more complex modelling work required for the quarterly forecasting cycle" - are more useful than conversations grounded in abstract competency language.

Common Shortcuts (and Their Costs)

Skipping the incumbent interviews. Managers often have outdated mental models of roles that have evolved since they last did the work themselves. Analysis without incumbent input misses how the role actually operates.

Using O*NET or ESCO profiles without adaptation. Occupational databases like O*NET provide useful starting points for standard roles. They're not substitutes for analysing the specific variant of a role in your specific organisation - the context that makes high performance possible or impossible here.

Treating the JTA as a one-off exercise. Roles change. A JTA from four years ago for a role that has since incorporated new tools, new scope, or new team structures is now a liability rather than an asset. Build in review cycles linked to significant role changes.

The organisations that hire consistently well don't have better instincts. They've done the upstream work of understanding what roles actually require - and built their selection and development systems around that reality.

Once your role profile is complete, the next steps are writing a job description that reflects it and building the structured interview questions that test the competencies you identified.