17.1 — Words as Tools: Building a Working Vocabulary

There are two vocabularies inside your head.

Your recognition vocabulary — words you understand when you meet them. It is large. For most educated adults, it runs to tens of thousands of words. It grows steadily just by reading and listening.

Your production vocabulary — words that arrive when you need them, under pressure, mid-sentence, while looking somebody in the eye. This is considerably smaller.

The gap between them is why people say "I know the word, I just can't think of it." And it is why reading alone does not make you articulate. Reading builds recognition. Only use builds production.

When you read a precise, powerful word, your brain says "I know what that means." But knowing what it means does not put it in your mouth when it matters.

What happens when the gap shows up

When you lack the production vocabulary to describe reality exactly, you fall back on approximate words. The result is that other people misunderstand you, underestimate you, or ignore you.

Here is what that looks like in the moments that matter.

The job interview where the candidate shrinks their own achievement.

What they said: "I did stuff with databases and made them faster." What they meant: They identified structural bottlenecks and rewrote the logic to process information efficiently. What the interviewer heard: A junior employee who performed routine maintenance. What they needed to say: "I optimized query performance across three microservices." The breakdown: "Did stuff" is a placeholder phrase. The interviewer cannot see the complexity of the work, so they assume the work was simple.

The doctor visit where the patient goes unheard.

What they said: "My stomach feels weird." What they meant: A sharp, localized pain that arrives only after eating and radiates to the back. What the doctor heard: Generic indigestion. What they needed to say: "I have a sharp, stabbing pain under my ribs that only happens thirty minutes after meals." The breakdown: Medical diagnosis relies on differentiation. Without precise descriptive words, the doctor groups the symptom into the most common, least serious category.

The parent-teacher meeting where frustration replaces clarity.

What they said: "He's just not getting it, and the homework is bad." What they meant: The child understands the concepts when spoken to, but freezes when faced with a blank page, leading to hours of anxiety. What the teacher heard: An unsupportive parent complaining about the workload. What they needed to say: "He grasps the concepts verbally, but struggles with task initiation when staring at written assignments." The breakdown: "Not getting it" is too broad. The parent needs vocabulary that isolates the exact friction point so the teacher can intervene correctly.

The salary negotiation where vague language leaves money on the table.

What they said: "I've been working really hard and doing extra things." What they meant: They have assumed the responsibilities of a senior role that was vacated six months ago, saving the company the cost of a new hire. What the manager heard: Standard employee expectation of a raise for simply doing their job. What they needed to say: "I have absorbed the scope and responsibilities of the senior position, resulting in uninterrupted project delivery." The breakdown: "Working hard" is subjective and easily dismissed. "Absorbed the scope" is objective and demands compensation.

The relationship argument where placeholders replace actual emotions.

What they said: "You always do this. You're just being annoying." What they meant: The partner made a decision that affected both of them without consulting them, making them feel disregarded and invisible. What the partner heard: A generic, unprovoked attack on their character. What they needed to say: "When you made that choice without asking me, I felt marginalized and dismissed." The breakdown: "Annoying" is a reaction, not an emotion. It puts the other person on the defensive. Naming the exact feeling—marginalized—explains the pain without attacking the person.

The age and profession problem

Your vocabulary needs change as your environment changes. The words that worked perfectly at one stage will actively fail you at the next.

The 15-year-old student. They are moving from narrative writing to analytical writing. They are reading history and literature texts that expect them to understand nuance. If they try to write essays using their speaking vocabulary, they will write "the author says bad things about society." They need to build the academic vocabulary to write "the author critiques the underlying assumptions of the culture."

The 25-year-old entering the workforce. They have an academic vocabulary from university, but they lack professional vocabulary. They write long, theoretical emails that no one reads. They need to transition from "this thesis argues" to words that drive action: propose, align, execute, timeline, mitigate.

The 40-year-old new manager. They were promoted because they were great at doing the work. Now they have to direct others. The technical vocabulary that made them an expert is suddenly useless. They need the vocabulary of leadership: words that delegate, hold accountable, resolve conflict, and set vision. They have to move from saying "here is how you code this" to "we need to align on the strategic priorities."

