Team Composition Matrix¶
Role matrix — instantiates Compositional Assembly
Maps candidate people against the roles, skills, and decision rights a capability needs, exposing coverage gaps, authority collisions, and who owns the whole.
A Team Composition Matrix is the grid that maps people against the roles, skills, and decision rights a capability requires — a who-covers-what view whose whole is a functioning team, not a product or a document. Its defining trait is that the components are human role-holders: it defines what each role must contribute, marks who holds it, and names who owns the team's overall coherence. Laid out as a matrix, it exposes the three failures a roster hides — a gap (a needed role no one holds), a collision (two people claiming the same decision), and an unowned whole (no one accountable for the capability as a whole). It does not catalog parts or draw how work flows between roles; it answers "does this group of people actually cover every role the mission needs, and who decides?"
Example¶
A game studio spins up a team for a new title and, instead of trusting that "we hired good people," builds a composition matrix. The columns are the roles and decision rights the capability needs: creative direction, gameplay engineering, engine and tools, art direction, audio, production, QA, live-operations — plus the standing decisions of creative direction, technical architecture, and ship / no-ship. The rows are the people, and each cell marks primary, backup, or none.
Read as a grid, three problems jump out. The live-operations column is empty — a role the launch plan assumes but no one actually holds. Two senior engineers are both marked primary on "technical architecture" — an authority collision that will stall every hard call. And the ship / no-ship decision has no owner at all. The studio hires a live-ops lead, splits architecture authority cleanly (one owns the client, one owns the backend services), and names the executive producer as the accountable owner of the ship decision. The matrix governed role coverage and authority — what a headcount list and an org chart both silently miss.
How it works¶
What makes this a mechanism rather than a staffing list is that it tests coverage and authority against the roles the whole actually demands:
- State the roles the whole needs. Enumerate the required roles, the skills each carries, and the standing decision rights — the columns the team will be judged against.
- Map people to roles. Mark who holds each role, and at what depth (primary, backup, none), so coverage is a claim on the grid rather than an assumption.
- Read for gaps, collisions, and orphans. An empty column is an unfilled role; two primaries on one decision is a collision; a decision with no owner is an unowned piece of the whole.
- Name the owner of the whole. Fix who is accountable for the team's overall coherence, so the capability is not a set of roles with no one responsible for their sum.
Tuning parameters¶
- Role granularity — broad roles versus fine-grained skills. Fine granularity reveals precise coverage gaps but bloats the grid and dates quickly as work shifts.
- Coverage scheme — binary filled/unfilled versus a primary/backup depth marking. Depth exposes bus-factor risk — roles held by exactly one person — but demands more judgment per cell.
- Authority explicitness — whether decision rights are mapped as their own columns, separate from skills. Explicit authority catches collisions early but can surface uncomfortable political questions.
- Redundancy target — how much backup depth each critical role must carry. More depth is resilient to departures but costs headcount and can blur ownership.
When it helps, and when it misleads¶
Its strength is that it makes role coverage and decision authority inspectable, catching the unfilled critical role and the unowned decision before they bite in the middle of a project — precisely the failures that a headcount total and an org chart both conceal.
Its failure mode is that a cell marked "covered" asserts a person is assigned, not that they are capable of or available for the role. A matrix can look fully staffed over a team that cannot actually perform — the "named but not able" trap — and, because it charts formal roles, it misses the informal glue-work that often holds teams together. The classic misuse is filling every cell to look fully-resourced for a plan review, rather than to honestly test coverage. The guarding discipline is to pair the matrix with evidence of real capability and availability, treat a filled cell as a claim to verify, and separate having a name in a box from having the role genuinely covered.[n1]
How it implements the components¶
A Team Composition Matrix fills the archetype's human-role slots:
role_definition— it defines what each role must contribute and which roles the whole needs, so gaps and collisions become visible against a stated standard.assembly_owner— it names who holds each decision right and who is accountable for the team's whole-level coherence, so no critical decision and no overall capability is left unowned.
A composition matrix maps people, not parts: it does not maintain a component_catalog of versioned items, fix component_selection of materials, or run a compatibility_check on them — those belong to Bill of Materials and Configuration, its nearest twin, which registers parts and their valid combinations where this registers people and their authority. It also does not draw the interaction_map or interface_contract of how work flows between roles (Architecture Blueprint), nor define the intended_whole_function the roster is ultimately judged against (Research Synthesis Protocol composes that kind of whole for knowledge).
Related¶
- Instantiates: Compositional Assembly — it composes people into a team by mapping role coverage and decision authority against what the capability needs.
- Sibling mechanisms: Architecture Blueprint · Bill of Materials and Configuration · Research Synthesis Protocol · System Integration Workflow · Integration Test Plan · Curriculum Map · Policy Package Design
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Team Composition Matrix is defined in the frozen evidence as: Maps candidate people against the roles, skills, and decision rights a capability needs, exposing coverage gaps, authority collisions, and who owns the whole. Its operative deployed or enacted form is therefore Representation, Specification & Plan.
Nearest alternative: Assessment, Review & Assurance — Assessment, Review & Assurance can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Team composition matrix derives most directly from organizational management's coordination, workflow, and capability tradition; its defining operation is to maps candidate people against the roles, skills, and decision rights a capability needs, exposing coverage gaps, authority collisions, and who owns the whole.
Related originating lineages:
- Operations Research — Operations research's allocation, scheduling, queueing, and optimization tradition provides a formative adjacent lineage for the same team composition matrix operation.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: maps candidate people against the roles, skills, and decision rights a capability needs, exposing coverage gaps, authority collisions, and who owns the whole.
Review resolution: Both blind reviewers independently select organizational_management as the primary historical origin for the concrete operation—Maps candidate people against the roles, skills, and decision rights a capability needs, exposing coverage gaps, authority collisions, and who owns the whole. The queued differences concern alternate origin disagreement, origin mode disagreement, domain reach disagreement, encyclopedia synthesis disagreement, not the primary lineage. I retain every alternate that either reviewer explains, without a numeric cap, and choose origin_mode=cross_disciplinary_synthesis because the reviewers' combined evidence identifies material construction from multiple disciplines. domain_reach=universal records later portability rather than multiplying historical origins; confidence=high is the conservative shared evidentiary level, and encyclopedia_synthesis=true preserves either reviewer's affirmative synthesis finding.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] A RACI matrix (Responsible, Accountable, Consulted, Informed) is a standard responsibility-assignment chart mapping tasks or decisions to roles, with the rule that each item has exactly one Accountable owner. A team composition matrix generalizes the same discipline to whole-role and skill coverage — and inherits the same caution: a name in a cell records an assignment, not a demonstrated ability to deliver it. ↩