Competency mapping: turn changing tasks into specific learning needs

Competency mapping connects the work a role must perform with the knowledge, skills and behaviour needed to perform it. For a change programme, start with the tasks that become different. Define observable performance under stated conditions, then examine the available evidence and agree how to close the gap.

A list of qualities such as “digital mindset”, “adaptability” or “good communication” is too broad to tell a learner what to practise. “Given a routine application, identify a missing enclosure and send the approved request to the applicant” gives someone a task, a context and an outcome they can examine together.

The map should lead to a support decision. Some gaps require explanation or practice. Others arise from missing access, unclear authority or insufficient opportunity to perform the work. This guide provides a small, original mapping process for development; it is not a personnel ranking instrument or a certification framework.

Clarify what competency means in this map

The U.S. Office of Personnel Management describes a competency as a measurable combination of characteristics needed for successful work, connecting competencies with how tasks are performed. Its competencies guidance supports tying descriptions to work rather than using an attractive label alone.

Different frameworks define competence and competency differently. Choose a working definition and make it explicit. Here, the focus is a person’s demonstrated ability to perform a particular task appropriately under agreed conditions. Knowledge of a rule, confidence about applying it and actual performance remain separate pieces of evidence.

The distinction connects with ADKAR’s knowledge and ability elements. Someone can explain a procedure yet still need supervised practice. Someone else may demonstrate it competently while lacking permission to use the relevant system in their assigned role.

Keep the map’s purpose visible. A development conversation asks what would help someone perform the work. A selection or disciplinary decision has different consequences and demands. Use change contracting to agree the purpose, access to notes and decision boundaries before collecting evidence. Do not quietly reuse informal development notes for a consequential decision they were not designed to support.

Start with an observable task

Consider a hypothetical municipal office introducing an online permit-application process. Caseworkers previously collected paper forms; they will now review uploaded documents, request missing information and route exceptions. The example concerns administrative preparation, not advice on permit law or a real office’s assessment criteria.

The manager initially proposes training in “digital competence”. The role holders identify a more useful first task: distinguish a complete routine application from one needing an enclosure, use the approved response and record what remains outstanding. A separate task concerns recognising when a case needs an authorised specialist decision.

Observe the current work with appropriate agreement and protected or invented records. Ask a role holder to walk through a normal case and one consequential exception. Note the information used, the judgement made, the tool involved and the boundary at which someone else must decide.

OPM’s job-analysis guidance connects job tasks with the competencies required to perform them. This developmental adaptation uses the same distinction, without claiming that a short workshop supplies the evidence required for formal employment selection.

Use stakeholder mapping to include the person receiving the handoff. A caseworker’s task may appear complete locally while leaving the specialist without the information needed to act. If the process crosses several roles, a service blueprint can expose the missing interface before it becomes a training requirement.

Describe performance without guessing at personality

Write a task statement with four parts: the situation, the action, the required standard and the support or authority available. For the invented office: “Using the current reference and a routine practice case, identify missing required enclosures, prepare the approved request and record the next review action; refer uncertain cases to the specialist.”

Use verbs that another person could observe: locate, compare, explain, record, prepare, check or escalate. “Be proactive” could mean several incompatible behaviours. Ask what a person would actually do differently, and under what circumstances.

Include judgement when it matters. An exception task may require someone to explain which information is missing, consider a second interpretation and decide when they must ask for help. Avoid reducing every competency to a speed target or a count of completed steps.

For technology roles, the SFIA framework distinguishes professional skills from levels of responsibility and considers attributes such as autonomy and complexity. It also separates demonstrated experience from a qualification that only tests knowledge. This guide does not reproduce SFIA levels; its practical lesson is to specify how independently and under what complexity the task is expected to be performed.

In our example, “handles routine cases using the reference” and “decides an unfamiliar exception independently” are different expectations. The latter might not belong to the caseworker’s role at all. Clear escalation can be competent performance, rather than evidence of a deficit.

Build a small role-based map

Start with a handful of changed tasks. A map covering every possible behaviour becomes difficult to maintain and tends to conceal the important transition. Separate the common requirement for a role from an individual’s development record.

The following map is hypothetical and illustrative:

Changed task	Observable performance	Evidence and current uncertainty	Support decision
Review a routine upload	Identify missing enclosures using the current reference	Practice case attempted; unfamiliar file format not yet checked	Add a second supported case
Request information	Prepare the approved message and record the next action	Correct draft, but no permission to send from the role account	Administrator to provide approved access
Handle an exception	Explain the uncertainty and route it to the specialist	Self-reported confidence; no task evidence yet	Walk through an exception with the specialist
Cover a colleague’s queue	Locate outstanding actions and confirm ownership	Normal handoff observed; absence scenario untested	Rehearse an absence handoff

