Why AI Writing Feels Flat: The Deep POV Fix

You read back the chapter you generated last night and nothing is technically wrong with it. The grammar is clean. Every beat you asked for is there — she finds the letter, she confronts her brother, she walks out. And it reads like a police report of a scene instead of the scene.

Writers call this "flat." Flat is the symptom. The cause has a name, it's been in craft books since 1983, and once you can see it you can't unsee it in AI output: your model is writing from the balcony. It describes your character from a seat several rows back, and no amount of "make it more emotional" moves it closer, because emotion isn't what's missing. Proximity is.

Your AI isn't writing badly — it's writing from too far away

The technical term is narrative distance, or psychic distance: how much space the reader feels between themselves and the character's experience. John Gardner defined it in The Art of Fiction as "the distance that the reader feels between himself and the events of the story," and the useful part of his framing is that it's a dial, not a switch. The University of Nevada, Reno's writing center lays the dial out as a five-step ladder, running from a wide establishing shot down to a character's unfiltered sensory present.

Here's the same moment at three settings on that dial. A harbormaster named Maeve is checking manifests on the north pier in late October.

Wide: It was late October on the north pier, and the harbormaster was working through the week's manifests.

Middle: Maeve hated October paperwork. The salvage filings always ran long, and this year's were worse than most.

Close: Third page. Cargo, tonnage, next of kin — and there, in the clerk's careful hand, her brother's name.

Nothing changed about the plot. What changed is where the reader stands. Ask a language model for "a scene where Maeve discovers her brother is on the salvage list" and you'll almost always get the first setting with better adjectives — competent, and a summary of an experience rather than the experience. Your reader feels the difference two paragraphs in without being able to name it.

What deep POV actually is

Deep POV is the practice of pinning that dial to its closest setting and keeping it there for the length of a scene. Fiction editor Beth Hill's definition is the one I keep coming back to: it's "as close to first-person narration as you can get without using first person" — every word on the page filtered through what this character notices, in the vocabulary this character would use, with no narrator standing behind them explaining.

The common misreading is that deep POV is a point of view, a fourth option next to first, third limited, and omniscient. It isn't — it's a distance setting you apply within third limited. Most published novels move up and down Gardner's ladder constantly: wide for the transition between chapters, close for the moment the letter comes out of the envelope. What separates a scene that lands from one that doesn't is usually that the author descended at the right moment and the AI didn't descend at all.

The three habits that keep AI prose up on the balcony

Three patterns account for most of it, and all three are fixable at the sentence level — which means you can fix them in a draft you already have.

Filter words

A filter word is a verb of perception that inserts the character as an observer between the reader and the thing observed: saw, heard, felt, noticed, realized, watched, wondered, seemed, decided, remembered. The term comes out of Janet Burroway's Writing Fiction, and her formulation of the damage is exact — when you ask readers "to look at rather than through the character", you have started telling instead of showing.

She saw the manifest slide off the desk and heard it hit the boards. Two filters, and the reader is now watching Maeve watch a piece of paper.

The manifest slid off the desk and hit the boards. Same information. The reader is in the room.

AI prose is dense with these because they're the natural grammar of explanation, and an assistant's default mode is explanation. Run a find on "felt" alone in a generated chapter — most of the hits are load-bearing for nothing.

Named emotions instead of the body's evidence

A named emotion is a receipt, not an experience. Maeve felt a surge of grief tells your reader the transaction occurred and gives them no way to feel it. The fix isn't more intense naming — overwhelming grief, crushing grief — it's deleting the name and writing what the name is standing in for. Her hand going flat on the page to stop it moving. Reading the line a third time as if the clerk's handwriting is the thing that's wrong with it. Saying that's not right out loud to an empty office.

A widely-shared r/WritingWithAI post on flat characters reaches the same problem from the character-design end. Its author, who says they've published 22 novels, argues that feeding a model a list of traits produces nothing usable because "adjectives aren't behavior" — and that without a contradiction driving them, "AI writes characters who move through the story in a straight line, which is why they feel flat." Same disease at a different altitude: a trait is a receipt for a person, a named emotion is a receipt for a moment, and readers don't read receipts.

Reaction compressed into report

The third habit is the sneakiest because it doesn't produce bad sentences. It produces good sentences that skip the part you needed. They argued for the better part of an hour, and she left angrier than she'd arrived. That's a clean line. It's also the entire emotional center of your chapter, folded into eleven words and handed back as a summary.

Models compress by default — they're optimized to be legible, and a rendered eight-minute argument is less legible than a sentence describing one. When you ask for a scene and get a paragraph covering the same ground, that's not a failure of instruction-following. It's the model doing to your chapter what it does to any content: making it tidy.

Why the default sits so far out

There's a structural reason to expect convergence toward that middle-distance register, and it's been measured. In a 2024 Science Advances study, Anil Doshi and Oliver Hauser gave some writers short-story ideas from an LLM and others none. Stories written with AI ideas were rated more creative, better written, and more enjoyable — especially from writers who scored as less creative on their own — but those same stories were measurably more similar to each other than the human-only ones. The authors call it a social dilemma: individually better, collectively narrower.

Be careful what you take from that. The study measured stories built from AI-supplied ideas, not AI-drafted prose, and it is not evidence that AI prose is bad. What it establishes is a pull toward a shared center, and narrative distance is one of the axes that center sits on. The model's default isn't wrong. It's average — and average is exactly what you can't afford in the four scenes your book rests on.