The 60-year-old facing new technology paradigms. They have deep industry knowledge, but the vocabulary of the tools has shifted. They say "the computer file thing" instead of "the cloud repository." When they lack the modern vocabulary, younger colleagues wrongly assume they lack modern competence. Learning the precise names of new systems bridges the authority gap.

The translation professions

Some jobs require you to master multiple vocabularies and translate between them on the fly.

The Engineer. They spend all day talking to other engineers using highly specific technical jargon. Then they have to explain a project delay to the marketing team. If they say "the API rate limits are bottlenecking the asynchronous database calls," marketing hears noise. The engineer must translate: "We are hitting a hard limit on how fast we can request data from our provider. We have to slow down our system to match theirs."

The Teacher. They need three distinct registers every day. To the administration, they speak the language of metrics and pedagogy ("differentiation, formative assessment, curriculum alignment"). To the students, they speak the language of clear, engaging instruction. To the parents, they must translate the pedagogical metrics into plain, empathetic English ("he is making steady progress, but needs help organizing his thoughts before he writes").

The Entrepreneur. They have a brilliant product. When pitching to venture capitalists, they must use the vocabulary of scale and return ("unit economics, customer acquisition cost, churn rate"). When talking to their early employees, they must use the vocabulary of mission and resilience. If they mix these up—pitching the mission to the VC, or pitching the unit economics to the burned-out developer—they lose the room.

What actually moves a word across

To move a word from your recognition vocabulary to your production vocabulary, you have to follow the rules of memory (covered in Part 3).

Retrieval, not exposure (3.3). Seeing a word again does little. Hearing someone else use it does little. Producing it from memory, in a real sentence, does a great deal. You have to pull the word out of your own head.

Depth of processing. Reading a definition is nearly worthless. A word used in a sentence about your own actual life is retained. Your brain remembers things that connect to existing structures.

Spacing (3.2). Encountering the word again after a gap tells your brain the word is permanently useful, not just a passing novelty.

And a cue you will actually have. A word learned in the abstract has no retrieval route. A word learned attached to a situation — this is the word for the thing my manager does — comes back when that situation arrives. You do not need to remember the definition. You need to remember when to use it.

The method: Six steps to ownership

This method forces a word across the gap. It takes about two minutes per word.

1. Collect from reading, not from lists. Words encountered in context arrive with their register and their usual company attached. Word-a-day lists teach the definition and not the usage, which is why people who learn from them use words slightly wrongly. Keep a running note on your phone. Any word you read or hear that made you think, or that you would not have produced yourself, goes on the list.

2. Write it with its actual sentence. Copy the sentence where you found it. This preserves the grammar and the context.

3. Write what it means in your own words. The generation effect (3.3). Do not copy the dictionary's phrasing. Explain it as if you were talking to a friend.

4. Write when you would use it.This is the step that matters most and the one nobody does. Not the definition — the situation. Give your brain a trigger.

5. Write one sentence of your own. It must be about something real in your life.

6. Use it out loud within a week.This is the transfer step. A word used once in actual conversation is more likely to be available afterwards than one revised ten times on paper.

Full worked examples

Here is exactly what this looks like in your notes.

Example 1: Disingenuous

Found in: "The politician's response to the scandal was entirely disingenuous." My definition: Pretending to be innocent or ignorant when you actually know exactly what is going on. Fake naivety. When I would use it: When a colleague says "Oh, I didn't realize that was your project" after deliberately taking credit for it in a meeting. My sentence: It is disingenuous for the client to claim they didn't know about the deadline when I emailed them about it three times. Action: Used it on Tuesday when talking to Sarah about the client's delays.

Example 2: Conflate

Found in: "The author tends to conflate wealth with intelligence." My definition: Mixing up two different things and treating them as if they are the exact same thing. When I would use it: During an argument, when someone twists my words by combining two separate points I made into one terrible point. My sentence: We need to be careful not to conflate the team's low morale with laziness; they are exhausted, not lazy. Action: Used it in Thursday's project review when the manager blamed the software for a process failure.

Example 3: Mitigate

