Word nuance & register (formal vs informal)¶
At a glance
Priority: P0 · Complexity: ⅘ · Est. time: 2 h · Phase: 1 · Prereqs: business & tech-leadership vocabulary You're done when: for any of 30 common near-synonym sets you can pick the right word for the audience and stakes, explain the difference in one sentence, and rewrite a paragraph up and down two registers.
Why it matters¶
Two words can share a dictionary definition and still be wrong in the same sentence. Ask, request, demand, require differ in power; problem, issue, challenge, risk differ in blame; cheap and inexpensive differ in judgement. At B2+ your vocabulary is wide; the gap is connotation (emotional colour), register (formal to casual), collocation and regional variety. A Staff engineer must switch registers within a day: a Slack thread with the team, an incident bridge, a board summary, a customer apology, an interview. Misjudged register is the most common reason "correct" English sounds off: too stiff to peers, too casual to executives, too blunt to customers.
Core concepts¶
Five dimensions of word choice¶
| Dimension | Question | Example |
|---|---|---|
| Denotation | What does it literally mean? | thin/slim/skinny all mean "not fat". |
| Connotation | What attitude does it carry? | slim (positive), skinny (neutral-negative), scrawny (negative). Work: frugal (+) vs stingy (-). |
| Register | How formal is it? | begin (neutral), commence (formal), kick off (informal). |
| Collocation | What does it naturally combine with? | heavy traffic, strong coffee; make a decision, not do a decision. |
| Variety and context | US/UK, industry, region? | fortnight (UK), quarter (US finance), tender (UK) / bid (US). |
The register scale (and where work sits)¶
| Register | Where | Features | Example (say "we're late") |
|---|---|---|---|
| Frozen/legal | contracts, policies | archaic forms, shall, hereinafter | "The Supplier shall deliver by the Due Date." |
| Formal | board papers, RFP responses, reports | Latinate verbs, passive, no contractions, hedged | "The delivery date will not be met." |
| Neutral/professional | most emails, docs, standard meetings | plain words, contractions in speech, active | "We're going to miss the date." |
| Informal-professional | Slack, team chats, standups | phrasal verbs, idioms, shortcuts | "We're going to be late; the vendor slipped." |
| Casual/colloquial | friends, banter | slang, ellipsis | "We're toast." |
| Slang/taboo | never at work |
Rule of thumb: write one notch more formal than you speak, and match the recipient's register; when in doubt, choose neutral.
Latinate vs Germanic vocabulary¶
English has two layers: short Germanic words (ask, get, show, start, end, need, buy) and longer Latinate/French words (inquire, obtain, demonstrate, commence, terminate, require, purchase). Latinate words sound more formal; Germanic words more direct.
| Germanic/plain (default) | Latinate/formal (use when required) |
|---|---|
| ask | inquire, request |
| start / begin | commence, initiate |
| end | terminate, conclude |
| get | obtain, acquire, receive |
| show | demonstrate, illustrate |
| help | assist, facilitate |
| use | utilise (often unnecessary) |
| need | require |
| buy | purchase |
| tell | inform, notify |
| try | attempt |
| enough | sufficient |
| about | approximately, regarding |
| think about | consider |
| find out | ascertain, determine |
| set up | establish |
| make sure | ensure |
| go up | increase, rise |
| put off | postpone, defer |
| check | verify, validate |
| fix | resolve, remediate, rectify |
| use up | consume, deplete |
Guideline: plain words for readers scanning quickly and non-native readers; formal words when the genre demands it (legal, regulatory, board). Never stack Latinate words to sound senior: "utilise the methodology in order to facilitate the commencement" is worse than "use the method to start".
Phrasal verbs vs single-word equivalents (see phrasal verbs)¶
Phrasal verbs are informal-neutral and dominant in speech; single-word equivalents are more formal: bring up / raise, find out / discover, look into / investigate, call off / cancel, put off / postpone, carry out / perform, set up / establish, go over / review, sign off / approve. In written formal documents prefer single verbs; in meetings prefer phrasal verbs.
Near-synonym sets at work (nuance table)¶
| Set | Differences | Workplace guidance |
|---|---|---|
| affect / impact / influence / effect | affect (v): change; impact (v/n): strong effect (as verb, still frowned by some editors: "impact the timeline" → "affect"); influence: shape indirectly; effect (n): result | "The outage affected 3,000 users." "The effect on revenue is small." |
| ensure / assure / insure | ensure: make certain; assure: tell someone confidently; insure: financial cover | "I assure you we will ensure it happens." |
| problem / issue / challenge / concern / risk / obstacle | problem (direct, can imply blame), issue (neutral, common in US business), challenge (positive framing), concern (worry, not yet a fact), risk (possible future harm), obstacle (blocks path) | To a customer: "issue"; to an exec: "risk"; to the team about a hard task: "challenge". Don't relabel a fact as a "challenge" if it is an outage. |
| ask / request / demand / require / insist | increasing force | Peers: ask, could you; formal: request; policy: require; demand is aggressive. |
| suggest / recommend / propose / advise | suggest (light), recommend (expert endorsement, accountable), propose (formal offer), advise (expert guidance) | Use recommend when you own the outcome. |
| agree / accept / concur / approve / endorse | concur formal; approve = authority; endorse = public support | |
| explain / clarify / justify / rationalise | clarify = make clear; justify = give reasons/defend; rationalise = invent plausible excuses (negative) | Not "rationalise the decision" unless you mean excuses. |
| change / modify / alter / amend / revise / update / adjust | amend = formal correction of a document; revise = rework; update = bring up to date; adjust = small tuning | "Amend the contract", "update the runbook", "adjust the threshold". |
| fix / resolve / mitigate / workaround / patch / hotfix | resolve final; mitigate reduces impact; workaround avoids problem without fixing cause | In incidents be exact: "mitigated" ≠ "resolved". |
| delay / postpone / defer / reschedule / slip | postpone = to later, set date; defer = decide later; slip = unplanned delay; reschedule = new time | "The date slipped" (unplanned); "we deferred the migration" (deliberate). |
| cheap / inexpensive / low-cost / affordable / economical | cheap can imply low quality; inexpensive neutral; low-cost business; economical efficient | "A low-cost option" not "cheap option" in proposals. |
| big / large / significant / substantial / considerable / major | size/importance; considerable/substantial formal | "A substantial reduction". |
| many / numerous / a large number of / plenty of / a ton of | formality drops | |
| old / legacy / mature / dated / outdated / obsolete | legacy (still running, often critical), outdated (negative), mature (positive: stable) | "Legacy system" is neutral/negative; "mature platform" positive. |
| easy / simple / straightforward / trivial / basic | simple (few parts); easy (little effort); trivial can insult | Avoid "it's trivial" to a peer. |
| hard / difficult / complex / complicated / challenging | complex = many interacting parts (neutral-technical); complicated = hard to understand (negative) | "The system is complex" (fact). |
| mistake / error / fault / bug / defect / failure | mistake (human), error (formal/technical), fault (blame or hardware), bug (software defect), failure (event) | "Human error" → "process gap". |
| blame / accountable / at fault / responsible | Blameless culture uses contributing factors. | |
| manage / lead / run / own / oversee / supervise | own = accountable end-to-end; oversee = supervise senior; run informal | "I own the platform" signals accountability. |
| team / group / squad / department / function | Use org vocabulary. | |
| boss / manager / lead / supervisor / executive | boss informal | |
| meeting / call / sync / catch-up / stand-up / session / workshop / review | different formats | "Sync" = alignment, informal. |
| sorry / apologise / regret / unfortunately | sorry casual/warm; apologise formal; regret formal (also we regret to inform); unfortunately softens | Customer: "We apologise for the disruption." |
| thanks / thank you / much appreciated / grateful / many thanks | ||
| but / however / although / yet | see clauses & cohesion |
Connotation traps¶
- Positive/negative pairs: confident/arrogant, frugal/stingy, assertive/aggressive, curious/nosy, detail-oriented/picky, persistent/stubborn, flexible/indecisive, direct/blunt, passionate/emotional. In reviews and feedback, choose a word describing behaviour and impact rather than character.
- "Aggressive" timeline, "ambitious" plan: ambitious is polite for "probably unrealistic"; aggressive often warns; tight = little slack; stretch = beyond capacity.
- "Interesting" can be a polite negative in British English ("That's an interesting idea" = I doubt it). Brave in UK = risky ("Brave decision, Minister").
- "Quite": UK = moderately ("quite good" = fairly), US = very ("quite good" = very).
- "Fine/OK/not bad/could be worse" vary in enthusiasm across cultures.
- "With respect," signals disagreement in formal UK settings.
- "Actually", "honestly", "frankly" imply that the previous statements were less than honest, or introduce blunt speech.
- "Obviously", "clearly", "simply", "just", "of course" can be condescending when the reader did not know.
- "I need you to..." vs "Could you...?" distinct power dynamics.
- "Whatever", "fine." can signal irritation.
- Gendered/loaded terms: guys (informal, some find non-inclusive; folks, team, everyone), chairman (→ chair), manpower (→ workforce, capacity), master/slave (→ primary/replica), whitelist/blacklist (→ allowlist/denylist), sanity check (→ quick check), grandfathered (→ legacy exemption). Follow your organisation's guidance.
US vs UK vocabulary and spelling¶
| US | UK | Notes |
|---|---|---|
| vacation | holiday, leave | holiday in UK means time off |
| resume (CV) | CV | |
| apartment | flat | |
| bid | tender | |
| fall | autumn | |
| stockholder | shareholder | |
| cell phone | mobile | |
| truck | lorry | logistics! |
| trunk | boot | |
| period | full stop | |
| "I'll table this" (US: postpone) | "table this" (UK: put on agenda) | Opposite meanings; avoid in cross-Atlantic meetings, use defer or bring to the agenda. |
| color / center / license / analyze / program | colour / centre / licence(n) / analyse / programme | Choose one variety per document. |
Switching register: sample ladder¶
Same message, five levels:
| Level | Message |
|---|---|
| Casual | "Heads up: prod's borked, we're on it." |
| Informal-professional | "Heads-up: we've got an issue in prod. We're looking into it and will update in 15." |
| Neutral | "We're currently investigating an issue in production. I'll update you in 15 minutes." |
| Formal | "We are currently investigating an incident affecting the production environment. The next update will be provided at 10:30 UTC." |
| Legal/regulatory | "The Company became aware of a service disruption at 09:12 UTC and is investigating in accordance with its incident response policy." |
Choose the level from: audience seniority, relationship, medium, stakes, cultural context, whether the message may be forwarded or archived. Emails can be forwarded to people you did not intend; use neutral for anything that may travel.
Vocabulary tools: how to check nuance¶
- Learner dictionary with usage labels (informal, formal, disapproving).
- Corpus check: search the phrase in COCA/GloWbE for frequency in academic vs spoken vs blog vs news; if it appears only in fiction, don't use it at work.
- Collocation dictionary for what it goes with.
- YouGlish to hear real usage.
- Ask a trusted native or bilingual colleague: "does this sound natural at work?" (ask them about tone, not just correctness).
Resources¶
| Resource | Type | Why this one | Level | Cost |
|---|---|---|---|---|
| Oxford Learner's Dictionaries | dictionary | Usage labels (formal/informal/disapproving) and "Word Origin"/synonyms notes. | all | free |
| Merriam-Webster | dictionary | "Synonym Discussion" sections explain nuance between near-synonyms exactly for this purpose. | intermediate-advanced | free |
| Macmillan Dictionary | dictionary | Style labels and thesaurus-style notes. | intermediate | free |
English-Corpora.org (COCA)  |
tool | Compare frequency across spoken, magazine, academic, fiction genres to judge register. | advanced | freemium |
| Ozdic | dictionary | Collocation lists distinguish near-synonyms by what they pair with. | intermediate-advanced | free |
| Michael Swan, Practical English Usage | book | Entries on formal/informal, US/UK differences. | advanced | paid |
| Bryan Garner, Garner's Modern English Usage | book | The definitive guide to disputed usage, register and connotation. | advanced | paid |
| Plain Language guidelines | guide | Word-choice guidance: "use simple words" with before/after lists of Latinate to plain. | intermediate | free |
| Google developer documentation style guide | style guide | Word list showing recommended and discouraged terms (inclusive language, jargon). | intermediate | free |
| BBC Learning English | site | Episodes on formal/informal language and workplace phrases. | intermediate | free |
Hands-on lab (60 min)¶
- Register ladder. Pick a real message (an escalation, a delay notice). Write it at five levels (casual to legal). Underline what changed each time (words, contractions, sentence length, hedges, passive).
- Near-synonym cards. Choose 10 sets from the table; for each write two sentences where one option is right and the other wrong or odd, and explain.
- Connotation audit. Review your last five feedback messages/reviews. Underline character-word adjectives (lazy, careless, aggressive) and replace with behaviour/impact statements.
- Corpus check. Look up "utilize" vs "use" and "commence" vs "start" in COCA by genre. Note frequency in spoken versus academic.
- Up/down conversion. Take a formal paragraph from a policy and write a version for a Slack announcement; then take your Slack message and produce a board-paper version.
Questions¶
L1 - Recall¶
Q1. Define register and name three factors that determine it.
Answer
Register is the level of formality and style appropriate to a situation. Determinants: audience/relationship, medium (spoken, chat, formal document), purpose/stakes, plus cultural expectations and whether the message may be forwarded.
Q2. Which is more formal: start, begin, commence, kick off? Order them from least to most formal.
Answer
kick off (informal) → start → begin → commence (formal). Start and begin are neutral; in most workplace writing use start or begin.
Q3. Distinguish affect and effect, and assure, ensure, insure.
Answer
Affect (verb) = influence; effect (noun) = result (verb effect = bring about, formal). Assure = tell someone with confidence to remove doubt; ensure = make certain; insure = provide financial insurance.
Q4. What does \"I'll table this\" mean in US and UK English?
Answer
US: postpone/set aside. UK: bring onto the table for discussion. In cross-Atlantic meetings avoid it; say "let's defer this" or "let's put this on the agenda".
L2 - Apply¶
Q5. Choose the better word: (a) \"We need to ___ (postpone / slip) the migration until we have a rollback plan.\" (b) \"The vendor's delivery ___ (postponed / slipped) again.\" © \"I'd like to ___ (recommend / suggest) we pick option B; I'll own the outcome.\"
Answer
(a) postpone (deliberate); (b) slipped (unplanned); © recommend (expert endorsement with accountability).
Q6. Rewrite for an executive audience: \"The system's borked because a dev screwed up the config, so it's a bit of a mess.\"
Answer
"The system is unavailable because of a configuration error. We are restoring service and will report the cause and prevention plan by Friday." (Neutral-formal; removes blame and slang; adds next step.)
Q7. Rewrite to a plain register: \"We shall endeavour to commence the requisite remediation activities prior to the aforementioned date.\"
Answer
"We will start the fixes before that date." (Plain, shorter, and the meaning is preserved.)
Q8. Replace character judgements with behaviour-impact language: \"You're careless with reviews and lazy about tests.\"
Answer
"In the last three PRs, I found bugs that tests would have caught, and reviews were approved within minutes. That increases the risk of incidents. Can we talk about how to build time for testing into your plan?" Behaviour, impact, and a forward-looking question; no labels.
L3 - Judge and choose¶
Q9. \"Problem\", \"issue\", \"challenge\", \"risk\": choose for (a) a production outage in an update to customers; (b) a possible future vendor failure in a board paper; © a hard staffing situation in a 1:1 with your team.
Answer
(a) Issue or incident (neutral, factual; avoid euphemism such as "challenge"). (b) Risk (future, probability and impact framing). © Challenge (constructive framing) but say what it is concretely; "problem" is fine if the team is comfortable with directness. Wrong label creates mistrust: calling an outage a "challenge" sounds evasive; calling a risk a "problem" alarms.
Q10. Is \"guys\" acceptable when addressing a mixed team?
Answer
Common in US informal speech and often perceived as neutral, but many people find it excluding in mixed or global teams. Safer: everyone, team, folks, all. In an important message (leadership, external), avoid it. Adapt if your organisation's norms say otherwise.
Q11. \"That's an interesting idea\" from a British colleague. How do you interpret and respond?
Answer
It may be genuine interest or a polite signal of doubt; check tone and follow-up. Respond by asking: "What concerns come to mind?" or "What would you need to see to be convinced?" This surfaces real objections without confrontation.
Q12. Is utilise ever better than use?
Answer
Rarely: utilise suggests using something for a purpose it was not primarily designed for, or making full use of it ("we utilised idle capacity"). In most cases use is shorter and clearer; utilise signals stiff writing. Check your habits: if you use it in every sentence, replace it.
L4 - Real-world decisions¶
Q13. You must send a delay notice to a customer contact who is very senior and in a formal culture, and a Slack message to your team, about the same delay. Draft both first lines.
Answer
Customer: "I regret to inform you that delivery of the integration will be delayed by two weeks, to 14 April. We apologise for the inconvenience and would like to present a revised plan." Team: "Heads up: we're slipping the integration by two weeks because the vendor API isn't ready. I'll share what that changes for us in stand-up." Different register, same facts and ownership.
Q14. A colleague from another culture keeps saying \"I demand a decision by Friday\" in emails, and peers are offended. How do you address it?
Answer
Explain privately that demand signals a power position and aggression in English; the same urgency can be expressed with I need a decision by Friday to keep the release on track or Could we agree on a decision by Friday? Otherwise the date slips. Give the reason for the deadline: reasons sound collaborative, not authoritarian.
Q15. How would you set a register policy for incident communications across engineering, support and executives?
Answer
Define three audiences and templates: internal technical (plain, precise, jargon allowed, informal tone acceptable), customer-facing (neutral-formal, apology, no jargon, no blame), executive (neutral, business-impact first, options and asks, numbers). Ban humour and slang in all incident writing, avoid idioms with regional meanings (table this, boil the ocean), state times in UTC, and make the incident commander responsible for the final review of external messages.
Real-world use cases¶
- Incident comms across three registers.
- Feedback and performance reviews (behavioural vs character language).
- Vendor and contract emails (formal, precise, hedged).
- Interviews (neutral-professional; avoid slang and over-formal words).
- Slack norms in a global team (inclusive terms, idiom light).
Pitfalls & anti-patterns¶
- Choosing the more formal word for prestige, resulting in stiff prose.
- Switching register mid-message (formal opening, slang close).
- Copying phrases from templates without checking connotation (do the needful, kindly revert).
- Assuming US and UK words are interchangeable (table, quite, homely, pants).
- Using words such as simply, just, obviously that hurt the reader.
- Softening so much that the message disappears (see hedging).
- Ignoring inclusive-language conventions of your organisation.
Checklist¶
- I can explain denotation, connotation, register and collocation with examples.
- I can rewrite a message at five register levels.
- I know the nuance differences for at least 15 of the near-synonym sets.
- I checked at least five doubtful words in a corpus or dictionary usage note.
- I answered all L3 questions out loud in under 3 minutes each.