Voice Profile · 7 min read
How to describe your writing voice so anyone can write like you
A repeatable method for writing down your voice so a ghostwriter, assistant, or AI tool produces drafts that actually sound like you.
"Conversational but professional" tells a writer nothing, because every client on earth says it and no two of them mean the same thing. A usable description of voice is made of rules and examples. Adjectives are decoration on top.
Start with ten posts you would publish again
Everything below comes from reading real work, not from imagining an ideal tone. Pick ten posts you are still happy with. If you only have five, use five. The exercise fails the moment you start writing down aspirations, because aspirations are what produced the mismatch you are trying to fix.
Turn observations into rules
- "I open with a scene, almost never with a claim."
- "I use contractions everywhere, including in the first line."
- "I never use the word leverage, and I never say we when I mean I."
- "My paragraphs run one to three sentences, and I break to a single line for emphasis about once per post."
- "I end with a question roughly half the time, and the question is always one I actually want answered."
- "I name the client type but never the client."
Rules work because they are falsifiable. Someone can read a draft and tell you it breaks rule three. Nobody can tell you a draft breaks "warm."
Attach an example to every rule
One line of your own writing per rule is the difference between a document that gets followed and one that gets skimmed once. Examples also catch the things you did not manage to articulate, because a writer copying your rhythm will absorb details you never noticed you had.
Test it on someone else
Hand the rules to a colleague, ask for one draft, and read what comes back. Everything wrong in that draft is a rule you have not written down yet. Two rounds of this usually gets you a document that holds up, and it is much faster than trying to think of every rule up front, because you cannot see your own defaults until someone else gets them wrong.
Keep it short enough to be used
Ten to fifteen rules is plenty. A three-page document will not be read before a draft, and a document that is not read before a draft may as well not exist.