Use a separate working record for dates, owners and the next check. Keep the public team map focused on coverage and support rather than displaying names against coloured ability scores. Decide who can see personal notes and how a role holder can correct an inaccurate entry.

Labels such as “not yet checked”, “with support” and “demonstrated in the stated case” are more honest than an unexplained one-to-five score. They describe the available evidence without pretending that a short exercise measures a stable personal trait.

Gather evidence and record its limits

Combine the role holder’s account with suitable task evidence. A conversation can identify prior experience and overlooked strengths. A work sample or rehearsal can show what happens in a specific situation. Observation can reveal conditions that neither party mentioned.

Choose a proportionate check and explain it before beginning. In the invented office, use fabricated application records and the current approved reference. Ask the colleague to narrate where they would check a rule and when they would involve the specialist. Do not turn a learning exercise into an undisclosed test.

CIPD’s learning-needs guidance recommends connecting current and future capability requirements with evidence at individual, team and organisational levels. It describes several information sources and cautions against defaulting to a course. The map here is one practical way to organise such a discussion, not an official CIPD template.

Interpret contradictory evidence carefully. A colleague may perform the task in a quiet rehearsal but struggle during a queue interruption. That might indicate a need for further practice, a different interface or protected attention. Conversely, failure caused by a broken file viewer is not evidence that they lack document-review skills.

Use systemic questions to examine differing accounts without assuming that the first explanation is correct. Retain enough context to avoid comparing unlike cases. A single successful attempt does not establish performance across all exceptions or over time.

Choose development that matches the gap

Distinguish at least four types of gap. Missing knowledge may need a concise explanation and reference. An unfamiliar task may need demonstration, practice and feedback. Judgement may need contrasting cases and discussion with an experienced colleague. An environmental obstacle needs someone able to alter the environment.

The COM-B paper distinguishes capability, opportunity and motivation in behaviour-change design. Applied to this mapping exercise, an inability to send an approved message could arise from missing knowledge, unavailable access or a concern about the task’s consequences. The map should keep those explanations open until they are checked.

In the hypothetical office, one caseworker prepares a correct message but cannot send it from the assigned account. Their next action is an access fix owned by the administrator. Another needs help recognising the exception boundary, so the specialist provides two contrasting practice cases. Sending both colleagues to the same generic course would leave one gap untouched.

Write a learning goal that matches the gap: “After supported practice, the caseworker will review an unfamiliar routine case using the reference and identify when escalation is required.” Name who provides practice, what support remains available and when a later task will be checked. Use the learning-transfer playbook to plan ordinary opportunities for application.

Agree priorities and protect opportunity to practise

Prioritise by the consequence of the task, how soon it is required, how often it occurs and whether another person can provide safe coverage. These are discussion criteria, not a mathematical readiness score. A rare but consequential exception may need an escalation arrangement before a frequent low-risk task needs refinement.

The manager must make practice possible. If the colleague receives the same workload plus two hours of training, the development plan has not resolved the capacity question. Set an achievable learning sequence and identify who covers ordinary work during rehearsal. Where shared expectations discourage asking for help, a focused culture analysis can examine the work routines and signals behind that condition.

Where knowledge depends on a colleague moving roles, combine the map with a knowledge-transfer plan. Where the requirement comes from a new application, connect it to the software rollout, including permissions, support and a pilot boundary.

Check team coverage as well as individual progress. One expert able to handle every exception is still a fragile arrangement if nobody can cover their absence. Decide whether the answer is developing another person, simplifying the process or maintaining a specialist escalation service.

Revisit the map when the work changes

Return to the task after the learning opportunity. Ask what the person can now do, which conditions have changed and what remains uncertain. Add the scope and date of the evidence. A completed course can support the record, but it should not replace a relevant demonstration.

Use change readiness to bring remaining gaps into the implementation decision. Missing coverage may justify a narrower initial rollout. An outstanding permission can block the task even when everyone understands it. Keep those issues with the owners able to resolve them.

Update the map when the workflow or reference changes. Remove tasks that have disappeared and revise performance expectations when authority is reallocated. A map copied from the launch workshop can become misleading if it still describes a task nobody is permitted to perform.

Evidence and limitations

The institutional and framework sources support linking tasks, capabilities, responsibility and development. COM-B supports considering working conditions alongside individual capability. None validates this original worksheet as a psychometric instrument or establishes that its descriptive labels predict future performance.

The municipal-office case is hypothetical. Its tasks and reference checks are illustrations, not legal standards, employment-selection advice or a complete assessment protocol. Formal personnel decisions require a suitable process and evidence for their consequences.

Keep the map as a revisable agreement about work and support. Its usefulness comes from specificity: an observable task, an honest evidence boundary, a support owner and a next opportunity to check performance.