All issues
    October 24, 20263 min read

    Plain Language Is Cultural Infrastructure

    Photograph illustrating Plain Language Is Cultural Infrastructure
    The limits of my language mean the limits of my world.
    Ludwig Wittgenstein

    Language Shapes Participation

    A colleague reads a project update three times and still cannot tell what is changing. The message mentions alignment, enablement, and an accelerated operating model. Everyone else seems comfortable, so the colleague stays quiet. Later, several people act on different interpretations. The problem looks like poor execution. It began with language that made understanding harder than it needed to be.

    For readers of Culture That Lasts, this is a useful place to practice intentional design. An organization’s language shapes who can participate confidently, how quickly people learn, and whether commitments can be examined. When understanding depends on knowing the right insider vocabulary, fluency can become a substitute for competence. People who understand the work may struggle to contribute because they do not yet speak the local dialect.

    Ludwig Wittgenstein wrote, “The limits of my language mean the limits of my world,” in proposition 5.6 of his Tractatus Logico-Philosophicus. His philosophical claim was not a management instruction. Still, it offers a useful prompt for organizational life: what does our everyday language let people see, and what does it leave difficult to grasp?

    Be Precise Without Being Vague

    Plain language does not mean removing technical precision. A laboratory, engineering team, or legal department needs specialized terms. The design question is whether those terms help the intended reader understand something accurately. A precise technical word with a clear explanation can serve people well. An impressive phrase that conceals an unanswered question cannot.

    Consider an announcement that says, “We are optimizing our service footprint to improve customer centricity.” Employees cannot reliably infer whether offices will close, roles will change, or customers will receive different support. A clearer version might say, “Starting in June, two offices will stop accepting walk-in visits. Customers will use appointments or phone support. We have not yet decided how staffing will change.” The second version makes both the decision and its uncertainty visible.

    That visibility matters culturally. Vague language allows different audiences to hear different promises. Concrete language makes it easier to notice consequences, prepare for change, and hold a shared understanding of what has actually been said. It also prevents confidence of delivery from doing the work that explanation should do.

    Design Messages For Understanding

    Start with one document that many people must use: a policy update, project brief, or service announcement. Give it a simple editorial structure: what is happening, who is affected, what the reader needs to do, and what remains undecided. Expand unfamiliar abbreviations on first use. Replace abstract nouns with people and actions wherever possible. “Managers will confirm assignments by Friday” is more useful than “Assignment alignment will be finalized.”

    Then check comprehension, not approval. Ask someone from the intended audience to explain the message in their own words and describe what they would do next. Make clear that you are testing the document, not the reader. If their interpretation differs from yours, revise the wording rather than defending your intention. A friendly “Does this make sense?” rarely reveals as much.

    Rewrite One Consequential Message

    The practical takeaway this week is small: rewrite one consequential message before it travels. Give the communication owner responsibility for checking understanding, not merely sending information. Over time, this practice teaches a durable cultural lesson: expertise should make the work more understandable, not make the expert harder to question. People should not need an interpreter to know what their organization expects of them.

    Tips for building lasting culture

    1. 1

      Rewrite one policy announcement under four headings: what is happening, who is affected, required action, and what remains undecided.

    2. 2

      Ask an intended reader to paraphrase a draft message and describe their next step before you publish it.

    3. 3

      Expand unfamiliar abbreviations on first use in your next project brief and remove jargon that adds no precision.

    Never miss an issue

    A new quote, article, and set of tips every Saturday morning.

    Browse the full archive