A founder we work with has one genuinely original idea about Amazon listings. It's good. Operators quote it back to him in DMs. Over eleven months he has published it nine times, and it has had four different names.
In March it was "the dead frame." In May it was "the image nobody briefed." In July it was "slot-seven drift." In August, after a call, it was "the orphan image." Same mechanism every time. Same evidence. Same fix.
When we pulled his content data, the posts about this idea had solid reach and strong comments. What they didn't have was accumulation. Nobody ever wrote "this is the dead frame thing again." Nobody tagged a colleague with "he's talking about slot-seven drift." The idea had been published nine times and had been introduced nine times.
That's what term drift costs, and it's why we now keep a concept glossary for every founder we write for.
What term drift actually does to a LinkedIn content system
A named concept is the smallest unit of positioning a founder can own. Not a topic, since topics are shared. Not an opinion, since opinions are copied within a week. A name attached to a mechanism, used consistently, becomes a handle other people can pick up.
Handles do three things a description can't:
- They let a reader connect post nine to post one. The fifth time someone sees "the revisit ratio," they recognise a body of work. The fifth time they see a different phrase for the same idea, they see five decent posts.
- They travel without you. People can repeat a name in rooms you're not in. They can't repeat a paragraph.
- They get attributed. When a phrase starts showing up in other people's posts and podcasts, it points back at whoever used it first and most. A description points at nobody.
Founders drift for understandable reasons. Repeating a phrase feels like repeating yourself. The writer wants a fresh angle. A new name sounds like a new idea. Every one of those instincts is correct for writing a single post and wrong for building an archive.
We'll be blunt about the cost: an idea published under four names gets roughly the positioning credit of four unrelated posts. We can't give you a percentage for that, because LinkedIn doesn't publish anything that would let us measure it. What we can show you is the DM pattern. Founders with consistent concept names get messages that use their language. Founders who drift get messages that describe their ideas back to them.
What goes in a concept glossary
This isn't a style guide or a list of banned words. A voice bible tells a writer how the founder sounds. A glossary records what the founder has named. Most founders end up with 6-15 entries. If you have 40, you're naming things that don't need names.
Each entry gets six fields:
- The canonical name. One. Exact capitalisation, exact wording. "The revisit ratio," not "revisit rate" or "the return-visit metric."
- The one-sentence definition. Written so a stranger could use the concept correctly. If you can't write this sentence, the idea isn't ready to have a name.
- The mechanism in three lines. Why it happens. This is the part competitors can't copy, because it comes from your access.
- First published use, with date and link. This timestamp matters later. It's the difference between "I've been saying this" and a record that shows it.
- Rejected names. The alternatives the writer or founder will be tempted to use. Writing these down is what actually stops drift, because the tempting synonym is now visibly a mistake.
- Boundary. Where the concept stops applying. "Holds for considered purchases, not impulse SKUs." This is the part that separates the person who built the idea from people repeating it.
The rejected-names field does most of the work. Writers don't drift because they forget the name. They drift because a synonym reads better in a particular sentence. When "slot-seven drift" is on a list marked "don't use," it stops sounding fresh and starts sounding wrong.
When to name something and when not to
Over-naming is the opposite failure, and it's just as common. A founder discovers that named concepts do well and starts naming everything. Six months later the profile reads like a jargon glossary nobody asked for.
Our test has three questions:
- Will you say this more than three times this year? If not, a description is fine.
- Is there a mechanism under it, not just an observation? "Heroes are getting brighter" is an observation. "Colour camouflage, where every hero in a grid converges on the same palette, so the brightest one stops standing out" is a mechanism.
- Would a reader need the handle to repeat it? If the plain description is already short, like "read your return comments," don't give it a name. Nobody needs "the comment pull."
About half the candidates founders bring us fail the second question. That's useful information on its own, because it means the idea isn't finished.
How to fix drift you already have
Most founders who come to us are 12-18 months into publishing and already have drift. The fix is not rewriting the archive.
Pick the name that performed, not the name you like. Search your own comments and DMs for which version other people repeated. That's the name the market already chose. In the founder example above, operators had quoted "the dead frame" back to him four times. Nobody ever used "orphan image." The decision took about ten minutes.
Bridge once, publicly. In the next post that uses the concept, add one clause: "what I've called the dead frame (I've given it a few names this year, this is the one sticking)." That clause joins the old posts to the new name for anyone reading back through the archive. It also reads as honest, which it is.
Don't edit old posts to the new name. Edits don't redistribute, and changing wording on posts people have already quoted creates confusion about what you actually said. Leave the archive alone and let the glossary govern everything from here on.
Add it to the brief. Every draft that touches a glossary concept gets the canonical name and the rejected names at the top. That's the whole enforcement mechanism.
How the glossary connects to the rest of the system
The glossary is small, but it sits between several other things we run for founders:
- The running order decides when a concept comes back. The glossary decides what it's called when it does.
- The claim register tracks numbers that travel across channels. Glossary names travel the same way, into newsletters, podcasts and sales decks, so the canonical name should be the one in the deck too.
- Voice sync calls are where new concepts show up. When a founder explains the same thing twice in two calls, we flag it as a glossary candidate on the call instead of letting it wait until the third draft.
The first sign it's working is almost always in the DMs. Within one to two quarters of consistent naming, prospects start using the founder's language on sales calls without being prompted. That's when an idea stops being content and starts being positioning.
FAQ
Isn't naming concepts a bit gimmicky? It is when the name is doing the work. It isn't when the mechanism is. A name on a thin idea gets you a catchphrase. A name on a real mechanism gets you a handle people use. If the one-sentence definition field is hard to fill, don't name it.
What if someone else is already using my name for something different? Check before you commit. Search LinkedIn and Google for the exact phrase. If it's already taken in ecommerce, pick a different one now, because switching after thirty uses costs far more than choosing twice.
How often should the glossary be updated? Add an entry when a concept passes the three-question test. Review the whole thing once a quarter alongside the running order. Retire concepts you've stopped using so the writer doesn't bring them back by accident.
Should we trademark concept names? Almost never. The value is attribution, not exclusivity. The record of first use in the glossary does more for you than a filing, and a founder threatening people for using their phrase has missed the point of making one.
If your best idea has been published under three different names and you want it to start compounding, that's the kind of system we build for ecommerce founders. Talk to EcomGhosts and we'll look at your archive with you.