Originally written in French. Translated by AI — the meaning has been preserved, not the prose.
A glossary isn't only there to define words.
In a knowledge system, it is there to pin down the vocabulary that lets people think together.
That matters most on subjects where the same terms travel across several functions: product, marketing, sales, support, leadership, design, engineering. Everyone can use the same words without giving them exactly the same meaning.
A glossary stops that from passing as obvious.
A glossary clarifies the words that carry decisions
Some words look simple right up to the moment the organisation has to decide.
Take customer signal.
For Sales, a signal might be an objection blocking a deal. For Support, it might be a recurring friction. For Product, it's raw input to interpret before it becomes work. For Product Marketing, it's a clue about perception or messaging.
If the term isn't pinned down, everyone believes they are talking about the same thing, but the decisions head off in different directions.
So a glossary entry is there to say:
- what the term means in context;
- what it does not mean;
- how it is used;
- which terms it can be confused with;
- which notes or decisions it sheds light on.
What a glossary entry is not
A glossary entry isn't a mini-article.
It doesn't have to say everything about a concept. It has to make a term usable.
Nor is it an atomic note in disguise. An atomic note carries an idea, often as a claim:
A customer request should stay a signal before it becomes work
A glossary entry pins the term down instead:
# Customer signal
Information from a customer or a market pointing to a need, a friction, an objection, a constraint or an opportunity, without amounting straight away to a decision or a ticket.
The first note thinks. The second defines.
The two go together.
What does a good entry look like?
A good glossary entry answers a few simple questions.
Short definition. What does the term mean, in one or two sentences?
Detailed definition. What nuances do you need to know to use it correctly?
Usage within the domain. Which deliverables, decisions or discussions does this term show up in?
Not to be confused with. Which nearby words create ambiguity?
Contextualised links. Which atomic or thematic notes use this term, and why?
An entry for product positioning, for instance, can make clear that positioning is more than a slogan or a marketing line. It gives the customer the right context to understand the value of the product: category, alternatives, target, differentiation and reason to buy now.
That clarification has very concrete effects. It keeps positioning, messaging, value proposition, tagline and campaign from being mistaken for one another.
Why the glossary is strategic
The glossary becomes important the moment a note system serves several people or several purposes.
In a marketing context, it can pin down:
- the customer's words;
- the internal words;
- the market categories;
- the perceived alternatives;
- the recurring objections;
- the terms to avoid;
- the phrasings that resonate.
In a product context, it can pin down:
- the signals;
- the stakes;
- the decisions;
- the trade-offs;
- the constraints;
- the segments;
- the situations of use.
The work can look modest, but it cuts an enormous cost: the cost of conversations where everyone uses the same word to defend a different idea.
The glossary protects the network of notes
A network of notes depends on the quality of its links.
But the links turn fragile if the words holding them up stay ambiguous. A note on product context, a note on product memory and a note on customer knowledge management can cross paths without understanding one another if their terms aren't pinned down.
The glossary then works as light infrastructure.
It doesn't replace atomic notes, it gives them a shared vocabulary. It doesn't replace thematic notes, it makes their syntheses easier to read. It doesn't replace sources, it helps translate their concepts into the language of the project.
The right definition
A glossary entry is a note that pins down a term from the domain to make it usable in decisions, links and deliverables.
It should be short, clear, sourced where possible, connected to the notes that use it, and alert to confusions.
A good glossary isn't a collection of textbook definitions.
It's a tool for collective precision.