A worked pass: one paragraph, eleven minutes

Here is Maeve's discovery scene written the way a model will hand it to you — 190 words, all three habits firing at once:

Maeve saw her brother's name on the third page of the manifest and felt a wave of shock wash over her. She realized what it meant immediately. She had known for weeks that the Tern had gone down off the shoals, but she had told herself he wasn't aboard. Now she knew he was, and grief hit her hard.

Three passes, and I'm not being generous with myself about the time — this took about eleven minutes.

Pass one, filters out. Saw, felt, realized, knew, had known. Cutting them cost 24 words and forced a decision on each one: if I can't say she realized what it meant, I have to show her realizing. That's the whole trick — filter words are load-bearing for evasion.

Pass two, receipts out. A wave of shock, grief hit her hard. Both deleted, replaced with the desk: she squared pages that were already square, then checked the date on the filing against the date on the wreck report, twice, as if arithmetic were the problem.

Pass three, one filter restored on purpose. The paragraph ends with her looking up at the window, and there I wanted half a step back — the reader needs a breath before the scene break. So: Out past the glass, the tide was going out. No perception verb, but the camera pulls back a foot on its own. Deep POV held at a constant 100% for forty pages is exhausting to read; knowing where the dial sits is what lets you move it deliberately.

Final: 166 words, and the difference between a paragraph a reader skims and one they stop on.

When wide distance is the correct choice

Not every paragraph wants to be close, and treating deep POV as a rule rather than a tool produces its own kind of bad book — one with no establishing shots, no time compression, and no relief. Wide distance is right for chapter openings that re-orient the reader in space and time, for the six weeks between act two and act three that nobody needs rendered, and for scenes where the character's read on events is less interesting than the situation. A gruff first mate who has spoken in fragments for two hundred pages and suddenly slips into complete sentences is a deep-POV effect; a line telling you the convoy took nine days to reach the strait is a wide-distance effect. The book needs both.

Making it hold past chapter three

Here's the practical problem nobody warns you about: distance instructions decay. You tell the model to write in deep third with no filter words, it does beautifully for two scenes, and by scene five she felt is back. Context windows fill up, your instruction slides out of the model's effective attention, and you're re-typing the same paragraph of rules into every prompt — which is the same failure mode behind AI forgetting your story details twenty chapters in.

The fix is to stop treating POV rules as prompt text and start treating them as project configuration — a standing constraint that ships with every generation rather than something you remember to paste. That's the logic behind building a reusable Claude Skill for your manuscript, and it's why NovelMage keeps narrative rules and character entries in a Codex attached to the project instead of to a chat thread. Its Character Interviews feature works the other end, putting questions to a character until you have how they operate rather than a list of adjectives — precisely the raw material deep POV runs on.

Write the distance rules down once, in whatever tool you use, in roughly this form: one head per scene; no perception verbs; no named emotions in narration; render reactions, don't report them; widen only at scene transitions. Five lines, and they'll do more for your prose than any amount of "write it more vividly." That same discipline is what keeps generated pages sounding like you instead of like the model — the longer argument for which is in our guide to using AI without losing your writing voice.

Frequently asked questions

Is deep POV the same as first person?

No. Deep POV is a distance setting, not a grammatical person. Most deep POV is written in third person past tense — she, had — with the narrator's voice removed so completely that the prose carries the character's vocabulary and judgments. First person can itself be shallow: a first-person narrator who reports events from a decade's remove sits far up Gardner's ladder despite the I.

Can I use deep POV with multiple POV characters?

Yes — it's the standard approach in commercial fiction. The constraint is one head per scene, with a chapter or scene break before you switch. What breaks it is head-hopping mid-scene: the moment you tell the reader what the other character is thinking, you've reintroduced a narrator who can see into two people, and the intimacy collapses.

Are filter words always wrong?

No, and a search-and-destroy pass that removes all of them will damage your prose. Keep a filter when the act of perceiving is itself the event — she heard it before she understood what it was does real work that it alone can't. Each surviving filter should be a choice you can defend, which in a generated draft usually means keeping about one in five.

How do I stop the model drifting back to distant narration mid-chapter?

Put the rules where the model reads them every time rather than where you have to remember to paste them, and check drift mechanically rather than by feel: search a finished chapter for felt, saw, realized, and seemed. If the count climbs sharply after the midpoint, your instructions have fallen out of effective context, and regenerating the back half with the rules restated at the top usually fixes it in one pass.

Does NovelMage handle this automatically?

Not automatically — no tool can decide where your dial should sit in a given scene, and you shouldn't want one that tries. What it does is remove the re-pasting: narrative rules and character entries live in a project Codex that travels with every generation, and because NovelMage is a native Windows and macOS desktop app that can run models locally through Ollama or LM Studio, or through your own Claude, GPT, or Gemini keys, the manuscript those rules are applied to never leaves your machine. It's $99.99 once for a lifetime license covering up to three devices, with a 7-day full-access trial that doesn't ask for a card.

Start with one scene

Pick the scene your book actually rests on — the one you'd read aloud at an event — and run the three passes on it: filters out, named emotions out, one filter restored on purpose. Eleven minutes. If the result reads noticeably better than the twenty pages around it, you've just diagnosed your whole draft and you know exactly what the fix costs.

Those passes work in any editor you already own. If you'd rather the rules lived in the project than in your clipboard, NovelMage's lifetime license is $99.99 once and opens with a free week.