Early in my time at Amazon, I described something as a “process.” I got corrected, politely but immediately: that’s a mechanism. I remember thinking the distinction was corporate theater. I was wrong. At Amazon, a mechanism has a definition: a complete, closed loop; a tool plus the adoption of the tool plus the inspection that makes it improve. “Good intentions don’t work. Mechanisms do.” One term, precisely defined and relentlessly repeated, carried an entire operating doctrine into every meeting I sat in for years. Nobody had to re-argue the doctrine. The name did the work.

Last weekend I published Be Gruntled; I Am, about my mission to make people use the word gruntled. Several people asked, in effect, “why do you care so much about one word?” Because this is a leadership pro-tip hiding in plain sight:

Effective leaders master the skill of choosing memorable terms, defining them precisely, and using them with unreasonable consistency. I call these load-bearing terms: words and phrases that hold up part of the structure. Remove one and something falls down.

A load-bearing term works because it snags. Gruntled makes people pause, think, ask, and debate; that pause is the feature, not the bug. A term that slides by frictionlessly (“synergy,” “alignment,” “program”) carries no load because nobody has to stop and grab hold of it. A term that is slightly odd, slightly wrong, or stolen from another domain forces the question “what exactly do you mean by that?”, and the answer is where the doctrine gets installed.

Kenneth Burke called vocabularies terministic screens back in 1966: a word choice doesn’t just describe reality, it directs attention toward some things and away from others. Fairhurst and Sarr wrote a whole book, The Art of Framing: Managing the Language of Leadership, arguing that framing through language, including deliberate jargon and catchphrases, is a core and learnable leadership skill. Gioia and Chittipeddi named the activity sensegiving in 1991. Eric Evans got closest in Domain-Driven Design (2003) with ubiquitous language: a rigorously defined shared vocabulary, enforced in conversation and in code, with drift treated as a defect. The Heath brothers’ Made to Stick explains the mechanics of why concrete, unexpected words outlive abstract ones.

The academics found this repeatedly and named it framing, sensegiving, and ubiquitous language. Those names didn’t snag; the concept kept getting lost. I’m giving it a name that can carry the weight: load-bearing. (And yes, the AIs have lately worn “load-bearing” shiny; some readers now flag it as a chatbot tell. Tough. The machines learned the metaphor from us. I’m not abandoning a good word to the robots; that would be letting the counterfeiters retire the currency.)

The masters were doing it long before the academics named it:

• Bezos built Amazon on load-bearing terms: mechanism, Day 1, bar raiser, two-pizza team, working backwards. Each has a written definition, and each compresses a doctrine. Say “bar raiser” in any Amazon building on Earth and everyone knows exactly what is meant, and what is expected.

• Musk has The Algorithm: question every requirement, delete the part, simplify, accelerate, automate. Note the definite article. It is not “an algorithm” or “our five principles.” The name is doing deliberate work: there is one, and it is not optional.

• Toyota ran the same play in Japanese: kaizen, andon, muda. The words survived translation into every factory on the planet precisely because they snag; an English speaker cannot say kaizen without having been told what it means.

I’ve run this play my whole career, and I wrote about the infrastructure for it in Taxonomy and Lexicon: every endeavor I lead gets a written lexicon, and I am obnoxious about consistent usage. Tenets are the same trick at the sentence level. It matters even more now that half your team is AI agents; a precise, consistently-used lexicon is the difference between an agent that gets it and an agent that guesses.

Tenets for Load-Bearing Terms (unless you know better ones).

1. Pick a term that snags. Pithy, slightly odd, slightly archaic, borrowed from another domain, or defined more narrowly than its everyday meaning. If nobody ever asks “what do you mean by that?”, the term is carrying nothing.

2. Write the definition down. A load-bearing term without a written definition is just a verbal tic. One sentence, somewhere everyone can find it.

3. Use it with unreasonable consistency. Avoid synonym-swapping for variety. Leaders repeat themselves on purpose, and the repetition is the point.

4. Police the drift. “That’s a process, not a mechanism” feels pedantic the first ten times. The eleventh time, someone else says it, and now you have a culture.

5. Watch for the tell. You know a term is load-bearing when people use it correctly in rooms you’re not in, to people you’ve never met. That’s when the term is holding weight instead of you.

The failure mode is obvious and everywhere: coining terms nobody needs, for concepts that deserve no weight. Deming saw it seventy years ago (point 10 of his famous fourteen is “eliminate slogans”). The test is the definition. If the name compresses a real doctrine you’re prepared to write down and enforce, it will bear load. If it decorates a slide, it won’t.

What are your organization’s load-bearing terms? If you can’t name three, what doctrine are your people re-arguing from scratch in every meeting? Leave a comment or find me on X at @tigkindel. I’d be gruntled to hear them.