Safety, not glossary
Your ticket still explains a word they heard on the radio
Rewrite live macros for the safety question, and keep a person on every claim that leaves the shop.
The definition is no longer the job. Your customer heard the word on a television they did not choose. They heard it from a radio in a car they did not drive. When they ring the desk, they are not asking you to introduce the category. They are asking whether your version is safe, and whether the answer you send them is true.
Your opener is still a lesson
Open the first paragraph of the macro your people paste when someone asks about the new tools. If it starts by explaining what the category is, you are teaching a class the radio already taught. That is not a small delay on the call. It is the wrong objection. The person on the line already has a picture. They want to know if a draft will invent a figure, if a machine will speak in your name, if a line in an email can be walked back next week.
Patrick McKenzie (@patio11), who has spent a career on billing, support mail, and the gap between what you ship and what a parent on a sofa will actually say, put it plainly.
@patio11It's been interesting the last few weeks hearing the parents' TV or Lyft drivers' radios saying things that in 2015 would have 100% pegged you as a LessWrong user.
Patrick McKenzie (@patio11)
If that talk is on daytime radio, it is already in your queue. People who write in this week arrived with a story. Meet the story with a sentence a closer can stand behind. Do not meet it with a glossary. Do not correct the version they heard in the car. You will lose the first minute, and you will still have to answer whether it is safe.
The objection that replaced the lesson
A shop this size does not get a new script from outside. You already have three places the old lesson still lives. Each one is a live surface, not a style guide sitting in a folder.
- The ticket macro the desk pastes when the thread mentions the new tools.
- The FAQ page a customer can find without waiting for you.
- The first thirty seconds of a sales, renewal, or "how do you use this" call.
On all three, the question flipped. It used to be "what is this." It is now "is this safe" and "is this accurate." Safety is whether a machine will act in your name, touch a file it should not touch, or send a customer something you cannot defend. Accuracy is whether a number, a date, or a promise in the draft is one you would sign.
Write those two answers in language a closer can read aloud. Two sentences each is enough. If you cannot say it on a call without looking down, it is not ready.
A glossary line sounds like this: we use new tools to respond faster and help the team. A safety line sounds like this: a person on our desk still reads anything that names a price, a date, or a promise before it goes to you. If a draft is wrong, we say so and we fix it. The second sentence is the one the radio did not give them. That is the work.
Do not hide a warranty inside a friendly macro. That is how a helper sentence becomes a claim you never meant to make.
Before a real call this week, the closer should read the two new sentences, not the explainer. If they still need the explainer, the rewrite failed.
Who rewrites, who signs
This dies in a team of twenty when everyone "has a look" and nobody owns the paste. Name the seats before Monday, then run them in order.
The support lead pulls every live macro and FAQ line that mentions the new tools. The person on the phone flags any opener that still defines the category. Whoever already writes the help text rewrites those openers into safety and accuracy answers. The sales manager does the same pass on the talk track for outbound and renewals. The owner, not the desk, signs anything that will appear in a contract, a quote, or a public promise. If one person wears two of these hats, they still stop for the owner on claims.
If a line could be read back to you in a dispute, it is not a macro. It is a claim. Claims wait.
Figure 1
Monday is the pull. Wednesday the rewrite sits in front of the people who have to say it. Friday you count what is still live. After this pass, put the next one on the calendar a quarter out. Patrick's point is not that the culture moved once. It is that the talk is now ordinary, which means your snippets go stale when the public story shifts again.
The desk can publish a safety sentence. They cannot publish a warranty. Outbound talk that names a result still goes through a person who can lose the deal if the sentence is wrong. That is the whole split. Speed on the macro. A human on the claim.
What you can count without a survey
Nobody has a credible figure for how many live snippets still open with a definition. Count yours. Friday is not a mood. It is three piles you can see in the help desk and the FAQ.
| Measure | Count |
|---|---|
| Live snippets that still open with a definition | |
| Safety or accuracy answers a closer can read aloud | |
| Claims waiting on an owner signature before they leave the shop |
The number that matters on Friday is the first row. If it did not move, the rewrite did not ship. A beautiful draft in a document is not a shipped snippet.
Kill the glossary openers this week
The live paste is the only copy that matters. Run this on what the desk actually uses, not on a rewrite in a side document.
- Export every live macro, FAQ answer, and call opener that mentions the new tools.
- Mark each one glossary or safety.
- Rewrite every glossary opener so a closer can answer "is this safe" and "is this accurate" in two sentences.
- Send any line that could appear in a quote or a contract to the owner before it goes live.
- On Friday, count the glossary openers that are still live.
You already paste these lines. Rewrite the first one, and send the claims to the owner.
Sources
If one workflow is eating your week, tell me which one. I'll tell you if it's worth deploying — and if it isn't.
Message Mikko on LinkedIn