Found in: "We must take immediate steps to mitigate the damage to the brand." My definition: To make something bad less severe, harmful, or painful. Not fixing it completely, just softening the blow. When I would use it: When a project is going wrong and we can't stop it, but we can do things to limit how much money we lose. My sentence: To mitigate the risk of the server crashing during the launch, we are adding extra capacity for the first 24 hours. Action: Used it in an email on Monday regarding the new vendor contract.

The compound effect

Ten words a week sounds trivial. But let us run the math.

If you capture ten words a week and run them through the six steps, you will spend about twenty minutes a week. In a month, you have forty words at your command. In six months, you have two hundred and fifty.

Two hundred and fifty precise, powerful words, actively deployed in your daily speech, completely change how you are perceived.

You cross a threshold. You stop reaching for words and finding nothing. You start speaking in complete, clean sentences because you have the exact bricks needed to build them. People begin to describe you as articulate, clear, and sharp.

Precision beats size: The words that make you sound foolish

The goal is not a large vocabulary. It is the right word.

A person with two thousand precisely-used words is more articulate than one with ten thousand approximate ones, and the second is much more likely to be caught using a word slightly wrong — which costs more than the word gains.

When you use a big word incorrectly, you signal that you are trying to sound smart, and failing.

Mistake 1: Using "Irregardless"

The story: A manager in a tense meeting said, "Irregardless of the budget, we have to move forward." The room went silent. Someone corrected him. His authority evaporated for the rest of the meeting. The reality: "Irregardless" is a double negative (the 'ir' and the 'less' cancel each other out). It is not a standard word. The correction: Just say regardless.

Mistake 2: Swapping "Affect" and "Effect"

The story: An analyst sent a company-wide report stating, "The new policy will have a negative affect on sales." The executives noticed the error, and quietly questioned the analyst's attention to detail on the data itself. The reality: Affect is usually a verb (to influence). Effect is usually a noun (the result). The correction: "The policy will affect sales." or "The policy will have an effect on sales."

Mistake 3: Using "Utilize" instead of "Use"

The story: A junior consultant wrote, "We must utilize the new framework to synergize our efforts." The client laughed out loud while reading it. The reality: Utilize means to use something for a purpose other than its intended one (e.g., utilizing a book as a doorstop). In business, people use it because they think "use" sounds too simple. The correction: Always prefer the plain word. Use. The long word is not more professional; it is more effortful for the reader.

Mistake 4: "Literally" for emphasis

The story: Someone said, "I was literally dying of embarrassment." The reality: Literally means it actually happened in physical reality. Using it to mean "figuratively" or "very much" destroys the meaning of the word. The correction: If it didn't physically happen, do not use literally. Just say "I was dying of embarrassment" (the metaphor works on its own).

Three rules that follow:

Never use a word you could not define. If challenged, you should be able to explain it simply.

Prefer the plain word unless the precise one carries something extra. Help over facilitate. Start over commence.

And use the precise word when it is genuinely more precise. Disingenuous means something specific that dishonest does not. Reluctant means unwilling, reticent means silent. That is when the vocabulary earns its place.

Register mastery: The right word for the room

Words carry a setting, and using one in the wrong setting is more noticeable than not knowing it.

A word is not just a definition. It is a piece of clothing. You do not wear a tuxedo to the beach, and you do not use "pursuant" in a Slack message.

Formal Register: The language of legal contracts, academic papers, and official policy.

Notwithstanding, endeavour, pursuant, aforementioned, commence, thereby.When to use it: Almost never. In ordinary business writing, these words read as padding. They create distance.

Neutral Professional Register: The language of competent business and clear thinking.

However, therefore, consider, ensure, propose, resolve, clarify.When to use it: This is where most of your professional writing and speaking should sit. It is clear, polite, and efficient.

Conversational Register: The language of warmth, connection, and speed.

But, so, let's, I think, quite, look into, fix.When to use it: Perfectly good in an email to a colleague, a one-on-one meeting, or anything that needs human warmth (17.7).

The register mistake that most damages credibility is upward. Over-formal writing in a casual context reads as insecure.

Look at the same sentence in three registers:

Formal: "Pursuant to our previous conversation, I shall endeavour to ascertain the root cause." Neutral: "Following our conversation, I will investigate the root cause." Conversational: "Like we talked about, I'll look into what caused it."

