• strict warning: Declaration of FeedsImporter::copy() should be compatible with FeedsConfigurable::copy(FeedsConfigurable $configurable) in /home/writezil/public_html/sites/all/modules/feeds/includes/FeedsImporter.inc on line 94.
  • strict warning: Declaration of FeedsNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsNodeProcessor.inc on line 319.
  • strict warning: Declaration of FeedsFeedNodeProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsFeedNodeProcessor::setTargetElement() should be compatible with FeedsProcessor::setTargetElement(&$target_item, $target_element, $value) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsFeedNodeProcessor.inc on line 227.
  • strict warning: Declaration of FeedsUserProcessor::map() should be compatible with FeedsProcessor::map($source_item, $target_item = NULL) in /home/writezil/public_html/sites/all/modules/feeds/plugins/FeedsUserProcessor.inc on line 195.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • warning: preg_replace(): Compilation failed: disallowed Unicode code point (>= 0xd800 && <= 0xdfff) at offset 1809 in /home/writezil/public_html/modules/search/search.module on line 334.
  • You must include at least one positive keyword with 3 characters or more.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_plugin_display::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display.inc on line 1877.
  • strict warning: Declaration of views_plugin_display_block::options_submit() should be compatible with views_plugin_display::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_display_block.inc on line 193.
  • strict warning: Declaration of views_handler_field_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_field.inc on line 641.
  • strict warning: Declaration of views_handler_sort_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_sort.inc on line 82.
  • strict warning: Declaration of views_handler_filter::options_validate() should be compatible with views_handler::options_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter::options_submit() should be compatible with views_handler::options_submit($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 585.
  • strict warning: Declaration of views_handler_filter_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter.inc on line 609.
  • strict warning: Declaration of views_handler_filter_boolean_operator::value_validate() should be compatible with views_handler_filter::value_validate($form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_filter_boolean_operator.inc on line 128.
  • strict warning: Declaration of views_plugin_style_default::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_style_default.inc on line 25.
  • strict warning: Declaration of views_plugin_row::options_validate() should be compatible with views_plugin::options_validate(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Declaration of views_plugin_row::options_submit() should be compatible with views_plugin::options_submit(&$form, &$form_state) in /home/writezil/public_html/sites/all/modules/views/plugins/views_plugin_row.inc on line 135.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of content_handler_field::options() should be compatible with views_object::options() in /home/writezil/public_html/sites/all/modules/cck/includes/views/handlers/content_handler_field.inc on line 208.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Non-static method view::load() should not be called statically in /home/writezil/public_html/sites/all/modules/views/views.module on line 843.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 745.
  • strict warning: Declaration of views_handler_argument_broken::ui_name() should be compatible with views_handler::ui_name($short = false) in /home/writezil/public_html/sites/all/modules/views/handlers/views_handler_argument.inc on line 770.

Wait, What?

https://i2.wp.com/writerunboxed.com/wp-content/uploads/2018/09/escher.jp... 416w" sizes="(max-width: 351px) 100vw, 351px" data-recalc-dims="1" />Last May, the opening scene I edited raised a lot of questions – about the characters, their relationships, their backstory – without answering them right away. Of course, no opening scene can tell you everything at once, but this one put questions out there and then moved on, leaving readers hanging.  This led one commentator to ask about ambiguity and what to do about it.
A quick survey of writing about writing shows that most of the advice you get on ambiguity is on how to get rid of it.  I’m not so sure this is wise.  Ambiguity can often be a powerful storytelling tool.
Understand, I’m not talking about misdirection, where your readers think they know what’s going on but eventually discover that you’ve been misleading them.  And I’m not talking about clear plot questions that readers don’t yet know the answer to – “whodunit” is not a matter of ambiguity.  I’m talking about the kind of scenes were readers have no idea what the scene means or why it’s in the book, and the writer knows that readers will feel that way.
You often have no choice but to include some ambiguity in your opening scene, especially if you’ve created a complex world or characters with full, interesting histories.  The alternative is to try to convey all that background before the story begins—and weigh down your hook with a lot of exposition.  It’s usually much better to simply trust that your readers will keep reading even if they don’t understand everything that’s going on.
Last February, we looked at a YA story set in Ghana, in which the narrator’s mother cooked a chicken that the narrator had considered a pet.  One comment raised the question of why the mother did this.  I pointed out that the rest of the village also seemed to be involved in the meal, which meant that the mother’s motives probably involved a skein of social obligations that western readers wouldn’t understand without a lot of explanation.  But getting into the weeds of the mother’s decision at that moment would have drawn attention away from the narrator’s reaction to losing her chicken, which was the emotional core of the scene.  The author had little choice but to leave the mother’s motives up in the air for the time being.
In trying to avoid this kind of thing, writers often choose an opening scene that is entirely self-contained and clear.  And this can sometimes work.  But it often means avoiding what’s most interesting about your world in your opener, since the things that make your world unique are also the things that make it engaging.  Besides, you can often draw readers into your story if you leave them wondering just a bit about what’s going on.  This is particularly true in science fiction and fantasy, where readers don’t expect to understand everything right away, or in spy thrillers, where readers expect that things won’t make sense until all is revealed.
In fact, it’s often possible to use ambiguity as a source of tension throughout an entire novel, leading readers to want to read through to the end just to understand what’s going on.  There’s some risk to this approach, since you are generating tension from how your story is structured rather than the things that are happening to your characters.  This kind of meta-tension can remind your readers that they’re reading a book.  But if your story is strong enough in other ways, readers are willing to forgive you the manipulation, since they know the payoff will be worth it.  (Note: my editor-wife, a voracious reader, disputes this point – she always resents the manipulation.  So this technique won’t work for all readers.)  Threading together all of the various enigmatic scenes into a coherent whole is one of the things (in addition to characters who are in constant peril for their lives) that drives Dan Brown readers through to the end.  (Ruth notes there’s a reason she’s only read one Dan Brown novel.)
“Story of Your Life,” the Ted Chang novella that was the basis for the movie “Arrival,” opens with a woman, Louise, telling her daughter the story of her life.  [SPOILERS]  The scenes of Louise and her daughter are then interspersed through the narrative of how Louise, a linguist, was recruited to translate the language of aliens who have just arrived on earth.  Readers have no idea what the story of her daughter — whom, we learn, dies young of cancer — has to do with unraveling the language of the floating, seven-footed octopus-like creatures.  I know I kept waiting for her grief about her daughter to change how she felt about the aliens.
It’s not until the final few scenes that the two threads of the story come together and make sense. The aliens don’t perceive time sequentially – they are aware of everything that happens, all at once.  As Louise becomes fluent in their language, she also begins to detach from time, remembering things that have not yet happened.  And in the last couple of paragraphs, we learn that one of these things is the life and death of her daughter.  What we thought were memories are in fact memories of events that haven’t occurred yet.
The reason this risky approach works is that Chang delivers enough other interesting elements that readers are willing to put up with not knowing the meaning of what they’re reading.  Louise is wonderfully sympathetic, and her daughter is a delight.  And the description of the situation with the aliens and the fight to penetrate their language makes it clear that readers are in the hands of a gifted storyteller.  All of this make them more willing to suspend understanding.
 
Of course, it’s possible to go overboard with this approach.  I’m currently working on a story told primarily from the point of view of a psychologically disturbed teenager, raised by a mother who is literally insane.  The daughter is not really aware of her mother’s madness and takes her homelife as normal – hence the psychological disturbance.  In the first draft, the author tried to capture the young girl’s skewed consciousness through a series of ambiguous scenes, colored by the girl’s confusion about her life and her mother’s pathology.  But these scenes were so ambiguous – it was often hard to tell whether something actually happened or was a hallucination – that the story was impossible to follow.  Readers not only didn’t understand what events meant.  They didn’t understand what the events were.  Readers will not put up with that for very long.
 
In the end, creating tension with ambiguity is pretty advanced storytelling.  To use it effectively, you have to be tuned in to how your writing comes across to your readers.  That’s the only way to confuse them just enough to keep them intrigued without driving them away.  You also need to give your readers reason to put up with not being able to follow everything that’s going on.  But working on your side, you’ve got the human need to make sense of things.  That need is one of the reasons we tell stories in the first place.
 

Wish you could buy this author a cup of joe?

Now, thanks to tinyCoffee and PayPal, you can!

 

 

About Dave KingDave King is the co-author of Self-Editing for Fiction Writers, a best-seller among writing books. An independent editor since 1987, he is also a former contributing editor at Writer's Digest. Many of his magazine pieces on the art of writing have been anthologized in The Complete Handbook of Novel Writing and in The Writer's Digest Writing Clinic. You can check out several of his articles and get other writing tips on his website.Web | Facebook | More Posts

"Living gives you a better understanding of life. I would hope that my characters have become deeper and more rounded personalities. Wider travels have given me considerably greater insight into how cultural differences affect not only people, but politics and art."
Alan Dean Foster

Random picks

  • Distributing very useful information in the World Wide Web is proven to be the most effective way to capture the attention of online users
  • Most of us think, writing a novel, that's got to be tough work! Just look at the size of those things. Certainly, I can write; I enjoy writing; I've written a ton of documentation for this or that; I've got down rhetoric, but a novel? I've study adequate of them. I know what they're about, that's, that they're stories, and, yes, I've got a few stories of my personal, but writing a novel? What does it take, I mean, what are the difficulties? Where do you begin? What do you require?
  • Interview: Benjamin Anastas, Author of Too Good to Be TrueToo Good to Be True" title="ben-anastas-200-2" width="200" height="267" class="alignright size-full wp-image-10412" />Benjamin Anastas has published two well-regarded novels: An Underachiever’s Diary in 1998 and The Faithful Narrative of a Pastor’s Disappearance in 2001. He then went through a kind of rough patch, and his new tome, Too Good to Be True, accounts for that time. While one is tempted to dismiss Anastas’s travails as being commonplace, it does call one to consider George Orwell’s insight that everyone’s...
  • Alabama didn\’t so much win their game against Tennessee on Saturday as much as they escaped. Despite playing one of their worst games of the year they managed to keep their undefeated season alive as nose tackle Terrance Cody blocked a potential game winning field goal on the last play of the game to preserve a 12-10 victory for the Crimson Tide. Alabama held a tenuous 12-3 lead late in the game before a Tennessee touchdown and recovered onside kick had them facing the specter of the defeat for the first time this season. College football pointspread players who took Tennessee as +14...
  • General info Index of all the 2009 NaNoWriMo cartoons so far. Follow @inkyelbows on Twitter for writing info & cartoons. Feel free to add me as a NaNoWriMo buddy.

Recommended sites

Most recent titles

Fast fact about writing

Writing is a distinctly human activity.