A post by James Scott Bell at Kill Zone Blog: Dialogue Bloat
Which, in this case, means “As you know, Bob” dialogue. This post winds up with a delightful paragraph, which is why I’m sharing it with you. The post itself is brief, clear, and can be summed up as “Don’t do ‘As You Know, Bob’ dialogue.” Here’s the amusing last paragraph:
Great dialogue keeps readers in the fictive dream. Bloat pulls them out of it. So never have a character answer the door and say something like, “Oh, hello, Arthur, my family doctor from Baltimore. Thanks for coming to my home here on Mockingbird Lane.”
And I laughed.
However, as always, I think actual good advice in this realm is:
Write effective dialogue, and if you’re going to do “As you know, Bob,” dialogue, then do it effectively, because in fact this is not difficult. The above example is funny because it’s so wildly far from effective. So, how do you have one character explain something everyone knows, or at least his listener knows, effectively? I mean in a way that reads smoothly so that the reader doesn’t trip over the exposition, possibly doesn’t even notice the exposition? You can actually use the phrase “as you know” and the reader won’t think a thing of it. You do it like this:
A) I’m sorry, of course you know all this. I fear I’m a little fretful. = The character acknowledges that the person to whom he is speaking knows something and, bonus, provides an emotional cue that contributes both to characterization and to tension. At least as important — more important — this dialogue just doesn’t sound stiff, wooden, or fake.
B) I’m sure we all realize this, but let’s make sure we’re on the same page. = The character makes the same acknowledgment, hints that possibly he’s not sure we all do in fact realize this, or implies that he’s a belt-and-suspenders type who likes to dot i’s and cross t’s rather than taking the chance someone does not in fact know something. Also, this just sounds smooth rather than stiff or wooden — or it should, in the right context.
C) [Pedantic explanation here]. Another character: “Yes, yes, great, fine, I think we all know that, can we move on?” The author is being sneakier about providing information. The pedantic explanation has to be brief, or at least I think brevity generally helps in this sort of conversation.
D) As you know, Bob, [brief non-trivial explanation here].
The fact is, it’s not that hard to make “as you know’ sound smooth in dialogue. It doesn’t have to sound stupid. “That counts as usurpation, as you know,” means “as you know because you have a legal background so you’re the sort of person who does know things like this.” It doesn’t sound wrong to point this out as long as the person speaking has a reason to put this into words, such as setting this legal fact into the formal record of a legal proceeding, or making sure that other people listening also understand this legal fact.
Or, “As you know, she’s pregnant,” may mean, “I suspect you’ve forgotten this or might not have known it, but it wouldn’t be polite to suggest that possibility.” The Ugaro also specifically say, “As perhaps you may know” when providing information they suspect someone might not know, because it’s not polite to suggest someone might not know or might have forgotten some bit of information. “My name, as perhaps you may know, is Tano,” means “I’m not sure you actually caught my name, so just in case, I’m gracefully informing you.”
None of this is difficult, none of it sounds wrong, and actually that makes sense because people in the real world routinely explain things other people already know. Honestly, I think sentences such as, “Oh, hello, Arthur, my family doctor from Baltimore” or “As you know, Bob, the US has been at war with China for fifteen years” sound silly just because of straight-up inability to write good dialogue or to hear when dialogue sounds silly, stiff, wooden, or otherwise wrong — not because there’s anything intrinsically wrong with or difficult about saying “as you know” in dialogue.
Back to Bell’s post.
Bell points out how stiff and boring exposition is (or can be) when the author tries to pack it into dialogue. Or, one could turn that around and say: Dialogue often becomes stiff and boring when the author tries to use it mainly for exposition and forgets that dialogue should be doing other stuff at the same time. Dialogue should be used to provide characterization or drama or humor, and it’s most likely going to be boring boring boring if ALL it’s doing is providing information.
On the other hand, one of the examples Bell uses isn’t really failing for this exact reason, or I don’t think so. Take a look:
“Because if my son had died as a result of finding out about something terrible that had happened to him that I had kept hidden to protect him, I would want to blame the person responsible.” Kate thought she would try the empathy tactic. She did feel a great sorrow for Betty and her tragic story. She watched as Betty returned her statement with a hard stare.
What do you think? Bell thinks this long, fairly awkward sentence is delivering information. I think it’s just long and fairly awkward. Bell says it feels unnatural. I agree, it does feel unnatural, but I don’t think that’s because of information-stuffing, I just think it sounds stiff and unnatural.
How would you revise that line of dialogue? I’d break it up, not in a conversation — this is something Bell shows, and sure, that can work, but I’d break it up just by breaking it up. And I’d probably turn it inside out.
Well, I mean, if my own son found out I’d kept a secret from him — some terrible secret — something that had happened to him, but I’d never told him — if my son found out and killed himself, I’d never forgive whoever who told him.
This version makes extensive use of interruption and repetition. In fact, it’s using anacoluthon, a great word, which I had to look up again because I knew there was a word for this, but couldn’t remember it. Anacoluthon. I need to remember that. Regardless, is that better? It’s not shorter. It doesn’t contain less information. It contains an explosion of dashes, meaning I could care less that someone might fret that generated text may contain dashes. I would say this multiple-interruption version is not necessarily better; that depends on what the reader thinks “better” means here. I would say it’s more lively. Dashes, I might add, create liveliness. Or, at least, they can.
If someone told my son a terrible secret about his past and he killed himself, I’d absolutely blame them.
That’s much shorter and much more direct. It loses the idea that the mother deliberately hid the truth from her son. Is that a problem? I have no idea; that depends on the context.
Problems with the original: “something terrible that had happened to him that I had kept hidden” — I bet you mean “a secret.” There is no reason to use a long phrase to say “a secret” because we have a term for this concept.
“Had died” — do you mean “committed suicide,” because if that’s what you mean, say so. “My son had died” is passive, indirect, and leaves out essential information. Did he commit suicide? Say so. Was he murdered? Say so. Did something else happen? What? Be clear.
“as a result of finding out” — do you mean someone told him? Say so. Do you mean someone carelessly let it slip? Say so. Say what you mean, and try to say it more directly. That’s what I’d say, rather than saying, “You’re trying to deliver too much information in this sentence,” because I think indirectness and passiveness are obscuring the information. I think obscurity is the problem, not information overload.
Personally, I’d also move the tags around. I’d be inclined to put Kate’s intention in the front, before she opens her mouth. Intention first, then speech, then reflection on what she just said, then Betty’s response. I’m thinking too much about this, probably. Bell says he suggested to the author who wrote the above sentences, try cutting everything from the dialogue that isn’t necessary, plus everything that’s not true to the emotional beats. More important, he asked her to consider What would either of them really say?
That, I think, is actually the key. Even though dialogue isn’t supposed to be realistic, it’s supposed to feel realistic. What would people really say? If they wouldn’t really say that, then possibly the dialogue is too wooden. If the dialogue isn’t realistic, that should be because the dialogue showcases more wit, humor, liveliness, or meaning than is typical in actual no-kidding real dialogue. It surely helps if the author hears it internally. It’s hard for me to imagine writing dialogue if you don’t hear it.
Regardless, dialogue is very important for me as a reader. I have seen novels that succeed despite wooden dialogue and wooden characterization — which I think go hand in hand — and conversely, I’ve seen novels that succeed despite silly plotting because the dialogue is especially lively. It’s almost always worth focusing on dialogue — on liveliness of dialogue — on making sure dialogue is doing more than one thing.
Things dialogue can and should do: provide information; deepen characterization and contribute to voice; clarify, deepen, and move relationships; provide humor and delight the reader. I think discussions of what dialogue is for tend to leave out that final item, but I personally think advice to cut unnecessary dialogue can lead to authors tending to devalue bits of dialogue if the main function of those bits involve wit, humor, or delight — but all of those aspects of dialogue are in fact wonderful, lively, and well worth keeping.
And honestly, it’s not hard to use ‘as you know’ in dialogue without the reader ever thinking about Bob.
The post Bloated dialogue appeared first on Rachel Neumeier.













