Guide
Your prompt has no sources. That's why the output has no voice.
Models trained on internet averages pull every draft toward the median. The fix is editorial: what you load before the cursor moves decides whether the output is yours.
The Sunday-night draft that reads like everyone else's
A newsletter writer opens a chat window on Sunday night, types 'draft a post about why most onboarding fails,' and pastes the result into her editor twenty seconds later. It reads fine. Clean topic sentences, a tidy three-point structure, a closing line that gestures at insight. It also reads almost exactly like the version a competitor in her niche published the same week, because they both started from the same blank box and asked it the same vague thing. The output had no voice because the input had no sources. That is the whole problem, and almost nobody treats it as one.
Sourcing debt: the specifics you never paid
Every general model predicts the most probable next stretch of text across a corpus that is, by construction, the internet's average. Hand it a vague topic and it has nothing to anchor on but that average, so it returns the average, dressed in whatever register you requested.
The gap that produces this has a name worth using: sourcing debt. It is the specifics you owed the draft and never paid. Real names, real numbers, a real thing someone said. Skip them at the input and the model fills the hole the only way it can, by reaching for the most common phrasing in its training. Median in, median out.
A tone guide can't rescue an empty prompt
The standard fix you will find under every 'why does AI writing sound the same' thread is a style instruction. Write like Hemingway. Adopt a persona. Paste a 600-word tone guide. Add three adjectives that describe your brand. The whole industry of prompt advice points at the same lever, and it is the wrong one.
A persona prompt changes how the median is dressed. It does not change that it is the median. Tell the model to be punchy and it gives you punchy generic. Tell it to be warm and you get warm generic. Style instructions operate on the surface of a draft that was already going to say the obvious thing, because nothing specific was ever put underneath it. You can sand and paint a draft endlessly. It will still be built from the same average material.
Creators are already naming the problem
The diagnosis is not new and it is not niche. Across r/writing and the SaaS and marketing subreddits, on LinkedIn, in Medium essays and PR Daily columns through the first half of 2026, working creators keep arriving at the same complaint: the drafts all sound like each other, and a reader can now smell it.
What is striking is how consistent the proposed cure is across all of those venues, and how consistently it underdelivers. The threads recommend better persona prompts, custom instructions, fine-tuned voice presets. People try them, report a marginal lift, and post the same complaint again a month later. The discourse has correctly identified the symptom (homogenization) and almost universally misdiagnosed the cause (style) by looking at the step after the one that actually decides the outcome.
The same story, two inputs
Take a single story you might actually cover: a SaaS company quietly raising prices and a few small customers walking. Hold the story constant and change only what you load. The persona, the tone request, the model can all stay identical. The difference at the sentence level is not subtle.
The vague prompt produces a sentence that could open ten thousand other posts. The source-loaded prompt produces a sentence that could only describe your story, because the specifics in it are yours and exist nowhere else in the model's training. That is the entire mechanism, visible in two opening lines.
The work happens before the cursor moves
If sourcing debt is the real lever, then the work that determines whether a draft has a voice is finished before the first word is generated. Editorial preparation is prior to and separate from tool use. The best prompt ever written, run over an empty research folder, still returns the median.
This reorders the whole job. The scarce, valuable, hard-to-copy part of publishing was never the drafting; it was deciding what is worth covering, finding the real material behind it, and knowing which detail is the one that makes the piece yours. Drafting is the cheap step now. The expensive step, the one that creates voice, is the sourcing that happens upstream of any cursor.
Research the signal first, draft second
Niche is built around that order. The desk takes the upstream half as its actual job: surface what is moving in your beat this week, attach the named sources and real data points behind a story before you ever frame it, and keep your brand-voice memory loaded so the specifics that are yours are already in the room when the draft begins.
The point was never a faster way to prompt. A faster prompt over nothing just gets you to median quicker. The point is having something to prompt with: a story you chose for a reason, sources you can cite inline, an angle that is yours because the material under it is yours. Differentiated prose is a downstream byproduct of that, not a setting you toggle.
What we're watching next
We are watching one shift. As more creators load real sources by default, the homogenization complaint should migrate from 'the writing sounds the same' to 'the research is shallow.' The lever moves upstream again, this time to whose sourcing is deeper and whose beat coverage is wider. The drafts converge; the differentiator keeps retreating toward the work that happens before anyone opens a chat box.
Frequently asked questions
Why does AI writing sound the same?
Because a general model predicts the most common phrasing across its training, which is the internet's average. Give it a vague topic with no named sources, numbers, or quoted observations and it has nothing to anchor on, so it returns that average. The sameness is a sourcing gap at the input, not a flaw in the model's style.
How do I make AI writing sound like me?
Load specificity before you draft, not after. Feed the real named sources, the actual data points, and the exact things people said behind your story. Sentences built from material that exists nowhere else in the model's training read like you, because only your story could produce them. A persona prompt over an empty research folder still returns the median.
Do persona prompts and tone guides fix the problem?
Only at the surface. A persona changes how a generic draft is dressed, not whether it is generic. Style instructions operate on a draft that was already going to say the obvious thing because nothing specific was put underneath it. The lever is editorial preparation upstream of the prompt, which is prior to and separate from any tone setting.
Isn't this just prompt engineering by another name?
No. Prompt engineering optimizes the instruction. This argues the deciding work happens before the instruction exists: choosing the story worth covering, finding the real material behind it, and identifying the one detail that makes the piece yours. The prompt is the last step. The sourcing is the step that creates voice.