Voice Literacy
Put six things your company sent last month on one table. The CEO’s note to staff. The CEO’s statement to the market. A message telling a customer no. A policy change announced internally. A support exchange handled by software. A piece from sales, which may be the most polished thing the company sends. Read them in a row. This is a reading exercise; a client audit reads the three to five communications in its agreed scope.
Each one looks fine alone. The policy note reads like a competent policy note. The decline reads like a competent decline. The problem exists in the space between them, and there may be no one in the company whose job is to examine that space.
The wrong question
Executives ask whether the writing is good. The honest answer is that some of it is, which supports no decision. It does not say what to fix, who should fix it, or whether the fix survives the person who made it.
The better question is not about quality. Can this organization produce one voice on purpose? Not in a launch that three senior people reviewed. On an ordinary Tuesday, in a message nobody senior will read, written under time pressure two levels down, possibly with a machine’s help. “Good writing” is difficult to manage across an organization. Capability can be assessed and improved.
A definition
Voice literacy is an organization’s ability to produce language that remains consistent across channels and faithful to its mission. Those two qualities can come apart without anyone noticing.
A company can be perfectly consistent and mean nothing. Everyone writes in the same register, uses the same approved words, and none of it connects to why the company exists. This is what happens when a style guide is adopted without anyone deciding what the organization is for. It may pass an audit that measures uniformity while failing a more important test: whether a customer can tell what you believe from how you treat them when the news is bad.
The reverse is the more tractable problem. People share a real sense of the mission but express it differently, because nobody gave them a shared way to say it. Both look like a writing problem from outside. They need opposite interventions.
Where to look
Not in the launch. An organization can sound like itself in good news, because good news makes it easy to lead with the mission.
Read the adverse message. The denial, the delay, the price increase, the policy that takes something away. This is where the register shifts and the legal department’s vocabulary arrives. Whatever an organization believes about the people it serves shows up most clearly in the paragraph that delivers bad news.
That is also why literacy has to be read from artifacts rather than reported by the people who produce them. Ask a communications team how well the company speaks with one voice and you may get a sincere but incomplete answer. They will describe the intent they hold rather than the full range of output the company produces.
Five levels
One: Improvised. Every writer starts from a blank page. Two departments share almost no vocabulary. It may not register as an organization-wide problem, because the writing looks reasonable from inside each department.
Two: Imitative. People copy the last thing that got approved. The consistency is real but inherited. Errors propagate because the template carries them. A company can be here and believe it is at level three. The tell is that nobody can explain a decision. They can only point at precedent.
Three: Documented. A voice guide exists, built on descriptive traits. Artifacts diverge from it constantly and nobody notices, because nothing checks. The guide records an aspiration; the artifacts record a practice.
Four: Governed. Someone owns the voice and decisions are recorded. The standard survives contact with hard messages, which is the actual test, because a standard that only governs good news is a marketing preference.
Five: Assured. The organization detects its own failures. Testing before release, sampling after, incident review, and a written boundary for anything a machine produces. This is a demanding level, and it may not be a realistic near-term target for every organization.
The dangerous middle
Level two feels like level four from inside, because the output is uniform. What it lacks is any way to change on purpose. When the company needs to sound different, after a repositioning or in a crisis, the template has no give in it, and the organization discovers it never had a voice, only a habit.
Level three feels like progress because there is a document. But a standard with no owner, no enforcement, and no way to detect its own failures remains a file on a shared drive.
Machine assistance makes both more fragile than they were. A template copies faster; a guide is ignored at higher volume. When different people prompt different systems with no shared instruction, the output inherits whatever level the organization was already at and produces far more of it.
How the reading gets done
Six artifacts, chosen deliberately rather than supplied by whoever has time. What the CEO said inside the company and what the CEO said outside it. One adverse decision sent to a customer. One policy or benefits announcement sent to employees. One exchange handled by software. And one piece from sales, because it may be the most polished thing the company produces, and it establishes the ceiling.
That set spans the three tiers a voice travels: what leadership means, what teams carry, what the person on the other end receives. Look for the finding between the artifacts, not inside any one of them. It is in the gaps, and the gaps have a pattern. Warm executive language with procedural customer language is a translation failure in the middle. A confident external voice with an evasive internal one is a trust problem that will reach customers eventually, because employees write the customer messages.
The claim
Every organization already has a voice literacy level. Where no one has chosen it, it was set by default, by whoever wrote the first version of each template and everyone who has copied it since, and the company may not be able to tell you what it is.
You can assess it using messages the company has already sent. And it determines whether any of this work holds after the engagement ends.
The question is not whether your people are good writers. It is whether your company can say what it means on an ordinary day, in a message no one senior will read, and have that still be true a year from now. §
This is the third essay in the Voice Governance framework. The first, What Is Voice Governance?, defines the discipline. The second, The Permission Boundary, specifies what an organization’s automated language is authorized to say. The framework is open: standards, decision rights, and assurance, published as they are written. The practice is where it gets implemented.