What Dialogue Doesn't Say

The worst line of dialogue I have ever cut answered the question it was asked.

I do not remember the scene anymore, but I remember the line, because I remember the relief of deleting it. A character asked another character what was wrong. The second character said what was wrong. Two lines of dialogue, doing exactly what dialogue is supposed to do on the surface, and doing nothing at all underneath. I cut it and replaced it with a non-answer. The scene came alive. I have been suspicious of direct answers ever since.

This is the subject of this post: the difference between dialogue that answers the question and dialogue that answers something else, and why the second kind is almost always the one worth writing.

Here is the failure mode, in its plainest form.

"What's wrong?" "I'm scared we're going to lose the house. I haven't told you because I didn't want you to worry, but the payments are three months behind and I don't know what to do."

This is not bad writing in the sense of clumsy sentences. The sentences are fine. It is bad in the sense that it has done the emotional work for the reader instead of letting the reader do it. The character has diagnosed her own fear, packaged it, and delivered it in a single uninterrupted paragraph, the way a person delivers a prepared statement rather than the way a person speaks when they are actually afraid. Real fear does not organize itself into a topic sentence and two supporting clauses. Real fear deflects, minimizes, changes the subject, and then, if it surfaces at all, surfaces sideways.

Here is the same beat, rebuilt.

"What's wrong?" "Nothing." She was folding a towel that was already folded. "Long day." "Sarah." "I said it's nothing."

The character has not told us what is wrong. She has told us that something is wrong, which is a different and more useful piece of information, because now the reader is doing the work the first version did for them. The reader notices the towel. The reader notices that "long day" is not an answer to "what's wrong," it is a deflection dressed as an answer. The reader notices that repeating "I said it's nothing" is not a denial, it is an escalation, because you do not have to repeat something you actually believe.

This is what dialogue is for. Not delivering information. Producing the gap between what a character says and what a character means, and trusting the reader to live in that gap.

The technical name for this is subtext, and every craft book mentions it, and almost none of them explain how to actually build it, because the building is less a technique than a discipline of refusal. You have to know what the character actually means, in full, before you can write dialogue that does not say it.

This is the part that trips writers up. You cannot write evasive dialogue by being vague about what is being evaded. Vagueness on the page produces vagueness in the reader's experience, and the reader ends up confused instead of intrigued. The character in the example above is not confused about what is wrong. She knows exactly what is wrong. The dialogue is evasive. The writer is not.

So the actual practice is this: write the real conversation first, privately, the one where the character says everything. Get the full confession down, the whole explanation, the entire load of what she is afraid of and why she has not said it and what she thinks will happen if she does. Write it badly if you have to. Write it as therapy-speak, as exposition, as the thing you would never publish. Then take that conversation away from the character and give them almost none of it.

What you keep is not the content. What you keep is the shape the content left behind. The character who was going to say "I'm scared we're going to lose the house" now says "long day," but she says it while folding a towel that does not need folding, and the towel is doing the work the sentence used to do. The writer knows what she is not saying. The reader can feel the shape of it without being told the content, the way you can feel the shape of a stone under a rug without lifting the rug.

The most reliable technique for building this is the answered-wrong-question move. A character is asked one thing and answers a different thing. The difference between the question and the answer is where the meaning lives.

"Did you call the doctor?" "I made coffee. You want some?"

Nobody reading this thinks the second character forgot the question. The reader understands, instantly and without being told, that the coffee is an evasion, and the evasion itself is the answer. Something about the doctor, or the appointment, or what the doctor might say, is being avoided. The reader does not know what, specifically, and does not need to. The avoidance is the information.

"Where were you last night?" "You look tired. Did you sleep?"

Again: nobody thinks this is a non sequitur. The reversal of the question back onto the asker is a classic deflection, the kind real people do when they do not want to answer and are buying time by pretending to be concerned about something else. The reader clocks it immediately, because readers are people, and people recognize deflection because they have both used it and been on the receiving end of it their entire lives.

This technique works because it relies on something the reader already knows about human conversation and simply declines to spell out. The writer is not teaching the reader a code. The writer is refusing to translate a code the reader already speaks.

Brevity does most of the remaining work, and it is worth being specific about why.

A character who explains themselves at length is a character the writer has not fully discovered, because a fully discovered character does not need to explain themselves. They know what they mean. They are not performing self-awareness for the reader's benefit. The long explanatory speech is almost always the writer working out what the character thinks, in real time, on the page, and forgetting to delete the working-out before the draft goes final.

The clipped exchange is the opposite. It assumes the character already knows what they think and is choosing, moment to moment, how much of it to reveal. This is a harder thing to write, because the writer has to know more than the dialogue shows. You cannot write a character economically withholding information you have not decided on. The discipline of brevity in dialogue is downstream of a discipline of clarity in the writer's own understanding of the scene.

Practically, this means most exchanges should run one to three lines per character before something interrupts, redirects, or ends the beat. A character delivering four consecutive sentences of uninterrupted dialogue is usually explaining, and explaining is the thing subtext exists to avoid. If a speech runs long, ask what it would look like cut into thirds. Interrupted twice, by the other character, by an action beat, by silence. The interruption is almost always more honest than the completion.

Action beats do more work here than dialogue tags. "She said, quietly" tells the reader how to hear a line. A towel folded twice, a glass set down harder than it needed to be, a door left open when it is usually closed, tells the reader the same thing without naming it, and lets the reader arrive at the feeling instead of being handed it.

There is a specific pleasure this produces in the reader, and it is worth naming because it explains why the technique is worth the extra difficulty of writing it.

When a reader decodes subtext correctly, they experience something close to the feeling of understanding a person in real life. Nobody tells them what the towel means. Nobody tells them the coffee is an evasion. The reader assembles the meaning from behavior, the way they assemble the meaning of an actual friend's evasiveness at an actual dinner table, and the assembly feels like insight rather than instruction. This is a more durable pleasure than being told what a scene means, because the reader did the interpretive work themselves, and people trust conclusions they arrive at more than conclusions handed to them.

This is also why direct dialogue reads as false even when it is technically accurate. A character who says exactly what she feels, in full, in the moment she feels it, is behaving in a way that almost no real person behaves. The reader's ear for human behavior, trained over a lifetime of actual conversation, registers the falseness even if the reader cannot articulate why. The clipped, evasive, off-topic exchange reads as true for the same reason a real conversation between two people who are avoiding something reads as true. It matches the shape of how people actually talk when the stakes are real.

None of this means dialogue should be cryptic for its own sake. There is a failure mode on the other side of this technique, where a writer withholds so much that the reader cannot construct any meaning at all, and the exchange reads as arbitrary rather than charged. The towel has to be a towel that means something, not a towel selected at random because a concrete object is an easy fallback. The deflection has to deflect from something specific, even if the specific thing is never named, because the reader's sense that something is being avoided depends on the writer knowing, precisely, what that something is.

The test is always the same one I use for the private document I keep behind every supernatural rule: does the writer know more than the page is saying? If the answer is yes, the withholding is disciplined, and the reader will feel the shape of what is missing. If the answer is no, the withholding is just an absence, and the reader will feel nothing at all, because there was nothing underneath the towel to begin with.

Write the whole conversation. Then take it away. What is left is the dialogue worth publishing.