liveBook · Manning

Competency matrix

As explained in Think Like a Software Engineering Manager

A competency matrix is a structured table that maps role competencies to evidence of demonstration and progress.

When a team member’s contributions are strong but unevenly documented, a competency matrix makes the gaps visible. It maps role competencies to how they are demonstrated and the progress made against them. section 3.1.1

Use the matrix to:

  • Compare demonstrated impact with role capabilities and expectations. section 3.1.1
  • Record evidence using situation, behavior, and impact. section 3.1.1
  • Track each competency as To do, In progress, or Done. section 3.1.1

Example: technical skills

Dave addressed a missing continuous data-streaming mechanism, explored the architecture with senior engineers, documented design trade-offs, and delivered under a tight deadline. The service launched on time and reduced message latency by more than 80 percent. section 3.1.1

Table 3.1 A competency matrix representing a sample gap analysis document
Competency
How do you demonstrate it?
Status (To do, In progress, Done)
Technical skills. Employee should be adept at coding and system design and have experience with large-scale system designs.
Situation 1—Dave was tasked with delivering a project to build a continuous data streaming service due to the missing mechanism.
Behavior—Dave stepped up to understand the problem statement and did a deep dive into the architecture design. He worked with senior engineers on the team and developed a technical design document detailing the pros and cons of each approach. Next, he implemented the project under a tight deadline.
Impact—His efforts led to a timely launch of the streaming service and helped reduce message latency by more than 80%.
Situation 2—<>
Behavior—<>
Impact—<>
Done
Participation in technical events.
Situation 1—<>
Behavior—<>
Impact—<>
In progress
Sharing learnings and expertise with cross-functional partners and having influence across teams.
Situation 1—<>
Behavior—<>
Impact—<>
In progress
Helping to improve operational excellence metrics for the team.
Situation 1—<>
Behavior—<>
Impact—<>
To do

Use the sample gap-analysis table as a reusable template for documenting competencies, evidence, and status across team members. section 3.1.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines a reusable evidence-and-status template, without detailing a broader scoring system.
Examples
Uses technical skills, system design, streaming-service delivery, design documentation, and latency reduction as evidence.
What it assumes
Assumes familiarity with role levels and employee development conversations.
What you can do after
Build it from scratch as a reusable table for identifying and addressing individual competency gaps.
How it connects
Connects gap analysis with role capabilities, expectations, career conversations, and internal mobility.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.