The words worth having ready

Do not memorize impressive, obscure words. Memorize the high-leverage words. These are the words that let you say a precise thing you currently say in a paragraph.

Here is a starting list, categorized by where you need them.

Resolving Conflict & Misunderstandings

Conflate — to treat two different things as one.

Sentence: "Let's not conflate his lack of experience with a lack of effort." When: When someone is unfairly grouping two issues together to make a point.

Nuance — a small but real distinction or difference.

Sentence: "There is a nuance here we are missing: they didn't reject the deal, they rejected the timeline." When: When a situation is being treated in black-and-white terms, but the reality is grey.

Ambiguous — genuinely open to more than one interpretation.

Sentence: "The client's email is ambiguous; I cannot tell if they approved the budget or just the design." When: When instructions are unclear and you need to politely pause work until they are clarified.

Equivocate — to use vague language to hide the truth or avoid committing.

Sentence: "When I asked about the launch date, the manager started equivocating." When: When someone is dodging a direct question with slippery answers.

Analyzing Decisions & Projects

Trade-off — what you give up in order to get what you want.

Sentence: "The trade-off for launching a month early is that we will have bugs in the system." When: When people want everything to be perfect and you need to force them to choose priorities.

Contingent — depending on something else happening first.

Sentence: "The marketing spend is contingent on the product team delivering the feature by Friday." When: When you need to clearly link two events so that blame is placed correctly if things fail.

Marginal — the effect or cost of one additional unit.

Sentence: "The marginal cost of adding one more user is essentially zero." When: When discussing whether to scale something up, separating the fixed costs from the ongoing costs.

Precedent — an earlier event that sets the pattern or rule for the future.

Sentence: "If we give him a refund, we set a precedent that will cost us thousands next month." When: When a small decision today has dangerous long-term consequences.

Describing Problems & Realities

Untenable — a situation or argument that cannot be maintained or defended.

Sentence: "Working sixty hours a week is an untenable long-term strategy for this team." When: When something is broken and you need to announce that it absolutely must change.

Substantive — having a firm basis in reality; meaningful.

Sentence: "We need to make substantive changes to the code, not just fix the spelling errors on the website." When: When distinguishing real work from superficial, surface-level work.

Systemic — affecting the entire structure or system, not just one part.

Sentence: "This isn't just one bad employee; it is a systemic failure in our hiring process." When: When people are blaming individuals for problems caused by the environment or the rules.

Mitigate — to make less severe or harmful.

Sentence: "We can't prevent the storm, but we can mitigate the damage by backing up the servers." When: When you are doing damage control and need to lower expectations from "perfect fix" to "survival."

Giving Feedback & Direction

Actionable — able to be acted upon; providing a clear next step.

Sentence: "This feedback is interesting, but it isn't actionable. What exactly do you want me to change?" When: When people give vague criticism and you need specific instructions.

Tangential — diverging from the main point; barely connected.

Sentence: "That is a fascinating point, but it's tangential to the decision we have to make today." When: When a meeting is getting derailed and you need to politely drag it back to the agenda.

Explicit — stated clearly and in detail, leaving no room for confusion.

Sentence: "I need you to be explicit about exactly when you need this finished." When: When people are relying on hints or assumptions and you need hard facts.

Implicit — suggested though not directly expressed.

Sentence: "The implicit threat was that if we didn't agree to the terms, they would go to a competitor." When: When you need to name the elephant in the room that everyone feels but nobody is saying.

Each of these replaces a rambling sentence. They are precision tools.

What to do

Start the note today. Any word you had to think about, or read and thought "that's a great way to phrase that," goes in it.

Do ten a week, with the six steps. Do not skip step four (the situation). Give your brain the cue.

Use each one out loud within a week. Force the transfer from recognition to production.

Write fifteen minutes a day. On anything. A journal, an email draft, an essay. Writing forces production, and production builds the muscle.

Prefer plain unless the precise word earns its place. The aim is being understood exactly, not sounding educated, and the two frequently point in opposite directions.

Next: 17.2 is the bank — a comprehensive library of the exact words worth having, grouped by the specific conversations where they do the most work.