Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Vague vs Specific: When to provide motivation details for action in a story?

+0
−0

I'm reading Wired for Story, by Lisa Cron, where she writes the following about being vague or omitting information that the reader does not know:

...being vague is never a good idea...

...Like most things, it can start off so promisingly: “Holly ducked into the alley, glad to have avoided Sam for the millionth time.” Sounds great, right? Trouble is, unless we know at that moment in the story why Holly has been avoiding Sam, it will fall flat.

Cron, Lisa. Wired for Story (p. 112). Potter/Ten Speed/Harmony/Rodale. Kindle Edition.

Is her thesis about vague vs. specific valid at all times? Based on her example above, what if the author intends to reveal why Holly is avoiding Sam later on? For instance, later on, we find that Holly has stolen Sam's collectible lunch box.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

This post was sourced from https://writers.stackexchange.com/q/44336. It is licensed under CC BY-SA 3.0.

0 comment threads

1 answer

+0
−0

Being vague is usually a bad idea, particularly early in the story. In the example, it doesn't make a difference what the author is planning or intends, all that matters is what the reader reads. If all you get is that Holly is avoiding Sam, yes, it does fall flat for the reader. They can't sympathize with Holly, or Sam, so the reading was a waste of time.

In writing you need the reader to identify with the characters in some way, or more generally the reader is ready to like the characters, particularly the Main Character, and you should make them want to follow the MC for the length of the book.

You do this by letting the reader in, on the thoughts and feelings of the MC, and that means you can't keep secrets about why they are doing what they are doing. In the same way you can't be vague about it. (Some authors do get away with it, but this doesn't make it good writing.)

In Third Person Limited (the narrator only knows the thoughts and feelings of the MC) you can have other characters keep secrets that your MC doesn't know, or doesn't even realize exist. Holly's best friend might be hiding something important, and Holly doesn't even realize it.

But don't be vague about the MC. Or, for that matter, about the setting or other descriptions. It is permissible to not describe things that don't matter -- a store can just be a store, a dirt path in the woods doesn't need a lot said about it, even the description of a character may be omitted altogether or require barely a sentence -- but if you choose to describe something because it is important, try to be specific and concrete. a "forty foot pine" is more concrete than "a tall tree".

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »