Organizations communicate constantly. We send emails, publish reports, issue policies, build dashboards, hold meetings, post updates, create campaigns, and distribute alerts. We document what was sent, when it was sent, and sometimes even whether someone opened it. Then, when people misunderstand the message or fail to act on it, we wonder what went wrong.
One possibility is uncomfortable but important: sending information and accomplishing communication are not the same thing.
This distinction seems obvious until we look at how organizations actually operate. “We communicated that” is often used as evidence that communication occurred. The email went out. The policy was posted. The presentation was given. The information exists somewhere on the website. From the perspective of the sender, the task is complete.
But communication is not defined solely by what leaves the sender. It is also shaped by what happens when information enters someone else’s world.
A person encounters a message with existing knowledge, assumptions, experiences, relationships, responsibilities, and constraints. They may already trust the organization—or distrust it. They may understand the terminology—or interpret it differently than the people who wrote it. They may encounter conflicting information from another source. They may understand exactly what the message says but have no practical way to act on it.
None of those conditions exists within the message itself. Yet all of them influence what the message ultimately means.
From Transmission to Meaning
We often talk about communication as though it were primarily a problem of transmission. An organization possesses information, packages it into a message, selects a channel, and sends it to an audience. This model is useful for describing part of the process, but it can also encourage a dangerous assumption: if the information was transmitted accurately, communication was successful.
Human beings are not endpoints in an information-delivery system. We interpret.
We compare new information with what we already know. We look for cues about credibility and intent. We interpret words and images through cultural and social contexts. We notice contradictions between what organizations say and what they do. We rely on other people to help us decide what information means. Sometimes we ignore a perfectly clear message because experience has taught us not to trust its source.
Meaning, in other words, is not simply contained in a message waiting to be extracted. It develops through the interaction between information, people, and context. That changes the communication problem considerably.
The Ecology Around the Message
This is where Design Ecology offers a useful perspective. Rather than isolating the message, we can examine the larger system in which meaning is being created.
Who is communicating with whom? What relationships already exist between them? Through which technologies does information move? What competing messages are circulating? What cultural meanings influence interpretation? What does the physical or digital environment communicate? What institutional policies support—or contradict—the message? What happens after someone receives the information?
These aren’t secondary considerations surrounding communication. They are part of the communication system itself. Consider an organization announcing that it values employee feedback while maintaining processes that make speaking up difficult. The verbal message says one thing. The designed system communicates another.
A public agency can issue technically accurate guidance, but if residents cannot translate that guidance into an action that fits their circumstances, information has been transmitted without necessarily producing useful understanding.
A university can repeatedly tell students where to find a resource, but if navigating to it requires insider knowledge of institutional terminology and organizational structure, repeating the message may never solve the underlying problem.
In each case, writing a clearer message might help. But the message may not be where the real communication problem resides.
Understanding Is Not the Same as Agreement
There is an important ethical distinction here. Designing for understanding does not mean designing communication that guarantees compliance, agreement, or a predetermined response. People have agency.
They may understand a message perfectly well and still disagree with it. They may evaluate the same evidence and reach different conclusions. They may have values, experiences, or priorities that lead them toward another choice.
Strategic communication becomes ethically troubling when understanding is treated merely as an obstacle to persuasion—something to engineer until people behave as the communicator wants.
The better goal is to create conditions in which people can meaningfully engage with information: understanding what is being communicated, evaluating its credibility and implications, asking questions, and making informed decisions. That is a higher standard than simply getting the message out.
Measuring What Matters
This distinction also raises questions about how organizations evaluate communication. Distribution is easy to measure. We can count emails sent, impressions generated, reports downloaded, meetings held, website visits, and social engagement. Those measures tell us whether information traveled. They tell us much less about what happened next.
Did people understand the information? Could they distinguish what mattered from what did not? Did they know what action was available to them? Did the message increase or decrease trust? Did different groups interpret it differently? Did it reach the people who actually needed it? Did the surrounding system reinforce the message or undermine it?
Those questions are harder to answer. They are also often much closer to what organizations actually need to know.
Communication as a Design Problem
Thinking this way changes the role of the communicator. The task is no longer simply to produce the right message and deliver it through the right channel. It requires understanding the environment in which that message will live.
That means studying audiences and stakeholders rather than merely targeting them. It means examining information flows, relationships, interfaces, institutional practices, and cultural context. It means paying attention to feedback and recognizing that communication changes as people interpret, discuss, question, and apply information.
Most importantly, it requires curiosity about the experience on the other side of the message.
Instead of asking, “Did we communicate it?” we might ask, “What did people understand, and what in the system shaped that understanding?” That is a much harder question. It is also a much more useful one.
Because communication did not happen simply because we said something.
Communication happens through the relationships among people, information, environments, technologies, and institutions that allow meaning to emerge. If we want better communication, we have to design for that entire ecology—not just the message moving through it.