Expertise Finding¶

Given a topic, question, or task, expertise finding uses evidence associated with candidate people to rank those most plausibly able to help.

Version: v3 · 2026-09-19 · History
Domain-specific #: 1809
Domain group: Professional & Organizational Practice
Origin domain: Organizational & Management Science
Subdomains: Information Retrieval and Knowledge Management, Expertise Retrieval → Organizational & Management Science
Aliases: Expert finding, Expert search, Expertise location

Core Idea¶

Expertise finding is the information-retrieval task of ranking people who are plausibly expert in a topic, question, or task by using evidence associated with those people. A user supplies an expertise need; the system relates that need to candidate people through profiles, authored or mentioning documents, work records, social or organizational signals, or other traceable evidence; and it returns people rather than documents as the primary results. The supporting evidence matters because topical co-occurrence, reputation, and organizational visibility are imperfect proxies for competence.

How would you explain it like I'm…

Who Can Help Me?

Say you have a question about bugs and want to know who could help you. A clever helper looks for clues, like who drew bug pictures or wrote bug stories, and gives you a list of people with the best guess at the top. The clues are only hints, so the list is a good guess, not a promise.

The Expert Finder

Expertise Finding is when a computer system helps you find the right person to ask about a topic. You tell it what you need to know. It looks at evidence about people, such as what they wrote, what projects they worked on, and who they work with. Then it gives you a ranked list of people instead of a list of documents. The evidence matters because someone who is popular or mentions a topic a lot is not always truly skilled at it.

Ranking People by Evidence

Expertise Finding is a search task where the answers are people, ranked by how likely they are to be experts on your question. The system links your need to each candidate through evidence: profiles, documents they wrote or are named in, work records, and social or organizational signals. It is part of a larger area called expertise retrieval, whose other direction is expertise profiling: finding goes from a topic to people, while profiling goes from a person to their topics. It is different from ordinary people search, like looking up a coworker by name or filtering by a listed credential. The result is a judgment that someone looks expert for this particular question, not a permanent label that they are an expert.

Expertise Finding is the retrieval task of ranking candidate people by how plausibly expert they are for a given topic, question, or task. The system represents the user's expertise need and links it to candidates through traceable evidence: profiles, authored documents or documents that mention them, work records, and social or organizational signals. The primary output is a ranked list of people as potential sources of help. It sits within expertise retrieval alongside expertise profiling; both can draw on the same person-by-topic evidence matrix, but finding goes from topic to people while profiling goes from person to topics. Evidence matters because topical co-occurrence, reputation, and visibility in an organization are only imperfect proxies for actual competence. A name directory, a credential filter, or a social recommender for well-connected users is not Expertise Finding unless it compares a represented need against evidence of knowledge or skilled performance. Formally, it estimates a query-relative relation, that candidate c appears expert for need q given evidence E, rather than certifying a lasting status.

Scope of Application¶

The canonical habitat is enterprise search: an employee has a problem and needs colleagues who know a relevant technology, client, process, or scientific area. Organizational analyses treat expert-finding systems as a recurring problem class rather than one product, with architectures that acquire expertise evidence, model candidates, and expose the result for use. TREC's official Enterprise Track made this an evaluable retrieval task using organizational corpora. In 2005, systems received topical queries and ranked W3C people using the W3C document collection. In 2006, systems returned ranked candidates plus supporting documents so assessors and prospective users could inspect why a person had been recommended.

Clarity¶

Expertise finding clarifies that the relevant unit of retrieval is a person supported by evidence, not an evidence document treated as the final answer. A high-ranking technical report may reveal a candidate through authorship, contribution, or mention, but the transformation from document relevance to person relevance must be explicit. The strongest formal models differ precisely in where that transformation occurs: build a candidate language model from associated documents, or retrieve topic-relevant documents and aggregate their support toward candidates.

Manages Complexity¶

Organizations distribute knowledge across people and leave indirect traces across heterogeneous systems. No seeker can remember every colleague, interpret every title, read every work artifact, and follow every referral. Expertise finding compresses that many-to-many problem into an indexed relation among needs, evidence, and candidates. It makes “who might know?” tractable at a scale beyond personal memory and local networks.

Abstract Reasoning¶

Expertise-finding reasoning proceeds as a sequence of typed checks.

Specify the need. Determine whether the seeker wants explanatory knowledge, operational experience, formal authority, a collaborator, or an available responder. These are not interchangeable labels.

Define candidate eligibility. Decide whether candidates must be current employees, members of a community, researchers in a field, reachable contacts, or persons satisfying policy constraints. Candidate extraction is itself a failure surface when the universe is not supplied.

Knowledge Transfer¶

The full abstraction transfers exactly across enterprise expert search, researcher discovery, software-maintainer location, support escalation, community question routing, and evidence-based staffing. The people, evidence, and query vocabularies change, but every case still requires a need, a candidate set, person-linked evidence, an expertise inference, and a ranked person output.

Transfer is safest through the role structure rather than a vendor feature list. A code repository may replace publications with commits and issue resolutions; a hospital research directory may replace enterprise email with publications, trials, and grants; a support center may use incident records.

Relationships to Other Abstractions¶

Current abstraction Expertise Finding Domain-specific

Parents (1) — outgoing typed relations

Expertise Finding is a kind of Search and Retrieval Prime

Search and Retrieval is the minimal taxonomic parent: expertise finding is literally a query-driven retrieval process with indexed evidence, relevance matching, ranking, and returned objects.

Hierarchy paths (4) — routes to 3 parentless roots

Expertise Finding → is a kind of Search and Retrieval → presupposes Problem Space → is a kind of Representation → presupposes Abstraction

Show alternative paths (3)

Neighborhood in Abstraction Space¶

Expertise Finding sits in a sparse region of the domain-specific corpus (96^th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Unclustered & Miscellaneous (2769 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25