What goes into a reference taxonomy
A taxonomy answers one question: by which attributes will people search for a reference? The usual ones are industry, company size, region, product or module, and use case. Many teams add a few of their own, such as the system a customer migrated from, the buyer's role or a deployment type.
Some attributes are fixed lists (industry, size band, region). Others are flexible tags that can be added as needs appear. A good taxonomy keeps the fixed lists short and uses tags for everything else.
Why it matters
A reference is only useful if someone can find it at the moment a prospect asks. If categories are inconsistent or missing, sales goes back to asking colleagues, and the same well-known customers get every request. A clear taxonomy is what lets less obvious references surface.
An example
A team classifies each reference by industry, size band, region and product, then adds tags for use case. A rep with a mid-size logistics prospect filters on those values and finds Sample Logistics, tagged for the same use case the prospect described.
Common mistakes
- Designing categories around how marketing segments the market instead of how sales describes deals.
- Creating so many tags that nobody applies them consistently.
- Allowing free text, so one industry ends up under several names.
- Tagging the company but not the individual. Willingness and role belong to the person.
- Never retiring tags that no longer match the product.
A simple test is to ask a few salespeople how they would describe the reference they needed most recently, then check that every word they use maps to a field or a tag. In a reference library those fields and tags become the search filters, so the taxonomy is worth settling before records are imported.