Define three jargon terms for the team wiki

Acronym fog slows every new hire and every cross-team thread. Three definitions today beat a style guide nobody reads.

This hack: ten minutes, three terms, glossary entries.

When to use it

• The same jargon confused someone this week.
• You have a glossary home.
• Definitions are stable enough.

When not to

• Terms are contested politically. Align owners first.
• You're defining client-confidential code names in a public wiki. Check permissions.
• One term needs a full RFC. Link out; don't fake brevity.

Do this (timer on)

1. 1. Pick three terms.
2. 2. Write plain-English definitions + non-examples.
3. 3. Publish. Link from onboarding doc.

Prompt (copy)

Write glossary entries for these three terms.

For each:
- Term
- Plain definition (1-2 sentences)
- In practice (1 example)
- Not to be confused with
- Owner

TERMS + ROUGH NOTES:
[paste]

After you send

If jargon keeps biting, documentation culture is thin. Operations Efficiency when onboarding still requires a decoder ring.

Start free assessment (Operations Efficiency) at https://faisalrizvi.com/ - See where we're wasting hours. 3 minutes. Score + prioritized roadmap. Shareable report. No login.

Book a free 30-min call only if you want a walkthrough after the roadmap.