A colleague once sent me a project brief that was, by any measure, impressively detailed. Three pages of specifications, timelines broken down by week, deliverables listed with precision. When I asked a clarifying question about the project’s underlying purpose, she seemed surprised. “It’s all in the document,” she said. And it was. Every word was clear, and every sentence was grammatically sound. Yet I had no idea what problem we were actually trying to solve or why it mattered. This happens more often than we acknowledge. A manager writes a carefully worded email about a policy change and is bewildered when half the team misunderstands it. A consultant delivers a presentation with crisp bullet points and discovers later that the client took away something entirely different from what was intended. An academic writes an article that colleagues in the same field interpret in contradictory ways. In each case, the communicator did everything right according to the usual standards. The language was precise, and the structure was logical. The terminology, too, was accurate. The problem lies not in what was said, but in an assumption about how communication works. Most professionals operate on the belief that clarity is primarily a matter of expression. If we choose the right words, structure our thoughts logically, and eliminate ambiguity from our sentences, we will be understood. This seems reasonable. It aligns with what we were taught in school about good writing. It matches our experience of reading well-crafted prose. When we encounter confusion, our instinct is to clarify our language further, to add more detail, to be even more precise. This instinct, however well-intentioned, misses something fundamental about how meaning actually gets made. Consider a senior executive who announces to her team, “We need to be more strategic going forward.” She knows exactly what she means. She has spent weeks thinking about the company’s direction, analyzing market trends, and identifying where the team’s efforts should focus. The word “strategic” carries all of that context for her. It is shorthand for a complex set of priorities and trade-offs that feel obvious from her vantage point. Her team hears something different. To one person, “strategic” means focusing on long-term projects rather than quick wins. To another, it means aligning more closely with what senior leadership wants. To a third, it signals that some of their current work is now considered unimportant. Each interpretation is reasonable. Each is based on that person’s experience, their understanding of the organization, and what they believe the executive values. The word itself has not changed. What has changed is the context each listener brings to it. This is where precision fails us. The executive could have been more specific. She could have listed exactly which initiatives to prioritize and which to deprioritize. But even that level of detail would not guarantee shared understanding, because understanding is not simply a matter of decoding words. It is a matter of interpretation, and interpretation depends on context that often remains invisible to the speaker. The field of pragmatics offers a useful framework for thinking about this. Pragmatics examines how context shapes meaning, how the same words can mean different things in different situations, and how much of what we communicate is actually implied rather than stated. From this perspective, meaning does not reside in words themselves. It emerges in the space between speaker and listener, shaped by what each person knows, assumes, and expects. This raises an important question: if clarity is not just about precise expression, what is it about? It begins with recognizing that your listener is not starting from the same place you are. When you have spent days or weeks thinking about an idea, it feels self-evident. The logic seems clear. The connections seem obvious. But your listener has not been on that journey with you. They are encountering your conclusion without having followed your reasoning. What feels like a small leap to you may feel like a chasm to them. I notice this frequently in academic writing. A scholar will present an argument that makes perfect sense within their theoretical framework, using terminology that has specific meanings in their field. To someone outside that framework, the same argument can seem opaque or even nonsensical, not because the language is imprecise, but because the reader does not share the conceptual scaffolding that makes the argument coherent. The problem is not that the scholar failed to define their terms. The problem is that they assumed a shared context that does not exist. The same dynamic plays out in professional settings. A project manager might say, “We need to move faster on this,” assuming everyone understands what “faster” means in this context. Does it mean cutt
Don't miss out on breaking stories and in-depth articles.
