The average role card is 18 months out of date, written in HR language nobody outside the profession uses, and treats a role as a list of tasks rather than a capability footprint.
Role cards persist because they fit the grading system, not because they help the work.
A capability signature is the alternative. It describes a role in 200 to 300 words, covers what the role needs in capability terms (not task terms), and can be updated in 20 minutes. Most importantly, it opens internal mobility in ways static role cards actively block.
What is wrong with the role card
Three problems:
Task drift. Role cards are written as a list of responsibilities, which means every time the work changes, the document is stale. Inside 18 months, almost any role card overstates historical activities and understates current ones.
Capability invisibility. Tasks answer "what do they do?" They do not answer "what capability does this role need to have?", which is the only question that matters for hiring, internal mobility, succession, or development planning.
Mobility friction. When an internal candidate is compared against a role card written for the previous incumbent, they almost always come up short on the literal tasks. A capability signature would show that they are a 90% match on the underlying capabilities.
What a capability signature contains
A signature has four short sections, usually fitting on one page.
1. Purpose (two to three sentences). Why this role exists, in plain English. Not the job description. The why.
2. Outcomes owned (three to five bullets). The outcomes this role is accountable for in the next 12 months. Written as outcomes, not activities.
3. Capability footprint. 8 to 12 capabilities drawn from the organisation's taxonomy (see skills taxonomy without drowning for a light model), each with a required proficiency level.
4. Stretch capabilities. Two to three capabilities the person should grow in this role, the development the role offers its incumbent.
That is it. No compliance language. No boilerplate. No 40-line list of responsibilities.
Why the signature unlocks mobility
Two effects.
First, it lets a hiring manager see a role as a capability pattern instead of a task list. That shifts the internal candidate conversation from "have you done this exact thing?" to "do you have the underlying capability?", which is the only fair question.
Second, it lets employees see roles as growth paths. A person in Role A can look at the signature for Role B and see exactly which capabilities they already have at the required level and which two or three they would grow into. That turns the career conversation from vague aspiration into a concrete plan.
When paired with a credible capability signal per employee (quarterly calibration evidence, see replacing the annual review with quarterly calibration), internal mobility becomes a transactable system instead of a hopeful one.
Building your first signatures
Do not try to rewrite every role in the organisation. Start with 10.
Pick 10 roles that matter for your current growth strategy, usually three or four critical roles in each of two or three core functions. Use the template structure above. Build signatures for all 10 in one week with the function leader.
Pressure-test them in two places: with the incumbent (do they recognise the role?) and with an external benchmark (does this describe the role as the market sees it?). Adjust.
Then publish them, alongside the old role cards if your compliance or grading system requires the role cards to exist. Over 12 months, the signatures become the trusted artefact; the role cards slowly fade to pure compliance purpose.
How the capability signature interacts with pay
A common worry: does this break the grading system?
It does not, if you design it right. The role card and grading system stay in place for HR compliance and compensation. The capability signature sits alongside, written in the language of the work and the worker.
Two distinct purposes. One system serves compliance; the other serves the people strategy. The moment you try to merge them, you end up with an artefact that serves neither.
When to retire the role card entirely
Some organisations eventually retire role cards altogether. It takes two to three years and typically happens alongside a job architecture refresh. The signatures become the primary artefact; compensation bands are attached to a capability mix rather than to a named role.
If you are not ready for that transformation, signatures alongside role cards is the pragmatic answer for 2026.
Where to start
Pick 10 critical roles. Write signatures for them in one week using the structure above. Publish alongside your existing artefacts. Measure two outcomes over the next quarter:
- Internal application rate for those 10 roles (target: 30%+ lift)
- Manager confidence in assessing internal candidates for those roles
If both move, expand. If only one moves, the limiting factor is usually the capability signal, not the role description.