How the work gets done.

Review the communications. Assign responsibility. Build the standards. Test and improve.

The scope varies. The sequence does not. An audit identifies what needs attention. A broader engagement establishes ownership, standards, and testing.

A Voice Audit begins with three to five high-stakes customer communications and traces each problem back to the policy, template, or decision behind it. A Voice Governance engagement examines the full chain: three tiers that function as one system. The three engagements, with scope and deliverables, are described on the Services page.

• C-level communication, internal and external, establishes what the company means.
• Internal alignment determines whether that meaning survives or fragments.
• Customer-facing communication shows the result.

We examine the messages people receive, then trace the problems to the decisions and processes that produced them.

01 · Review the communications

We begin with what people actually received. Then we trace that language through the communications, policies, presentations, and processes behind it. We interview the people who create these communications and, where possible, the people who receive them. You get a map showing where the voice your company intends diverges from the language it produces.

02 · Assign responsibility

We establish who owns the voice, who approves its use, and who intervenes when it fails. This is a governance question before it is a language question. Without explicit ownership, standards become optional.

03 · Build the standards

We build the Voice Governance Standard: operating rules, guidance for recurring situations, shared terminology, who can approve what, and who to bring in when a case does not fit the rules. We train the people who will use it, so the voice belongs to the organization rather than a handful of writers.

04 · Test and improve

We test communications before release, sample them afterward, review incidents, and correct the system. A system that cannot detect its own failures cannot govern them.

Where we work

Health, education, and financial services organizations, and the technology companies that support them, produce communications that carry consequences: coverage decisions, loan determinations, financial aid notices, and care instructions. At the moment of decision, the message becomes part of the product. A language failure becomes a product failure.

The people receiving these communications may be under stress, reading in a second language, using assistive technology, or working through a process they had no hand in designing. The same organizations are now using AI to draft, adapt, and deliver those communications. Our work is to make sure the language holds.