Tone of voice, explained without the jargon

The advice here is unglamorous, which is probably why it gets skipped. Here is tone of voice without the vocabulary that usually surrounds it.

Content is the part of a project most likely to be underestimated and most likely to delay a launch. If two people in the business would answer this differently, that gap is the actual problem.

The short version

Write like a knowledgeable person talking, not a brochure. None of that requires a large budget, only a decision and someone to own it. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. The teams that handle this well are rarely the ones with the biggest budgets.

Consistency builds recognition. The reasoning matters more than the rule, because the rule has exceptions. It is the sort of thing that looks like polish right up until it costs you an enquiry.

Where to go from here

Jargon signals insecurity more often than expertise. This is the sort of thing that compounds, quietly, in both directions. Most teams find the first pass takes an afternoon and the maintenance takes minutes a month.

In practice

Pages that answer a real question outlive pages written to fill a slot in a sitemap. Three things worth confirming about tone of voice before you move on:

• Someone can say what the current setup is without going to look
• Jargon signals insecurity more often than expertise — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Worth checking on your own setup before it becomes someone else's problem to fix.