Build a new starter's glossary from the jargon your team really uses

In their first week a new starter will hear "the SLA", "a P1", "the Tuesday huddle", "can you check Sam's tracker" and "that's a Sheffield thing", and nod at all of them. Nobody wants to be the one who asks what the third one means.

A glossary helps. Nobody writes one because it's nobody's job and it's tedious. But the raw material already exists in your documents and chats.

Gather a few real things: a team update, a process document, a long chat thread. Take out anything confidential, then:

Below is text from our team's documents and messages. Find every
acronym, abbreviation, nickname, system name and bit of shorthand that a
new starter wouldn't know.
Give me a table: Term | What it seems to mean | Where it appeared |
How sure you are.
Rules:
- Only give a meaning if the text itself explains it. Otherwise write
  "NOT EXPLAINED: ask [team]", and don't guess.
- Order by how often it appears, most first.
- Flag terms that seem to mean different things in different places.
- Leave out ordinary words and anything everyone would know.

Text: [PASTE]

Read the "NOT EXPLAINED" list closely. It's the terms nobody has ever defined, and there's often one that two people in the team explain differently.

Fill in the blanks by asking the team, and send the result to the next person who starts. Keep it as a living page with a named owner and a review date (documentation people will read covers how).

Let new starters add to it in their first fortnight, while they can still hear the jargon.