Bobadilla v. The Dialect Problem
On shared language, operational drag, and the document nobody told you to build.
Every company has its own dialect. But that isn't a communication problem in the way most people think about communication problems. It's not about tone or clarity or whether your team likes each other enough to speak honestly. It's about the fact that inside any organization, words accumulate meaning over time, and that meaning is not always the same meaning the word has everywhere else, and almost nobody notices until something goes sideways.
Take "compliance." In a regulated business, compliance is everywhere. There's a compliance department. There's a compliance policy. There's a compliance framework. There's a code of conduct that is itself a compliance document. When someone says "we need to run this through compliance," they might mean the department, the policy, the regulatory requirement, the internal review process, or all four simultaneously. Everyone in the room nods. Nobody is nodding at the same thing. The meeting ends. The project moves forward. Three weeks later something falls through a gap that everyone assumed someone else was covering because everyone heard the same word and understood something different.
This is the dialect problem. It's not dramatic. It doesn't announce itself. It just quietly generates confusion, misaligned expectations, and the kind of operational drag that costs money and energy without ever producing a clear incident report you can point to.
What Operational Drag Actually Costs
Operational drag is friction in a system that costs money or energy. It's the energy wasted on inefficient processes, the meetings that required follow-up meetings to clarify what the first meeting meant, the new hire who learned the wrong definition of a term in week one and carried it forward for two years before anyone caught it. It's the difference between a team that moves cleanly and a team that moves through sludge, and it almost never has a single identifiable cause. It accumulates. It compounds. And because no single instance of it is catastrophic, it tends to go unaddressed until the drag becomes so significant that something actually breaks.
A company glossary is one of the most underrated tools for reducing operational drag because it attacks the problem at the root, which is that your team doesn't have a shared, documented, agreed-upon definition of the words they use most often to run your business. Most founders have never thought to or been told to build one. Most boilerplate business advice and professional business coaches don't mention it. It doesn't appear on any standard checklist for launching a company. And yet the absence of it is one of the most consistent sources of friction I see inside founder-led businesses, regardless of industry, regardless of size, regardless of how smart and well-intentioned the people involved are.
What a Company Glossary Actually Is
Before we go further, let's be clear about what a company glossary is not. It's not a legal document. It's not a compliance requirement. It's not a formal HR deliverable that needs to be drafted by counsel, reviewed by a committee, and filed somewhere. There are no rules about what it has to contain or how it has to be structured. Anyone who tells you there's only one right way to build one is selling you boilerplate advice that doesn't account for the actual shape of your business, which is the most expensive kind of advice there is.
A company glossary is a living precision tool. Its job is to close the gap between what leadership thinks is being communicated and what's actually landing. It defines the words your business uses most often, in the way your business actually uses them, so that when someone new joins the team they're learning your dialect deliberately rather than absorbing it accidentally. So that when two departments are in conflict, there's a shared reference point for what the relevant terms actually mean. So that when you're negotiating a contract or reviewing a vendor agreement, you have a clear internal record of how your company defines the concepts at stake. It starts at onboarding and lives on forever, growing and updating as the business grows and changes, referenced when things get confusing and revised when the confusion reveals a gap.
What It Can Include
The simplest version of a company glossary is a document that defines the terms your team uses most frequently and most ambiguously. That alone is worth building. But if you want to push further, a glossary can expand into something more comprehensive that functions as an operational reference for the whole business. Here's a range of what it can include, from the essential to the ambitious:
Core business terms defined in your company's specific context, not the dictionary definition, your definition
Acronyms and their meanings, because every company develops shorthand that new people have to decode
Role definitions that clarify what each function actually owns versus what it influences or supports
Decision-making language that distinguishes between who decides, who needs to be consulted, and who just needs to be informed
A systems inventory that maps the tools and platforms your business runs on and what each one is used for
A data map that identifies what information lives where and who has access to it
The Bus Factor for critical functions, meaning an honest accounting of which parts of your business would stop functioning if a specific person were suddenly unavailable
That last one sounds morbid but it's one of the most useful risk assessments a small business can do. The Bus Factor asks a simple question: if this person got hit by a bus tomorrow, would the business survive? If the answer is no, that's not a personnel issue. That's a documentation and redundancy issue, and the glossary is where you start to address it.
The Terms Every Founder Should Know But Probably Doesn't
Since we're on the subject of shared language, here are a handful of terms from the Field Notes glossary that I think belong in every founder's working vocabulary. These aren't obscure legal concepts. They're practical tools for thinking more clearly about your business, and having the word for something is often the first step toward being able to address it.
Operational Drag. The energy or money wasted on inefficient processes. This one is worth knowing because once you have the term, you start seeing it everywhere. The meeting that could have been an email. The approval process that involves four people when two would do. The system that was built for a five-person company that's now being used by twenty. All of it is operational drag. All of it has a cost. Naming it is the first step toward fixing it.
Ground-Truthing. The process of verifying your strategic map against the actual reality of the terrain. In business this means comparing your vision, your plan, your assumptions about where things stand, to your actual bank balance, your actual calendar, your actual capacity. Founders who skip this step end up making decisions based on where they thought they were rather than where they actually are.
Bus Factor. The measurement of risk concentrated in a single person. Every business has at least one. Most have several. Knowing yours is basic risk management.
Waiver. Voluntarily giving up a right. This one matters because founders waive rights accidentally all the time without knowing it. If you let a client pay late ten times without penalty, you may have waived your right to charge a late fee the eleventh time. Behavior creates precedent. Precedent has legal implications. A glossary that includes this term helps your team understand why consistency in contract enforcement isn't just a preference, it's a protection.
Piercing the Corporate Veil. When a court ignores the separation between owner and business because funds were commingled or something was handled improperly, making the owner personally liable for business debts. This is the reason your entity structure matters. This is the reason keeping business and personal finances separate isn't just good practice. It's the whole point of having an entity in the first place.
Operational Drag, again. Worth repeating because it's the one that connects everything else. Every term on this list, when misunderstood or ignored, generates operational drag. The glossary is how you prevent that.
How To Build One
Start with the words your team uses most often and define them in the way your business actually uses them. Not the dictionary definition. Not the legal definition unless the legal definition is the one your team uses. Your definition, in your context, reflecting your actual operational reality. Write it down somewhere everyone can access it. Make it a living document, not a filing cabinet artifact. Add to it when something causes confusion. Revise it when the confusion reveals that the existing definition is wrong or incomplete. Reference it when things get murky. Use it in onboarding so that new people are learning your dialect deliberately rather than absorbing it accidentally and hoping for the best.
There's no required length, no required format, no required review cycle. The only requirement is that it reflects how your business actually works rather than how someone else told you a business is supposed to work. A one-page list of definitions that your team actually uses is worth more than a fifty-page policy manual that lives in a shared drive and hasn't been opened since the person who wrote it left the company. The goal is a document that reduces confusion in practice, not one that looks comprehensive on paper.
If you want to start today, open a blank document and write down the five words that caused the most confusion in your business last month. Define them. Share it with your team. Ask if they agree with the definitions. The conversation that follows is the beginning of your company glossary, and it will tell you more about where your operational drag is coming from than almost any other exercise you could do this week.
The Precision Tool
Language is a precision tool. That's the first line of the Field Notes glossary and it's the truest thing in it. When everyone in your business is using the same words to mean the same things, the operational drag drops. The decisions get cleaner. The onboarding gets faster. The misaligned expectations that were generating confusion and dropped balls and follow-up meetings to clarify the first meeting stop compounding. That is not a small thing for a founder-led business where time, energy, and money are all finite and none of them can be wasted on problems that a shared document could have prevented.
You don't need a consultant to build it. You don't need a committee to approve it. You don't need legal review unless you want one. You need a blank document, the words your business uses most, and the willingness to write down what you actually mean when you say them.
Start there. The rest follows.
- m
