The problem a glossary solves
Every technical field arrives with its own vocabulary. In your first weeks on a new project, you may hear acronyms, nicknames for subsystems, and ordinary words used in a narrow sense, all without explanation. Colleagues stop noticing their own jargon, so nobody offers definitions, and asking about every term feels slow or embarrassing.
Good engineer onboarding often includes a glossary for exactly this reason, but you cannot count on one existing. A personal glossary is a short list of terms you have met, each with a definition in your own words. It is a private working tool, not a published reference. Its job is to catch confusion at the moment it appears, so that the same unfamiliar word does not puzzle you three separate times.
Why your own words matter
Copying a definition from a textbook is easy and often useless. Writing it in your own words forces you to check whether you understand. If you cannot restate a term simply, that is useful information: it tells you where to look further or whom to ask.
A glossary also records meaning in context. The same word can mean different things in different places. A team may use a term more loosely or more narrowly than a standard reference does. Noting how your project uses a word, alongside the general meaning, saves you from confusing the two.
What to put in an entry
Entries should be quick to write, otherwise you will stop writing them. A small, consistent format is enough:
- Term, exactly as people say or write it, including any abbreviation and what it stands for.
- Meaning, in one or two plain sentences.
- Where you met it, such as a meeting, a document or a particular part of the system.
- A related term or contrast, when it helps, such as a word that is often confused with it.
- Confidence, a simple mark for entries you are unsure about, so you remember to confirm them.
An example entry, written as an illustration only, might read: “Torque: a twisting effect that tends to turn an object about an axis. Met in a fastener specification. Not the same as force, though it is calculated from a force and a distance.” Keep it that short. If a topic needs a full explanation, write that as a separate note and keep the glossary entry as a pointer.
Choose a format you will actually use
The best format is the one you will open without effort. Common options include:
- A single text or Markdown file, searchable and easy to back up.
- A spreadsheet with a column for each field, which is handy for sorting and filtering.
- A section in a digital notebook, if you already keep notes there.
- A paper index card or small notebook, which some people find easier to review away from a screen.
Searchability is the main practical point. A glossary you can search in a few seconds will get used during meetings and while reading documents. If you already keep technical notebooks, a dedicated glossary section there keeps everything together. A pile of paper that takes minutes to leaf through may not be. Whatever you choose, keep everything in one place rather than scattering terms across several notes.
Capturing terms in the moment
Capture needs to be fast. Jot down the word as soon as you hear it, even without a definition, and fill in the meaning later. A running list at the end of each day or each meeting is enough. At the next break, look up the unclear ones, or ask a colleague a specific question: “When you say the interface board, do you mean the one in the test rig or the production unit?” Specific questions get quick, accurate answers, and people generally appreciate that a newcomer is trying to understand rather than guessing.
Terms from component documents are a good example: the habit of reading datasheets carefully goes hand in hand with noting down unfamiliar symbols and abbreviations. Be cautious when you look things up. Sources vary in quality, and definitions may differ between industries and countries. Where a precise meaning matters, such as in a standard, a safety requirement or a contract, rely on the authoritative document and the people responsible for it rather than on your own summary. Your glossary is an aid to understanding, not a replacement for the official text.
Organising and reviewing
For a small list, alphabetical order is enough. As it grows, you may add tags for subject areas, such as electrical, mechanical, software or process terms, or for the project they belong to. Do not spend long designing a system. A flat alphabetical list with good search is usually sufficient for hundreds of entries.
Review is where a glossary starts to teach you. Once a week, or at the end of a learning phase, read through the recent entries and test yourself by covering the definition. Remove duplicates, correct anything you got wrong earlier, and mark terms you now know well. Over time, you will notice that new entries slow down, which is a quiet sign that you are becoming familiar with the field.
Beyond the first weeks
A personal glossary can become more useful as you gain experience. When you later help a newcomer, your early entries show exactly which words confuse beginners, and you can share a cleaned-up version of the list with the team if the entries are accurate and nothing in them is confidential. Check with colleagues before sharing, since some terms or project names may be sensitive.
Treating vocabulary this way fits the broader idea of continuous learning, where small, regular habits accumulate. You can also carry the habit from one field to the next. When you move to a new domain, begin a fresh section and record how its vocabulary differs from the old one. Words that mean something precise in one discipline can mean something quite different in another, and a glossary makes those differences visible instead of leaving them as vague unease.
A short routine
- Write down unknown terms as you hear them.
- Fill in plain-language meanings within a day or two.
- Confirm uncertain entries with a colleague or an authoritative source.
- Review recent entries weekly and tidy as needed.
Maintained lightly, this takes a few minutes a day, and it often pays back quickly in confidence during meetings and while reading unfamiliar documents.