Performance and learning diagnosis · Lesson 3

Capability mapping from task to evidence

5 min read

Lesson objectives

  • Map a role into observable tasks, proficiency levels and evidence of current versus future capability.
Reading tools

When a manager says “raise team capability,” the name of the capability is too broad to guide a decision. A capability map turns a role into observable tasks and describes the proficiency needed in a defined context. Start from the work process rather than a course catalogue. What output does a colleague or customer rely on? Which steps produce it? How does an ordinary task differ from an exception? Who reviews the output and corrects an error? “Complaint handling” then becomes tasks such as coding the cause, assigning an owner and telling the customer a traceable next step. A job title is not itself a capability; two people with the same title may perform different tasks.

Write each task with an action, object and performance condition. “Knows the complaints system” is hard to observe. “Selects the correct cause code after reading the record and available evidence” can be checked. Specify the output and authority boundary: can an agent close the complaint, or only refer it? Which cases require escalation? A change in authority changes the capability requirement even if a broad skill label stays the same. Review the description with a task performer and the process owner. A manager may miss invisible work; a practitioner may describe a rare exception as though it were routine.

Proficiency levels help when they describe performance rather than rank people. In this example, a novice codes a standard case with a code guide and review; a practitioner independently codes common cases and explains the choice; an advanced practitioner handles an ambiguous case, recognises when to escalate and can review a colleague's work. This is a local task rubric, not a universal professional scale or a judgement of someone's worth. Attach evidence to each level: classification of fresh cases, approved work records or observation against one standard. Years in a role are not equivalent to proficiency, and self-rating alone is not conclusive evidence.

Once the requirement is stated, estimate current capability with proportionate evidence. For a high-impact task, combine perspectives: work records with appropriate redaction, a task simulation, and supervisor observation using a clear rubric. For a low-impact task, a small sample may guide an initial trial if uncertainty is declared. Record the required level, observed level, gap, evidence quality and affected population for each task. “Unknown” is better than an apparently exact number without measurement. The numerical distance between levels 3 and 1 does not translate into two hours of training: these levels describe performance, while time depends on practice difficulty and opportunity.

Add a future view without pretending to predict it. If the organisation has approved a new system for release in six months, checking an automated decision or explaining an exception may become a task. Record the basis: approved project plan, limited pilot or suggestion. A future task backed by an approved plan can enter the development budget. An unapproved possibility belongs on a watch list, not in a mandatory need for all staff. Connect the map to business direction where that direction is known, but do not use broad strategic language to conceal an undefined task. “Be adaptable” is less useful than “reclassify a request when new customer information appears while preserving the reason for the decision.”

A capability map does not automatically order a course. If most employees classify a case correctly in simulation but err only when the system hides its code list, the observed gap sits in the work environment. Record the constraint and route it to the system owner. If practitioners succeed on standard cases but fail on exceptions, design practice on exceptions with a decision and escalation aid instead of repeating the interface introduction for everyone. A mixed-experience team may need targeted support rather than removing every employee from work. The map makes this choice defensible because it shows who needs which support and why.

Validate the map in reverse. Select an actual output and ask whether the mapped tasks and levels explain how it is produced and reviewed. Then select a map row and ask whether its evidence can be gathered fairly and whether the worker has an opportunity to perform it. An unobservable row usually needs rewriting. Record the review date and version because processes change: an old map can turn an obsolete skill into a training requirement. Do not distribute individual results beyond authorised access, and keep role requirements separate from judgements about a particular person.

Lesson summary

Map a role into observable tasks, proficiency levels and evidence of current versus future capability.