Skill Matrix

Purpose

A Skill Matrix creates a transparent, shared view of who knows what in a team. By mapping individual competency levels across the skills that matter most, the team can identify single points of failure, plan cross-training, and make informed decisions about hiring and delegation.

At a glance

How to run

1. Define the skills (15 min): Collectively brainstorm the skills relevant to the team’s work. Aim for 10–20. Include technical, process, and interpersonal skills. Write each as a column header on a large grid.
2. Define the scale (5 min): Agree on a simple rating scale, e.g.: 0 = No knowledge, 1 = Beginner, 2 = Can do with help, 3 = Can do independently, 4 = Can teach others.
3. Self-assessment (15 min): Each person rates themselves across all skills. Use sticky dots, numbers, or a digital spreadsheet.
4. Peer calibration (optional, 10 min): In pairs, compare ratings and discuss surprises. Adjust if needed — people often under- or over-estimate themselves.
5. Analyse the matrix (10 min): Look for patterns: skills where only one person scores 3+ (bus factor risk), skills where everyone is low (training need), and skills that are well-covered (strengths).
6. Action plan (5 min): Agree on 2–3 development priorities: cross-training pairs, courses, or mentoring arrangements.

Materials needed

• Large grid (whiteboard, flipchart, or spreadsheet)
• Sticky dots or markers for rating
• Pre-prepared list of candidate skills (optional, to seed the brainstorm)

Pitfalls & common mistakes

• Too many skills: Beyond 20, the matrix becomes unwieldy. Prioritise the most critical ones.
• Treating it as a performance review: Emphasise that this is a team planning tool, not an individual evaluation.
• Never updating: Skills evolve. Schedule a refresh every 3–6 months.
• Ignoring soft skills: Including only technical skills gives an incomplete picture.

Inclusion & accessibility

• Allow private self-assessment before any public sharing.
• Use a digital format so remote team members participate equally.
• Frame low ratings positively — they represent learning opportunities, not deficiencies.
• Do not display the matrix in contexts where it could be used punitively.

Variations

• Aspiration layer: Add a second colour for "I want to grow this skill" to surface learning interests.
• Team-of-teams version: Create matrices per team and overlay them to find cross-team synergies.
• Star chart: Replace numbers with star/dot visualisations for a more visual impact.

When NOT to use this

• In low-trust environments where people fear being judged for low ratings.
• When management uses it as a stealth ranking tool — it must remain a team-owned artefact.
• For very small teams (2–3) where a simple conversation achieves the same result.

Source & further reading

• Jurgen Appelo, *Management 3.0* (Addison-Wesley, 2011)
• Practice library of agile leadership practices — Competency Matrix
• Henrik Kniberg, *Scrum and XP from the Trenches* (Lulu.com, 2015)