Analyze tasks and entry criteria
6 min read
Lesson objectives
- Link critical tasks to entry competencies and evidence while removing unsupported criteria.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Once a search is authorized, a manager may hand you a three-year-old job description and ask for “someone with the same profile.” The description is a starting point, not evidence that every item still matters. Job analysis identifies what the role actually does, what good output looks like, and which capabilities are necessary when someone starts. It differs from assembling an ideal person's attractive traits. The Office of Personnel Management (OPM) describes a sequence of collecting role descriptions, expert input and performance standards, then identifying critical tasks and entry-level competencies. We use that sequence as a method, not as a rule binding every employer or country.
Where possible, start with at least two kinds of evidence: people doing or supervising the work, and artifacts of the work, such as anonymized service requests and quality measures. Ask the manager about an ordinary week and a peak week. “Manage” and “support” are too broad to assess. State a task as an action, object, output, and setting: “Triage incoming customer requests, identify escalation priority using the approved service table, and record the reason in the system.” This form helps you ask what success looks like and which error harms the service. If the manager says the task is “excellent communication,” treat that as a possible competency, not a task. Ask where communication appears in the workflow and what the employee does in that moment.
Separate a task's frequency from its importance. An information-security incident may occur monthly but carry serious consequences, while frequent basic data entry may require little assessment time. Reviewers can rate each task on frequency and the impact of an error, then identify critical tasks, recording that their ratings are expert judgments rather than universal measurements. Do not multiply arbitrary numbers and present the result as scientific certainty. When two experts disagree, ask for a work example: does one group handle more complex cases, or has the service changed? Resolve the difference by clarifying the task or role boundary before turning a disputed idea into a rejection rule for applicants.
A competency is an observable pattern of knowledge, skill, ability, or behavior that supports work. Link each one to at least one task: knowledge of request categories supports triage; clear writing supports a clarification message; recognizing a critical case supports escalation. “Works well under pressure” is weak unless it specifies a situation and behavior; otherwise it becomes an inconsistent personal impression. A more useful statement is “prioritizes three simultaneous cases by delay impact and explains the ordering.” You can later assess that through a work sample or situational question. A competency with no linked task should be removed or trigger another look at the analysis.
Next ask whether the capability is needed on the first day or can be taught during onboarding. That distinction separates a minimum entry criterion from a capability that can develop later. Familiarity with an employer's ticketing interface may be learnable in a week. Protecting sensitive information or writing an understandable response may be needed before independent case handling. Do not assume a particular degree proves practical capability. Equally, do not discard a qualification genuinely necessary for the role or required by a competent authority: request its task rationale and identify who decides the restriction. Where licensing is local or changeable, refer the matter to the appropriate legal or professional owner. This country-neutral program does not invent a universal licensing rule.
Convert the analysis into a short, screenable person specification. For each criterion, record its linked task, acceptable evidence, whether it is required at entry or can be developed, and a proposed way to assess it. For example, “writes an accurate summary of a 120-word case” can be measured through a short writing sample with known criteria. Years of experience alone do not show what the person writes. Experience can matter, but its duration is a proxy whose relevance must be explained. Avoid “five years in this exact sector” if equivalent experience could perform the task and no analysis explains the restriction. Apply each minimum criterion consistently to all applicants; do not introduce a new preference halfway through screening because a particular candidate impressed the manager.
Fairness does not mean lowering the role's quality threshold. It means each restriction in the notice and screening process has a visible connection to work, and the assessment measures the intended capability rather than incidental familiarity with one tool. Examine working conditions too: the language actually used at work, approved shift hours, available tools, and whether assistance or reference material is allowed. If the job involves writing summaries while consulting a manual, a memory-only test can measure the wrong thing unless immediate recall is a critical duty. Review the task-to-competency table with the manager. Freeze the version used to build the vacancy notice and assessments, and record the reason for any later change.
Lesson summary
Distinguish a vacancy from a measured need, then link tasks to entry competencies. An old description or employer label cannot replace job analysis.