A spreadsheet full of scores can look like a clear picture of a team’s capabilities. Without agreed definitions and recent examples, it may be little more than a collection of impressions.
Start with the work the team actually needs to perform. “Communication” is too broad to assess usefully. “Explain a project delay to a customer with a revised plan” describes an observable task. Keep the first matrix small enough that people can discuss every entry.
Define the levels together
Use plain descriptions such as “needs guidance,” “can complete independently” and “can support others.” Explain what evidence would support each level. Avoid pretending that a one-to-five scale has mathematical precision when the difference between its numbers has never been defined.
Invite each person to contribute examples and identify areas they want to develop. A manager may know about one project while missing work done elsewhere. Treat disagreement as a prompt to examine the evidence, not as proof that someone lacks self-awareness.
Add a date and a next opportunity
A useful entry might include the task, current level, a recent example, a review date and the next chance to practise. That makes the matrix changeable. Someone who needed support six months ago should not carry the same label indefinitely.
- Record demonstrated work rather than personality judgments.
- Distinguish lack of opportunity from lack of ability.
- Restrict access to information that affects individuals.
- Explain how the matrix will and will not be used.
Use the overall picture to plan mentoring, project coverage and learning time. Do not turn every strong performer into the default trainer without discussing workload. Teaching others is itself a task that needs time and support.
At the next review, ask whether the matrix changed any practical decision. If it only generated coloured cells, simplify it. Its value comes from helping people get suitable work and support, not from producing a more elaborate ranking.