Expertise Scope Matrix¶
Reference matrix — instantiates Domain-Specificity of Confidence
Maps each actor or team against domains as validated, adjacent, or out-of-domain, fixing where confidence is licensed before any specific claim is made.
An Expertise Scope Matrix is a standing grid — rows are people or teams, columns are domains — where every cell carries one verdict from a short vocabulary: validated, adjacent, or out-of-domain. Its defining move is that it is settled in advance, as a design-time policy, independent of any particular question on the table. It answers "where is this person's confidence licensed?" before a claim even exists, so that when a claim arrives the boundary is already drawn rather than improvised under pressure. It declares scope; it does not, by itself, measure whether the declaration is deserved — that separation is what keeps it a map rather than a scoreboard.
Example¶
A management-consulting firm builds a matrix of its partners against industry×function cells — "retail — supply chain," "healthcare — M&A," "energy — pricing." Each cell is filled from engagement history and peer review: a partner who has led eight retail supply-chain turnarounds gets validated there, adjacent on retail pricing, out-of-domain on healthcare regulation. A pharma client then invites that partner to opine on a hospital reimbursement redesign. Because her cell for "healthcare — regulatory workflow" reads out-of-domain, the matrix flags the mismatch before the proposal ships: staff the engagement with the health-policy group, or bring them in as co-leads. The grid did nothing case-by-case; it simply made the scope boundary legible at staffing time, which is exactly when the decision is cheap to change.
How it works¶
The distinguishing choices are structural, not procedural:
- Cut columns fine enough to break liquid domains. "Finance" is useless as a column; "small-cap industrials under stable rates" is a usable target. Granularity is what lets a matrix expose a weak sub-area a coarse label would hide.
- Fix a small band vocabulary. Three tiers (validated / adjacent / out) keeps cells comparable across the whole grid; more tiers add nuance at the cost of consistency.
- Define each band by warrant type, not feeling. Validated = repeated, feedback-tested success; adjacent = plausible but untested transfer; out = no warrant.
- Treat it as a policy artifact. It governs staffing and sign-off. It is deliberately not self-updating — revisions come from a separate review event, so the map and its own history stay legible.
Tuning parameters¶
- Column granularity — coarse vs. fine domain splits; finer cuts surface hidden weak specialties but multiply cells and maintenance.
- Band vocabulary size — two tiers vs. five; more tiers capture nuance but erode cross-cell consistency and invite disputes.
- Assignment authority — self-declared vs. peer- or committee-assigned; peer assignment resists inflation but costs review time.
- Adjacency permissiveness — whether "adjacent" is a gateway inviting a transfer test or a soft "stay out"; loosening it raises useful transfer and overreach together.
- Refresh trigger — event-driven (after each engagement) vs. calendar-driven; more frequent refresh fights staleness but churns the artifact.
When it helps, and when it misleads¶
Its strength is pre-emption: it moves the scope decision upstream to staffing and sign-off, where "who should answer this?" is easy to reroute, instead of leaving it to the moment a confident answer is already leaving someone's mouth. It makes a whole organization's competence boundaries visible at once.
Its characteristic failure is overrestriction: cells harden into credential walls that block legitimate transfer, so the matrix becomes a tool for protecting territory rather than calibrating warrant — a bureaucratic expression of the halo effect it was meant to check, where a title in one cell silently licenses authority in another.[n1] Its other failure is staleness: an unrefreshed cell keeps vouching for competence that has decayed or grown. The guarding discipline is to treat adjacent as an invitation to run a transfer test rather than a verdict, pair the grid with a live exception path, and route all revisions through a periodic review so cells never freeze.
How it implements the components¶
The Expertise Scope Matrix fills the scope-declaration side of the archetype — not the measurement or communication sides:
source_domain_map— the validated cells are the map of where each actor's confidence was earned, held as a standing grid rather than recalled ad hoc.target_domain_definition— the columns enumerate, at a chosen granularity, the candidate target domains any incoming claim can be sorted into.domain_confidence_band— each cell assigns a standing band (validated / adjacent / out) to an actor-domain pair.
The matrix declares scope but never checks whether a declaration is earned: it records no outcomes and computes no accuracy. The measured warrant that would justify or overturn a cell — warrant_inventory and feedback_update_loop — belongs to the Track Record by Domain Scorecard, its nearest twin. The matrix asserts where confidence is licensed; the scorecard measures whether the assertion holds.
Related¶
- Instantiates: Domain-Specificity of Confidence — the matrix is the standing scope map the rest of the pattern reads against.
- Consumes: Track Record by Domain Scorecard supplies the measured evidence that should justify each cell's band; Confidence Retrospective supplies the revisions that keep it current.
- Sibling mechanisms: Claim Confidence Labeling · Out-of-Domain Prompt · Track Record by Domain Scorecard · Transfer Assumption Review · Referral or Collaboration Protocol · Confidence Retrospective
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Expertise Scope Matrix operates as a non-executable information artifact that externalizes static or prospective structure because it maps each actor or team against domains as validated, adjacent, or out-of-domain, fixing where confidence is licensed before any specific claim is made.
Independent corroboration: The frozen evidence defines Expertise Scope Matrix as 'Maps each actor or team against domains as validated, adjacent, or out-of-domain, fixing where confidence is licensed before any specific claim is made', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Mapping competence boundaries across people and domains derives from organizational skills and competency management.
Related originating lineages:
- Education & Pedagogy — Credentialing and competence assessment materially shape the validated, adjacent, and out-of-domain distinctions.
- Statistics & Experimental Design — Measurement and validation practice materially supplies the distinction between validated, adjacent, and unsupported confidence.
Review resolution: Both reviewers agree that organizational_management is primary. I retain statistics_experimental_design, education_pedagogy only as formative origin lineages; cross_disciplinary_synthesis is appropriate because the final form materially combines the agreed primary with the retained formative lineages. Reach is multi_domain because the structure transfers across several fields but is not a near-universal human pattern, an applicability judgment kept separate from provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. No unresolved historical ambiguity remains after reconciling the secondary fields.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
Keep the matrix and the scorecard as two artifacts, not one. Their value comes partly from being allowed to disagree: a cell declared validated while the scorecard shows sinking accuracy is precisely the signal the retrospective exists to act on. Fusing declared scope with measured accuracy destroys that early-warning gap.
[n1] The halo effect is the cognitive bias in which a positive impression in one area (here, proven competence or status in one cell) inflates judgments in unrelated areas. A scope matrix guards against it by forcing competence to be recorded per-cell; misused, it can instead institutionalize the halo as a permanent credential. ↩