Skill

Origin & evolution

Treating capability as a named, mappable thing produced the skills matrix: a grid of people against competencies, scored by proficiency, used to spot coverage and single points of failure. The matrix makes a quiet but important claim, that capability is an attribute of an individual or group, separate from the role they happen to be assigned and the title they happen to hold.

Julie Zhuo's *The Making of a Manager* frames this as a core managerial responsibility: a manager's job🔨JobUserJob To Be Done: what the user is trying to accomplishView reference → is to know what each person on the team can do well, where they are still developing, and what that aggregate means for the work in front of them. By that reading, the skills matrix is not an HR artefact but the working tool a manager maintains to answer those questions reliably.

The most influential shape for an individual's skill profile is the T. The "T-shaped" idea began as internal McKinsey language for consultants in the 1980s, was articulated publicly by David Guest in a 1991 Independent article on the "Renaissance Man of computing", and reached the product and design world when IDEO's Tim Brown described hiring T-shaped people around 2010 (Wikipedia). The vertical bar is depth in one discipline; the horizontal bar is enough breadth to collaborate across others. A team of pure specialists ("I-shaped") bottlenecks on hand-offs; a team of pure generalists lacks anyone who can go deep.

Where the skill concept earns its keep operationally is the build-versus-hire-versus-buy decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference →. A skills matrix that shows a gap, say, no one on the team can do data engineering, turns an abstract worry into a choice with three named options: grow the capability internally, hire someone who has it, or contract it out. The matrix dates the gap and lets you watch it close.

Will Larson's *An Elegant Puzzle* offers a complementary frame: teams cycle through recognisable states — falling behind, treading water, paying down debt, innovating — and diagnosing which state a team is in depends on knowing where its capability falls short relative to its load. A skill gap that goes unnamed keeps a team stuck in the earlier states; surfacing it, and choosing the right lever (hire, grow, or shed scope), is what moves the team forward.

How it works in practice

A team of six is asked to ship a usage-based billing system. The skills matrix shows deep coverage in frontend and backend, one person at intermediate data engineering, and nobody with payments-domain experience. That is two gaps with different answers. Data engineering is adjacent to skills the team already has, so they grow it: the intermediate engineer pairs with a contractor for a quarter and the matrix moves her to proficient. Payments domain knowledge is far from anything they hold and the deadline is fixed, so they hire it. Six months later the matrix shows the data-engineering gap closed internally and a new permanent hire carrying the payments skill, and the single-point-of-failure flag on billing has cleared.

Skill vs. its neighbours

• Role is a responsibility assigned to someone; a skill is a capability they hold. You need🫀NeedUserA user need, pain, desire, or constraintView reference → the relevant skills to perform a role well, and a skills matrix is precisely the map of which people have the skills their roles demand. Holding the skill does not assign the role, and holding the role does not confer the skill.
• Certification🏵️CertificationCustomer EducationA certification programView reference → is third-party evidence🔎EvidenceValidationData supporting or refuting a hypothesisView reference → that a person has a skill to a defined standard (AWS Solutions🔧SolutionDiscoveryA proposed approach to address an opportunityView reference → Architect, CISSP). The certification validates the skill; it is the proof, where the skill is the underlying capability. A team may hold a skill it has never certified, and a lapsed certification does not erase the capability.
• Team is the group that, collectively, is skilled in a set of capabilities. A team's skill profile is the aggregate of its people's, plus the practices it shares, and it is what a capacity plan🗓️Capacity PlanTeam & OrganisationA plan for allocating team capacityView reference → is really sizing.

In the graph

In the Unified Product Graph, skill🎓SkillTeam & OrganisationA skill or competency within a team is a leaf in the Operations & Quality region, team_org domain. Two edges carry its meaning: a certification🏵️CertificationCustomer EducationA certification programView reference → proves competence through certification_validates_skillCertificationvalidatesSkillcross-domain, and a team🫂TeamTeam & OrganisationA cross-functional teamView reference → records its capabilities through team_skilled_in_skillTeamskilled inSkillhierarchy. Connecting teams to skills, and skills to the certifications that evidence them, turns the skills matrix into a live query rather than a stale spreadsheet: you can ask which skills a team lacks for the work it owns, which capabilities rest on a single person, and where a build-or-hire decision is overdue.