Voice is not a tone setting. It is the accumulated result of what you notice, what you refuse to say, how much you hedge, and which claims you will stand behind when someone pushes back. An assistant can imitate the surface of that and miss all of it. Keeping your voice means giving the tool a narrower job than writing for you.
- Write the reader, the claim, and three trusted observations yourself before any request.
- Favor compression, critique, and reordering over open-ended generation.
- Keep a voice card listing preferences, anti-preferences, and two samples you still admire.
- Rewrite the load-bearing paragraph of each section by hand.
- Read the draft aloud; sentences you would not say out loud do not belong to you.
What voice is actually made of
Some of it is surface: sentence length, punctuation habits, whether you use semicolons, how often you reach for a metaphor. Those patterns are learnable from samples, and an assistant will reproduce them reasonably well if you show it enough of your work.
The rest is judgment. Which detail you lead with, which counterargument you take seriously, where you concede, what you find funny, what you consider beneath mentioning. That layer comes from having lived through the thing you are writing about, and samples cannot encode it.
Write the claim before you ask for prose
Before any request, put four things on the page in your own words: the reader, the single sentence you want them to accept, the response you want from them, and three observations you personally trust. It takes a few minutes and decides the character of everything after.
Without it, the assistant supplies a position by default — usually a balanced, agreeable one that offends nobody. You will then spend the revision arguing yourself out of somebody else's framing, which is slower and duller than framing it yourself would have been.
Style is what a model can copy; voice is what you are willing to defend.
Prefer transformation over generation
Ask for six headline variants on a line you wrote. Ask which paragraph is doing the least work. Ask what a hostile reader would say. Ask for the same argument in half the words to see what survives. Each keeps your material as the substrate.
Generation inverts that. When the assistant writes first and you edit after, the structure, emphasis, and vocabulary are already set, and editing mostly means smoothing someone else's choices. Authorship is decided by who makes the first structural decision, not by who types the last word.
Build a voice card from your own sentences
Write half a page of instructions to yourself: preferred sentence length, level of formality, how you handle examples, whether you address the reader directly, and a blunt list of phrases you will not use. Anti-preferences do more work than preferences here.
Attach two or three passages you would still be happy to have written. Choose work that sounds like where you are going, not where you started. Then treat the card as guidance for a collaborator, not a filter for fixing flat prose afterwards.
Learn the tells of unedited machine prose
Watch for triads that add nothing, escalating restatements of a point already made, transitions that promise contrast and deliver agreement, and closing paragraphs that summarize instead of landing. Watch for hedged claims that avoid committing to anything checkable. None of these are errors exactly. They are the texture of prose written to be inoffensive.
The deeper tell is evenness. Machine drafts tend to give every section the same weight and the same confidence. Real writing is lumpy: it dwells where the writer cared, hurries past what bored them, and admits uncertainty in specific places rather than uniformly.
Edit by ear, then take the pen back
Read the passage aloud. Your voice will stall at sentences you would never say, and it will speed up where the rhythm is yours. This is a cheap test and it catches most borrowed phrasing before a reader ever sees it.
Then rewrite at least one paragraph per section entirely by hand — the one carrying the most weight. A piece can absorb a lot of assisted prose as long as the load-bearing sentences are yours, because those are the ones readers quote back to you.
When flattening your voice is fine
Not every document needs a personality. Release notes, internal process docs, form letters, and status summaries are better neutral. Spending voice on them is a misallocation, and readers of those genres want speed, not company. Nobody rereads a changelog for the prose.
Decide the register deliberately per document rather than by default. The risk is not that you flatten a changelog. It is that the flattening habit follows you into the essay, the argument, and the piece that was supposed to sound like a specific person.
A smoothed paragraph and the one that replaced it
The assisted version: "In a competitive market, effective onboarding has never been more critical. Organizations that prioritize a seamless user experience consistently see stronger engagement and improved retention. By streamlining initial setup, companies can reduce friction, foster trust, and empower users to realize value faster. Ultimately, a thoughtful onboarding strategy is not merely a nice-to-have. It is a strategic imperative that drives long-term growth and positions a business for sustained success."
The rewrite: "We cut setup from twelve steps to five because step four was breaking people. Most of the tickets we answered last year came from that one screen. Removing it was not a strategy; it was an apology. What we learned is narrower than a growth thesis. If a step exists only because the software needed it, customers will find it and resent it. We took the step out. The tickets about it stopped arriving, and nobody has asked for the wizard back."
The second version says things the first cannot: a specific decision, an admission, and a limit on the claim. None of that arrived by asking for a warmer tone. It came from putting the writer's own knowledge back on the page.
Common mistakes
| The mistake | Why it costs you, and what to do instead |
|---|---|
| Asking for "my style" as a tone instruction | A one-word register request produces an average of that register, not you. Supply actual samples and a list of phrases you avoid, then check the result against them rather than trusting the label to carry the work. |
| Editing only at sentence level | If you accept the generated structure and fix the wording, the piece keeps someone else's emphasis. Reorder the sections yourself first, then worry about phrasing. Order is where a point of view actually lives. |
| Keeping a sentence because it sounds good | Fluency is persuasive on the page and hollow under questioning. If you cannot say where a sentence came from or what it commits you to, cut it, even when it is the smoothest line in the paragraph. |
| Feeding it your worst work as reference | Samples chosen for convenience teach the habits you were trying to leave behind. Pick two or three passages you would happily reread, and refresh them as your writing changes rather than leaving old material in place. |
Your checklist
- State the reader and your single claim in writing before opening any request.
- List three observations only you could contribute to this piece.
- Convert generation requests into transformation requests on text you already wrote.
- Run the draft against your anti-preference list and cut every match.
- Rewrite the heaviest paragraph in each section without assistance.
- Read the finished piece aloud and revise anything you stumble over.
Key terms
- Voice card
- A short written brief on how you write: sentence habits, formality, use of examples, phrases you refuse, and two or three sample passages you still stand behind.
- Register
- The level of formality and distance a document adopts for its reader. It is chosen per document, and it is a smaller thing than voice, which persists across them.
- Anti-preference
- A phrase, construction, or habit you have decided never to use. Listing these constrains a draft more effectively than describing the style you want.
Working on a draft with AI right now?
Frequently asked questions
Can an AI model actually learn my writing style?
+
An AI model can pick up repeatable surface patterns from a handful of samples — cadence, sentence length, punctuation habits. What it cannot pick up is the judgment underneath: why you chose that example, what you declined to claim, and where you decided to be blunt.
How many writing samples should I supply?
+
Two to five is usually enough for practical guidance, and more than that tends to average your registers together. Choose pieces written for a similar reader, and drop anything you no longer want to sound like. The samples are a target, not an archive.
Is it dishonest to use AI assistance at all?
+
Using a tool for compression, critique, or alternatives is ordinary craft, the way an editor's query is. The line most writers settle on is authorship of the argument and responsibility for every claim. Where a publisher or client has a disclosure policy, follow it.
My drafts still come out generic. What is wrong?
+
Usually the claim is generic, not the prose. If the piece is arguing something nobody would dispute, no amount of stylistic work will make it sound particular. Sharpen the position until someone could reasonably disagree, and the voice problem often solves itself.
Should I keep a separate voice card per publication?
+
Yes, if you write for outlets with genuinely different registers. Keep one card for your own writing and short variants for each regular venue, noting what changes: formality, use of first person, how much you explain, and whether humor is welcome.
How do I tell whether a passage still sounds like me?
+
Cover the byline and read it to someone who knows your work. Failing that, compare it against a paragraph you wrote before you had any assistance and look for what is missing: the aside, the concrete number, the joke you would have made.