The Jargon Blind Spot: Why Your Website Makes Sense to Everyone Except Newcomers
Photo: The White House from Washington, DC, Public domain, via Wikimedia Commons
Every office has a first-day moment. You are handed a mug, a laptop and a login that works on the third attempt. Someone says, ‘We’ll need the QBR notes before the DPS review, then ping the MSA to Legal.’ You nod. You understand none of it. By Friday, you will. That is the problem.
Your website has the same effect on people who have never worked with you. The team knows what ‘Project Atlas’ means, why the ‘Core’ package is different from the ‘Core Plus’ package, and what happens after someone clicks ‘Enquire’. A new visitor does not. They have no induction, no intranet and no colleague to lean over and ask.
That is why the most expensive sentence in UK web copy is not a badly written headline. It is ‘everyone here knows that.’
Why insiders cannot see the jargon
Familiarity is a poor editor. If you have written about your services for years, the shorthand stops looking like shorthand. It becomes the thing itself. You see ‘Integrated Compliance Hub’ and think of the product. A newcomer sees four words that could mean anything.
This is not about dumbing down. It is about giving people a fair start. A smart outsider should be able to land on your site and work out three things without help: what you do, who it is for, and what they should do next. If they need a staff induction to answer those questions, the copy is carrying too much internal context.
Run the 20-minute induction test
You do not need a research budget or a six-week discovery phase. You need one person who is not soaked in your world and 20 minutes of honesty.
Pick the right person. A genuine new starter is ideal. So is a colleague from another department, a friendly client, or a sharp friend who works in a different industry. Avoid anyone who already knows your product names. Avoid anyone who will be polite to spare your feelings.
Set the timer and give them three pages: your homepage, one main service or product page, and your contact or pricing page. Ask them to talk out loud as they read. Not in a performative way, just narrate what they think you do and where they would click next.
Then say nothing. This is the hard part. Do not explain. Do not say, ‘Ah, but that bit means...’ The moment you rescue the page, the test is over.
Ask four questions at the end:
- What does this company do?
- Who is it for?
- What makes it different?
- What would you do next if you wanted to buy?
Write down every pause, every wrong guess and every question they ask. Those are your repair jobs.
What to fix first
Not everything needs a rewrite. The induction test usually exposes a short list of repeat offenders. Start here.
1. Acronyms and product names on first use
If a term only makes sense to your team, expand it or cut it. ‘Our CRM migration service’ is clearer than ‘Our CMR platform’ if no one knows what CMR stands for. If your product genuinely has a name, introduce it in plain English: ‘Atlas is our onboarding tool for new starters.’ Do not make the reader earn the explanation.
2. The first sentence of the homepage
Newcomers need orientation before persuasion. A headline that says ‘Work smarter’ could belong to 400 companies. A headline that says ‘HR software for UK care homes’ gives them a place to stand. You can be clever on line two. Be clear on line one.
3. Calls to action that assume knowledge
‘Book a discovery call’ is fine if people know what a discovery call is. ‘Talk to us about your payroll migration’ is better. Tell them what happens next, how long it takes and whether it costs anything. The fewer invisible steps, the more people will take the visible one.
4. Navigation labels written for the org chart
‘Solutions’, ‘Capabilities’ and ‘Ecosystem’ may make sense in a boardroom. They rarely help a first-time visitor. If your menu reflects how your company is structured rather than how customers search, simplify it. People are not trying to understand your departments. They are trying to solve a problem.
5. Case studies that assume the reader knows the client
‘We helped a leading FTSE 250 business transform its operating model’ says very little. Name the sector, the problem and the result. If you cannot name the client, describe the situation in concrete terms. Assumed context is not mystique. It is friction.
The cost of ‘everyone here knows that’
That phrase hides in sign-off meetings, content reviews and sales decks. It sounds efficient. It is actually a bill paid by someone else.
A customer pays it in confusion. A salesperson pays it by repeating the same explanation on every call. A support team pays it by answering questions the website should have answered. Your SEO pays it when search engines cannot work out what the page is about. And your brand pays it when a promising lead decides you are probably lovely, but not quite worth the effort of decoding.
None of this requires a radical rebrand. It requires a habit: read your site like it is someone’s first day, not your hundredth.
Make the test a routine
Run the induction test once a quarter, or whenever you launch a new service, rename a product or add a page to the main navigation. Keep a short glossary of internal terms and decide which ones deserve a public explanation. Add ‘Would a new starter understand this?’ to your pre-publish checklist. It sits nicely beside ‘Is the link working?’ and ‘Have we spelled the client’s name correctly?’
A website should not require an induction. It should give one. If a newcomer can land on your homepage, understand what you do and take the next step without a colleague whispering in their ear, you have written copy that works harder than most.
That is sharper words for a sharper brand. And it starts with admitting that ‘everyone here knows that’ is not a strategy. It is a blind spot.