Showing posts with label craft. Show all posts
Showing posts with label craft. Show all posts

Wednesday, October 9, 2013

Some Thoughts on First Lines


We hear all the time how important first lines are in hooking a reader’s attention. First lines must provoke curiosity, create anticipation, and move seamlessly into the sentences that follow. That’s not what I want to focus on today, but if you’re interested in the elements of good first lines, check out the following posts:


Instead, I’m more interested in what the “right” first line gives to the writer.

by sippakorn of freedigitalphotos.net
Recently I found myself having trouble digging in to a short story I’ve been trying to write. I have a premise, characters, conflict, and even a rough idea for the plot. Sounds like I should be having no problem writing the story, right? Wrong.

I’ve started and stopped working on the story over the past few months, picking it up only to set it back down again. For a while, I thought my troubles in executing were because I hadn’t let the story simmer in my mind long enough.

Then I realized the real reason. My opening scene—particularly my opening line—wasn’t strong enough to hang the rest of the story on.

In the drafting stage, I don’t care about hooking readers. My only concern is getting to “the end”. And while I know what the shape of this story should be, my starting point is very fuzzy. Hence my troubles.

Starting points are a fundamental aspect of the architecture of a story. Everything that comes after the beginning cannot exist in the reader’s mind without the context the start of the story creates. Similarly, as a writer, each sentence I write affects the trajectory of the story. Where I choose to begin can have huge ramifications on what follows.

Even though I’d say 90% of the time I rewrite my first lines, I still need one—regardless of how imperfect—to help me write my story.

So what makes for a strong first line that facilitates the writer’s drafting process?
  • It should give you an organizational framework that dictates how you tell the story.
  • It should pose a question that you as a writer want to answer.
  • It must keep you writing.
Have you ever gotten stuck on your first line at the drafting phase? How did it affect your process? And how did you get unstuck?

Wednesday, July 24, 2013

The Art of Layering in Our Fragmentary World


Infodumps are evil. Readers hit them, and their eyes glaze over. We’re lucky if they skip over them and keep going. Unlucky if they decide then and there to set the story or book aside.

We writers know infodumps are bad even if we can’t always avoid them in actual practice. Most advice tells us to break up the details and pepper them in the best we can.

Which is a helpful, but I’d argue an incomplete suggestion.

I’ve talked before about my writing process, and how my stories often begin as a skeletal first draft of dialogue and action, then I have to layer in everything else. In this case, layer refers to the iterative passes where I add in setting detail, character blocking, internal thoughts, and other expository “flesh” to the story.

Picture Source

Today I want to focus on the layering in of specific types of information: Description and Backstory.

But first, a digression (because it’s my blog and I can do what I want). Readers have a choice in how they spend their time. Books are in competition with video games, TV and movies, the black hole that is the internet, on top of demands of work and family. This isn’t new. With advances in technology and changes in how people spend their free time, people’s attention spans become increasingly fragmentary.

I have to wonder if this is related to readers’ intolerance with infodumps. They don’t have the patience to wade through them when in the back of their mind, they’re wondering why they’re wasting their time on a boring book when they could be doing X, Y, or Z…

In other words, you need to make your book worth the opportunity cost of other activities.

And that means conveying information in an entertaining way (however defined) all the time. So. Back to layering in details. We’re told to break them up and add them in as necessary, but it should go further than that. Here’s what I strive to do with my words, but your mileage may vary.

Description

Lush description can be wonderful, but so often, such passages have no movement, no underlying action, no impetus forward. It’s a hard balance to strike: having enough detail the reader can visualize your world, but not so much it slows down pacing.

Don’t explain/describe everything at once—Readers can tolerate a certain amount of uncertainty and that can even be a driving motivation to keep them reading. Just be careful to not have too much uncertainty because then curiosity will morph into frustration (and frustration means no more reading).

Readers are on a need-to-know basis—Some grounding details are necessary, but don’t overwhelm or bore them with things that aren’t quite important yet. Granted, there are things you’ll want to sow in to foreshadow or set up subsequent scenes, but you want to strive for natural inclusion, else those details will draw attention to themselves.

Rely on archetypes—Think of these as writerly shorthand. Use them when you want to get across a basic concept: Tree, house, cow, [insert your own noun here]. Most readers will have a mental image of these concepts in their brain. The key is to prime the reader by relying on that mental image, then gradually introducing details that confirm or disrupt that image as you move from a universal concept to a more specific one.

Think telling details—These are details that are evocative and appropriate and important for describing something accurately or setting the tone or establishing voice. But don’t waste words (and your reader’s time) on the obvious. Let the archetype do the heavy lifting, and include telling details as necessary. And sometimes, a tree is just a tree.

Backstory

Also something you’re better off peppering in as needed, this one is particularly insidious for writers because they spend so much time trying to figure out who their characters are and how they came to be that way, that it’s hard for them to decide what is and is not relevant for the reader.

So how do you determine what’s relevant? When the information:

Is key to understanding a character’s reaction/state-of-mind/worldview—This helps the reader identify where a character is coming from and may help to explain why they react in the way they do in the story. A character who has a history of abuse will probably react differently than a character who doesn’t, for example. Think of this type of information as an extension of character development. But extension is an important distinction—character development should be grounded in the story itself, the backstory just provides occasional context. 

Disrupts a character or reader’s assumptions for dramatic effect—Remember telling details? Backstory can function in the same manner, either confirming or clarifying character, or disrupting expectations for a dramatic twist. Look at the way JK Rowling handles Snape’s character in the Harry Potter series for how the judicious application of backstory can be used to increase tension, conflict, drama, and, interestingly, catharsis.

Obviously the worst thing a writer can do is bring a story to a screeching halt in order to convey whatever details are needed. But almost always the reader doesn’t need as much as the author thinks they do to understand what is going on. (This is where trusted readers are worth their weight in gold.)

Character archetypes can also come in handy here (hooker with the heart of gold, sad sack detective, fresh faced apprentice on hero’s journey, etc.) to help the reader tap into unconscious understanding of character—just don’t forget to round them out so they become more than just a caricature as you move from universal archetypes to specific characters only you can create.

***
So remember, less is almost always more, unless it confuses the reader. Strive for clarity above all, and to a lesser extent, Donald Maas’s microtension—those unexpected but revealing details that describe your story world or provide a provocative hint at your character’s past. Such details create curiosity in your reader and serve as minihooks to help your story compete in a media-rich and fragmentary world.

Happy writing!

Wednesday, July 10, 2013

Being Clever versus Being a Good Storyteller


Over the weekend I went to a reading for a local speculative fiction author. In the course of his talk, he said something that resonated with me.

That with his first book series, he was trying very hard to be Clever and write Very Important Stories. But now, a few books later, he’s focused on good storytelling, no matter the milieu he’s working in (I’m paraphrasing here).

I found this to be an interesting distinction he made, and it echoed some of my internal (but not quite fully formed) thoughts about my own work and what I need to be focusing on if I want a career in this field.

Case in point: One of my short stories that I have been submitting since early 2012 has been shortlisted or bumped to the second round at SIX pro or semipro markets. But it still hasn’t found a home, and I have to ask myself why. I’ve settled on the fact that it is my “cleverest” story, given its subject matter. It asks a lot of the reader at the beginning, but it also rewards you once you get to the end. (Yeah, that kind of story.)


The first couple of times it was shortlisted, I chose to be encouraged, thinking I just haven’t found the right market. But after six (six!) times being a bridesmaid, well, I think it’s time to reevaluate things.

Perhaps I’m a little too in love with my cleverness, and as a result, I’ve forgotten the number one reason for writing a story for publication…. Readers.

I’m not saying cleverness is a bad thing. Instead it’s a matter of emphasis.

Putting story and the reader experience first does not mean you can’t also be clever. In fact, being clever in that context can be an amazing thing.

But the flip side? When being clever is your primary goal, sometimes to the exclusion of all else? That’s where you tend to lose people. (A semi-related aspect of this is when beautiful writing overwhelms a story to its detriment—see the recent article Literary Talent versus Story Talent.)

I think this is a particular problem in SF/F because Ideas! and Science! are often an integral part of the story. A nifty idea can make up for a lot of sins in craft, character development, and plot. Almost to the point where that nifty idea becomes a crutch.

My story has a nifty idea, and it also commits a few sins of good storytelling. And that combination has netted me a whole lot of close-but-no-cigars. So where do I go from here? I’ve got to figure out a way to present my nifty idea within the context of good storytelling.

That can be a hard gulf to bridge for any writer, beginning or seasoned. But letting the story rest and getting some new eyes on it will go a long way. At least I’m hoping so.

Warning signs your “cleverness” is getting in the way of your story:

  • Focusing on your “nifty idea” to the detriment of other story elements.
  • Reader feedback saying they didn’t understand aspects of your story.
  • Infodumps that are necessary to explain things to unenlightened readers.
  • Telling yourself the above is okay because you’re writing for a select/smart/in-the-know audience which consists of you and maybe five other people.

Have you ever been guilty of letting your ideas take over your story?

Wednesday, May 29, 2013

Invisibility of Progress

Improvements in writing ability are often hard to detect. So much of what is “good” is contextual—dictated by a particular project, the audience you’re writing for, or even market trends.

I’ve talked before about How Do You Know if you are ready for publication. Although it’s related, that’s not exactly what I want to talk about today.

Instead I want to focus on all the invisible things writers do in the hopes of bettering their craft, expanding their professional network, and positioning themselves for success to the best of their ability.

Image courtesy of Penywise of Morgue Files

Objective measures of success in this field are pretty self-explanatory. You’re either published or you're not (however you choose to define it). When you’re “not” published, chances are you’re doing a bunch of things other than writing in the hopes they will pay off in some small way in the future.

For example, I haven’t sold any short stories since last fall. If you are looking at my output objectively—well, there isn’t any by that definition. Instead, so much of what I’m doing these days is invisible. And I’m still trying to figure out what that means.

These invisible activities include:

Reading slush for Masque Books – Beyond occasional mentions here on the blog, it’s something I do to strengthen my ability to evaluate projects, diagnose writing problems, and gain insights into the editorial process. I won’t be able to learn these things overnight—this requires a commitment of months if not years to see the benefit from this type of activity.

Joining an invitation-only critique group – The meetings are intense and panic-inducing. I’m learning tons, making good connections, but as with any critique group, feedback is only as good as the projects I bring to them. Workshopping novels (and short stories to a lesser extent) can be a long process outside of development time.

Submitting to higher-tier markets – I have three in rotation right now that I truly believe in. And I’ve been aiming high. My sales last year gave me the confidence to target higher-tier markets. Personal rejections? Check. Second-round bumps? Check. Agonizing ‘You just missed the cut’ notices? Oh yeah. And the worst part is, all this means longer response times.

When non-writers ask me about my writing these days, it’s hard to explain how all these invisible activities fill up my time and contribute to my work. But they do mean something. They are valuable. They just go largely unseen because they don’t conform to objective measures of success.

I just have to believe they’ll add up to something that cannot be ignored one day.

What aspect of your writing life is invisible?

Wednesday, May 8, 2013

Feedback, But When?


Feedback is an essential part of the creative process. Well, at least mine! How else will you know if your intentions match up with the reception of your work? Today, I’ll talk about the different stages of a project where it might be appropriate to solicit feedback.


In-Progress Feedback

In one of my writing groups, the work I share is almost always a work-in-progress. It’s literate, but it’s usually a snippet from a novel or a short story that still needs some fleshing out. In this case, I’m actively looking to my other group members for assistance in how to flesh the story out, what I’ve overlooked, and ultimately whether I’m on the right track or not. Just realize not every writing group is geared to workshopping this kind of early stage writing. 

Best critiquers at this stage: Critical thinkers, other writers.

Developmental Feedback

I’d call this feedback on anything that’s been drafted and fleshed out, but hasn’t fully cured in a version you are confident in submitting somewhere. In other words, you’ve gotten to the end, but the ride is still a bit bumpy (not in a good way). Here, I’m looking for macro-level adjustments (micro is good too) that I can make so the story can gel into a finalized draft. At this stage, I want people who understand the big picture but also the aspects of craft that will help me realize it all on the page. 

Best critiquers at this stage: Other writers, particularly those writing in your genre.

Polished Feedback

This is feedback on a polished draft that you think is the best it can be. You know, all those checklists when you’re trying to decide if you’re ready to submit or not? If your answer is yes, it’s still a good idea to get another person (or persons!) to take a look. You might burn a few weeks only to get your readers’ blessing to send it out, but it’s better to know you are sending out your best work than being surprised by some issue that was overlooked at other stages. And when you only have one shot with agents, you want everything to be as good as it can be. 

Best critiquers at this stage: Readers of your genre, other writers.

Public Reception

So let’s say your story/novel/what-have-you got published. Yay! At this stage, there’s still a couple metrics you can use to see how your work is received and ways to use its reception and apply it to your next story. Obviously things like sales figures are important. But so are reviews. I’m not talking about the reviews your mom/critique partner/best friend wrote. I’m talking about the reviews written by strangers who have no personal investment in you or your story.

Seth Godin says the worst feedback is indifference. Some stories and novels get published, and just as quickly vanish into the ether. Now some of this can be attributed to poor marketing and positioning, and sometimes a story just doesn’t have the impact it should. And sometimes, you are lucky enough to get reviews that help you to understand what worked and what didn’t in your story. Elizabeth Spann Craig talks about this in Handling Reviews from Mystery Writing is Murder. Give yourself time for the sting to wear off, but even bad reviews can be instructive (so long as it's not coming from someone with an ax to grind).

One of my published stories was not received in the manner I had hoped for, and I learned a lot from seeing those reviews of my work. It forced me to analyze my assumptions in writing that particular story as well as my assumptions in who the story's audience was, and so on. Despite the short-term disappointment in that story’s reception, that was a hugely valuable experience, and one that will shape my work to come.

***

So obviously, you need feedback, and at what point you solicit it and from whom will be dependent on your writerly network and your own needs and comfort level with the critique process.

Personally, I try to get feedback at each stage of a project, if possible. In my goal to write faster, I’ve found that In-Progress Feedback is extremely helpful for heading off mistakes in a story that would need significant retooling if they were found much later in the process. However, for that to be successful, I think you need to be:

1)     very used to critique and,
2)     very clear in your own head with what you’re trying to achieve with your work.

Especially because rogue comments can easily affect the trajectory of a story and your confidence in it at the early stage of a project. It should also be said that if you’re sharing early work, you are sharing it with writers who:

1)     you trust
2)     understand that it’s an early draft, and
3)     can provide constructive criticism (not all critiquers are alike in this)

Your mileage may vary, of course. But I’ve found this work for me.

Happy writing (and critiquing)!

Monday, April 22, 2013

Deliberate Choices -- Guest Post with L. Blankenship

Today, I'm pleased to host fantasy author L. Blankenship on the blog today. You may recall in my interview with her last fall, that she has two (!) successful Kickstarters under her belt, and Part II of her hard fantasy romance Disciple is now available. If you love adventure and romance in a fully textured world with realistic characters, look no further. And be sure check out below for links to a Goodreads giveaway!



Deliberate Choices by L. Blankenship
I did make some deliberate choices, in writing Disciple, about the kind of story I wanted to write. I'm of the opinion that plot, character, and world-building are tightly linked and should be allowed to grow organically -- but I did put a few restrictions on that growth.

Some look like simple things, like not wanting to use the tag "s/he thought" on a thought. Or "I thought," in my first-person narrator's case. It's just so clunkily obvious, or ought to be, that I committed to not using it at all.

Which sounds simple, but I found myself rewriting a lot of sentences before the habit settled in.

There was something deeper I wanted to do, in Disciple: I wanted a good, solid fight. It seems to me that many fantasy stories go to great lengths to stack the deck against the protagonists. They're poor, they're helpless, they're emotionally damaged, they're completely unprepared for the challenges they face. It's Bambi vs. Godzilla.

It's meant to ramp up the tension. It's meant to make the eventual success -- and whatever losses along the way -- all the more savory.

I wanted to see competent, well prepared protagonists go into a tough fight, take hard losses, get their asses kicked a couple times, and claw their way to winning. There seem to be plenty of stories about finding that Magic Thingy or tapping the Cosmic Can of Whup-ass to help Bambi beat Godzilla. Why write another one?

I wanted this to be a fair fight because evenly matched opponents make for an interesting game. I'm not much of a sports fan, but I know the Superbowl isn't much fun when one team dominates the other from the first kickoff. The games you stick around for are the ones that teeter back and forth to the final minutes.

So both sides of the war, in Disciple, came in with stacked decks. They'd made strategic choices, ahead of time, because war was inevitable and they'd be idiots to not prepare to the hilt. Both sides take risks. Both sides take losses. When I sat down to write Disciple, Part VI and finish the story, I wasn't sure exactly how the last few minutes of the Superbowl would play out. 

Which sure held my interest.

Back cover of Disciple, Part II

The prince first kissed Kate Carpenter for fear of missing the chance if they didn’t survive the journey home through the monster-prowled mountains.

Now that kiss seems like a fever dream. It’s back to work for her, back to the fellow physicians jealous of her talents and the sneers of an infirmary director who wants her shipped off to some tiny village. Kate means to be on the front lines to save lives. She’s worked too hard to overcome her past to let them deny her the chance to serve her homeland when the enemy’s army reaches their kingdom.

The grand jousting tournament is a chance to prove she can manage combat wounded, and at the royal Solstice banquet Kate means to prove she isn’t an ignorant peasant girl anymore.

But the prince’s kiss still haunts her. Their paths keep crossing, and the easy familiarity they earned on the journey home is a welcome escape from their duties. It’s a small slip from chatting to kisses.

This is no time to be distracted by romance -- a vast and powerful empire is coming to slaughter anyone standing between them and the kingdom’s magical fount.

Kate ought to break both their hearts, for duty’s sake.

Disciple, Part II on sale now
along with Disciple, Part I


Disciple, Part III coming in late 2013
Disciple is complete in six parts and will make a lovely doorstop
when all 400k words have been published.

Goodreads links:

 

Wednesday, April 17, 2013

The Pros of Professional Development


While the blogosphere is a fantastic resource—rife with informative posts on craft, publishing, and other aspects of the writing life—it can get overwhelming and, at times, repetitive. Not that repetition can’t be helpful in crystallizing some aspects of craft. But too much, and my brain starts saying I’ve heard this before and I tune out.

When that happens, the act of learning, of actively improving, becomes passive. For this writer, that means I start to feel complacent. Not a good place to be.

I had been feeling this way recently—after all it’s been just under a year since I attended Taos Toolbox—so when I saw my local SCBWI chapter was hosting a NY agent for an all-day workshop, I signed up, hoping to be reinvigorated.


I was nervous as I always am when owning my writer persona in an unfamiliar environment with (gasp!) strangers. For the morning session, the agent presented an overview of essential craft elements for children’s books. Then the afternoon was all about the business side of things. It was a very informative session, and unfortunately I signed a waiver that doesn’t let me get any more specific than that.

The workshop would haven been tremendously helpful for me a year or three ago. As it was, I’d say didn’t learn anything “new.” Instead, I learned the relative importance this agent placed on different aspects of craft and business. Much of the content I had been exposed to before, though not as systematically all at once. Hand in hand with the workshop, I paid for an optional critique that didn’t uncover any fatal deficiencies in my writing. So at this point you may be wondering what I actually got out of a wasted Saturday and a c-note.

1. It’s Worth Checking In Sometimes


It is entirely possible to reach a point with your craft where you simply don’t need all the handholding you once did to stay productive. The writing is going well, you’re in the zone, this one’s going to sell, and so on. And that’s all great. But when you’re holed up in your cave, sometimes you can lose sight of what your writing really needs.

By attending a workshop like I did or engaging in some form of professional development to put you and your work out there, you have the opportunity to evaluate your writing through someone else’s eyes. On the business side of things, the publishing world is changing so rapidly every day, you can’t afford to not pay attention to opportunities to help put all the changes into perspective.

2. Don’t Underestimate the Value of Knowing You’re On the Right Track


You remember that critique I got? It let me know my opening for a new project was on the right track. That is invaluable. Looking back at where I was with past projects and knowing they wouldn’t have received this kind of feedback at this stage, shows just how much I’ve improved. Doesn’t mean it’s perfect, doesn’t mean there aren’t things I can do to strengthen my story. But it’s now a question of calibration, not wholesale revision. And that’s a huge difference (and a huge confidence boost).

3. Professional Organizations Provide Superior Opportunities


Now, this assertion is grounded in my personal experience. I’ve tried a lot of different things, including:

-Local, grassroots style writing groups like those you find through Meetup.com or your local alt-weekly. You can find some good individuals, but too often the group includes people who don’t know what they’re doing or have a different focus (say self-publishing when you have your eye on the Big 6).

-Classes at the local community college or university. Again, you might find some serious individuals, but many of these people are just testing the waters and haven’t screwed up the courage to take the plunge. The teachers at this level can also be suspect in their ability to teach or inspire. Note, I am not talking about MFA programs and the like.

-Regionally-focused writing organizations. The ones near you may be different, but the one closest to me serves as a catch-all for writers not represented by other organizations. Mine has a lot of writers writing memoir and literary fiction, and their classes and workshops cater to hobbyists and beginners.

-Residential workshops like Taos Toolbox. Expensive, but being surrounded by a dedicated group of peers, and being instructed by individuals who have lived through publishing’s ups and downs is priceless.

-Local chapters of national writers groups like RWA or SCBWI. These organizations are far more likely to have classes and workshops for the intermediate and seasoned writer.

I can say with absolute certainty that you get folks who are a lot more serious about learning their craft at organizations and workshops with a targeted focus like genre. Not one of the thirty people in the workshop I attended had stars in their eyes that they’d be the next JK Rowling. Everyone was aware of the years of hard work and the smart choices it takes to succeed in publishing.

Now, I’ve held off joining any of the membership organizations. Partly because it’s another cost in a field with too little money for writers as it is. Partly because I was a little too in love with the idea of the “lone writer” for a long time. And partly because I felt I had to “prove” myself in a genre before I could presume to join an organization dedicated to it. Imposter syndrome, much?

But now? I’m in a place where I’m reasonably confident in my abilities as a writer. I’m also very cognizant of what I don’t know as I contemplate what’s next for me. That’s where the support of a national organization becomes invaluable. I’m still debating which one is best for my career long term, but I can no longer ignore the benefits they can provide.

What about you? Have you had a recent professional development experience? How did it go?

Happy writing!

Wednesday, February 6, 2013

Collaborative Writing

Over the last few months, I’ve participated in a collaborative writing project with two of my writing friends.

It’s something I was initially hesitant doing. For one, the project is in a genre I don’t normally write in. For another, I wasn’t confident our writing styles would mesh. Plus, the time I spent on the project would inevitably take time away from my own work.

But I did it anyway, and as we’re polishing the initial draft, I can say it was largely a success. How did we keep it from devolving into a game of tug-of war?


Well, for starters, my emotional investment in this project was much lower to begin with. After all, I had to share this story with two other people. So my level of engagement was more in line with the collaborative writing I did in academia—I had a professional desire to get things done and do them well, but I was more than happy to put it aside at the end of the day. In other words, I viewed this as a job or an assignment, not my “art” (whatever that means).

That also meant I was accountable to the other writers I was working with. Excuses that I sometimes use to get out of working on my own projects didn’t fly in this case because I had two other people counting on me to write my portions of the story.

That level of detachment did make it harder to engage with the material initially, but as we got further along into the story, that became less of an issue. The detachment also meant I was also more open to compromise as we discussed the overall story arc and decided on character traits and plot points.

We also stuck to a schedule. We met every two weeks while drafting the story. We started with an initial brainstorming session where we roughed out the plot. Then we would assign each other scenes to write. We would exchange those scenes before the next session, review them, and make big-picture adjustments at the next meeting. Then the process would start all over again. The result was a full draft in less than four months.

It also helped that each writer was assigned a specific POV character, so we didn’t have to worry about handing off that character to someone else and the continuity issues that would stem from that.

Would I do it again? It depends. I learned a lot about my writing through this process and exposed myself to the drafting techniques of other writhers. And it's encouraging to know that such collaborations can be successful—provided there’s a good mesh of working styles. Plus it was a lot of fun too.

Doing it again would necessitate a time commitment I’m not eager to make at this stage right now. That doesn’t mean some future project won’t be worth the effort.

So if you are contemplating a collaborative writing project, here are a few things to keep in mind:

Find writers you trust.

This means you trust their creative instincts, you trust their ability to do the work, and (it has to be said) you trust they won’t dick you over in the end. It helps that I’ve known the two women I worked with for over a year through our local writing group. Not everyone starting a collaboration will have this option, but the point is to vet the other writers the best you can and go with your gut.

Treat it as a professional obligation.

This means you (and the other writers) need to be accountable to one another. Make goals, stick to a production schedule, brainstorm together—but remember to build in enough leeway so that you can help each other if the going gets tough. Respect each other’s work and each other’s time. Couch story development negotiations in terms of craft and structure, not you own selfish desires for how the story should turn out. There’s no ‘I’ in ‘team’ and all that.

Remember that this is a learning opportunity.

Collaboration is a useful skill to have in your toolbox. It’s also a rare one, because of the difficulties inherent in any collaboration. Use this time as chance to look under the hood at someone else’s writing process—you may glean a few nuggets of wisdom for your own writing. You may also surprise yourself at what you are capable of in the right set of circumstances.

Check out On the Art of Collaboration in Writing from Magical Words and Amie Kaufman’s Three Rules You Can’t Break for more insights into collaborative writing.

Wednesday, December 5, 2012

You Know What Happens When You Assume Things…


Assumptions sometimes get a bad rap. A lot of times they make an ass out of you and me, but that’s often only in hindsight. In fact, I’d posit assumptions are essential to living, and, along with that, writing.

After all, an assumption is made based on the information you have on hand or experiences you’ve acquired and can extrapolate from. For example, deciding what to wear based on a glance out the window—I assume I won’t need a rain jacket because the sun is out. Or I assume I can make cream of cauliflower soup because I’ve made cream of broccoli soup in the past.

The assumptions we make are based on our accrued knowledge. So we accrue knowledge to survive, but that doesn’t mean that knowledge is always enough to navigate our world. Mistakes do happen, and that’s actually a good thing for writers.

As people read our stories and novels, they are interpreting our words and trying to make sense of the world we’ve presented them with. To do this, they must make assumptions. For example, if I don’t point out that the sky is green in my story and people get around by walking on their hands, my readers will assume the sky is blue and people walk like normal.

So if on page 30 I suddenly point out that the sky in my world is actually green, that forces the reader to stop and reevaluate what I’ve told them. This can be a bad thing when it throws the reader out of the story. But for some story elements, particularly reveals, this can be a neat trick and make your reader even more invested in figuring out your story as they try to fit the pieces together into a cohesive whole.

"But what does it all mean?"



I like to do this particularly at the opening of a story, where I’m trying to hook a reader’s interest by slowly dealing out world details. Readers will make assumptions based on what is mentioned and/or described, along with what isn’t. And depending on how those details complement one another or how they disrupt one another, my reader will make assumptions about the larger story world that can potentially make the worldbuilding easier on me.

As writers, we should all be relying on a reader’s assumption about genre conventions when crafting our stories except when those conventions interfere with the story we’re writing. In other words, we should be using these assumptions as world building shorthand except when they get in the way. Big deviations, ones that will just cause more confusion than not, however, should probably be addressed as soon as possible so you don’t disorient the reader.

But for me, I like to use reader assumptions and turn them on their head sometimes. As James Killick discusses in Reveals and Revelations,
If you break it down, there are only really two types of revelation that can be made within a story – revelations about the story and revelations about character. The differences should be fairly self-explanatory – a revelation about the story is when something is revealed outside of character – who the murderer is, who is sleeping with the heroine's husband. Character revelation is when something is revealed about character – a hidden trait, an unrealised dream, a hitherto misinterpreted desire.
And both of these (when successful) work because the author has leveraged the reader’s assumptions about the story. The trick is setting them up (which is another post entirely :P).

As readers, we make all kinds of assumptions based on what’s presented to us by the author, as well as unconsciously, based on our own personal and cultural biases. Remember the social media explosion when peoplewere surprised that Rue was black in the movie version of The Hunger Games? That was attributed to a tendency of assumed whiteness where readers assume literary characters are white unless told otherwise. In fact, as The Hunger Games demonstrated, those details stating otherwise can be easily overlooked in a culture of assumed whiteness (and it must be said, poor literacy skills).

So what does that mean for the writer? Well, I think in some ways it’s our duty to engage with these assumptions and draw attention to them by disrupting them in unique ways without sacrificing story. Particularly the more insidious ones related to gender and race and power (and Juliette Wade has a great post on this subject).

But ultimately playing with readers’ assumptions is just another tool in your toolbox. So use it wisely.


Thursday, November 1, 2012

How Do You Critique?

The last couple of weeks (and maybe into the next) I’ve been buried in critiques. Hence this slightly delayed post. I’m not complaining, mind you, but the volume recently—the result a confluence of chance—has forced me to evaluate my process in between all my edits, insertions, and comments.



Some observations:

I read everything. For me, critiquing is less about the genre or subject matter and more about supporting the writer behind the project.

I firmly believe there is a level of trust required for exchanging work. And that mutual respect means doing my best to evaluate the work I agree to critique, regardless of what it is, as I would hope others would do for me. It’s too early for me to be trapped in a particular genre, and I’m always eternally grateful that my CPs and trusted readers are usually game to crit whatever I send their way.

Part of this is because I’ve spent a lot of time in non-genre specific writing groups. In fact, one of the more successful groups I’ve been a part of has members writing in completely different genres—poetry, alt lit, women’s fiction, and then there’s me. All of us have good bs detectors and strong writing chops, which definitely helps. Plus having this exposure also keeps me from getting tunnel vision from the particular genre/style I’m writing in.

If a fellow writer thinks they’ll benefit from an honest reader reaction from me, I’m happy to support them. Karma is important, and I know I've benefited from the writer connections I've made. That’s not to say if they hand me a mystery I’ll be thrilled. But I’ll do my best to critique it, with the caveat that I’m not as well-versed in this genre as I am others.

I usually have to read a piece twice before I’m ready to critique.

This is time consuming, yes. That has become abundantly clear these last couple of weeks. BUT, it’s something I’ve made peace with. Mostly because my own standards of quality demand it.

Reading the piece the first time, I’m trying to get a general feel for the story, understand how all the different elements work as a whole. I might make some copy edits in the first round, but really I’m just reading for story.

This is a tremendous help when it comes time to offer my comments on the second pass. That’s when I decide what are real issues that need to be dealt with to support an author’s story intentions. I believe I have to understand the macro story elements into order to comment on the micro-level ones (outside of grammar).

My critique style has evolved as I’ve taken strides with my craft.

What this essentially means is that early on, I was overly focused with style and micro level issues. If someone wrote a line in a way I wouldn’t, I’d offer my suggestions for changing it. I was also overly concerned with "the rules" and more than happy to say "You're doing it wrong!" because the craft books said so. I won't say I was a Craft Nazi, one of the Writerly Types to Avoid, but it took time for me to digest all that advice so I could apply it in more constructive ways.

But after a number of critiques, after reading a variety of work, I’ve been exposed to a lot of different ways of doing things. And I've realized with all the do's and don'ts out there, all that matters is whether a particular technique is effective in a particular story context. That's it.

So I’ve adopted a more flexible live and let live policy. I’ll still point out awkward phrasings or unsuccessful techniques, but I’ve come to realize that just because someone doesn’t write something exactly the way I would doesn’t make it wrong. It just makes it different, and that’s ok. And that frees up more of my mental space for addressing more substantive story issues.

I rarely say no to requests to exchange work, but the time may be nigh to change that.

For so long, I was too scared to share my work. Then, when I got less scared, I had trouble finding people to share it with. I talked about this progression in my post The Critique Mindset a while back.

Over time, I’ve collected a formidable group of trusted writer friends: local writers, online writers, and my writer colleagues from Taos. For every person I can rely on for critiques, they must be able to rely on me. And as the last weeks have shown me, I’m near my limit, if I still want to be producing my own work at a pace that doesn’t make me cranky. (Hint, I'm cranky this week.)

So while I’m a huge proponent for exchanging work for critique, all things in moderation. And maybe it’s time to take my own advice.

***
Happy Nanoing for those participating! Happy writing for the rest of us! And only good thoughts for our friends on the east coast!

Wednesday, September 5, 2012

Pitfalls of Writing Tight

We are constantly told to write tight. No unnecessary words. Story as iceberg. Kill our darlings. Et cetera. You know, the Elmore Leonard school of writing.

And this is something I’ve taken to heart as I’ve tried to further my craft over the years. I like to think I’ve developed a spare style for myself. Which also may have evolved out of my experience writing flash fiction in one of my early writing groups. Still, I try to write tight, no matter what project I’m working on.

But sometimes this hurts me.

A long time ago, I wrote a post on how I have to write in layers, starting with a skeleton of action and dialogue and layering in all that other stuff that makes for a coherent and satisfying story.

Once I have a sense for my story, I’m eager to get it all down on the page and move on. I know what my characters need to do, when, and how. And then try to convey that as efficiently as possible.

There are a lot of reasons for this. Because I’ve already figured out what happens, there’s not always enough of an intellectual challenge to flesh the story out. Another reason is that there’s always another story jumping up and down in the back of my brain, waiting for its turn to be written. I have to take care to manage both of these impulses since I’m writing for publication, which requires a higher level of storytelling from me than if I were writing for my own entertainment.

Writing tight is great for controlling a story’s pacing. But if I’m too thin on the details, the character insights, the scene setting, and so on, I often rob my story of its full potential. So I have to spend a significant amount of time lingering over my scenes to ensure they are fully realized without slowing things down. And I often rely on my CPs and trusted readers to figure out what the right balance is.

Plot complications are another area I have to watch out for. After all, why delay the inevitable? I already know what happens in my stories, and complications just muck that up. But it’s also those complications that ratchet up tension and make the story’s climax awesome (or at least they should contribute).

There’s a reason I’ve stayed away from writing mysteries and suspense novels. So many of those stories rely on misinformation and red herrings to carry the story until the real plot is revealed at the three-quarters mark. And it’s hard for me to justify spending so much time developing irrelevant plot threads, when there’s a real story to cover. But I guess that’s just another writerly flaw of mine.

So while my craft has definitely benefited from learning to write tight, there are some pitfalls:

  • Write too sparely, and you risk confusing your reader. 
  • Write too lean, and you rob your story of its full emotional impact. 
  • Write too tight, and you could ruin the journey for the reader.

How do you strike that balance between tight writing and fully realized stories?

Wednesday, August 1, 2012

Different Stages, Different Questions

It’s funny how the questions you face as a writer shift and change at different stages.


Just starting out, I was preoccupied with things like:

How do I find story ideas?
How will I make time to write?
What even constitutes a story?

These are issues dealing with PROCESS – where I was still trying to figure out what to do. I’m to the point now where I’ve created a life around my writing (and I know how lucky I am to have the ability to do this). By making writing a priority, by owning it, these types of process questions have started to fade. Ideas come because I’m writing.

Then, for a very long time, different kinds of questions took over. Things like:

How do I show, not tell?
How do I layer description into story action?
How do I manage pacing?

And so on. These are questions of TECHNIQUE, as I’ve learned my craft in fits and starts. I’ve encountered different aspects of craft in each writing project I’ve attempted. Not every project will encompass every skill or technique we need to have in our bag of tricks. That’s why we’re told to write a little bit of everything—not only to see what we like, but also to expose ourselves to different aspects of craft and learn by doing.

Personally, I’ve found the gap narrowing between what I do and don’t know technique-wise. Doesn’t mean I’m awesome. But I’ve tried enough different kinds of writing that I’m much more comfortable when a trusted reader points something out that isn’t working than I was when I first started out. Because now I know things to try to fix it, where before it was more often than not a stab in the dark.

Doesn’t mean I’m right every time, but I have enough skills in my arsenal to get the job done. Eventually. I think ;)

But this iterative process can take a long time. At some point you start wondering why you didn’t come up with a sound story idea to being with, instead of one that needs so much fixing to get right. A different set of questions then:

What makes a compelling character?
What makes an exciting plot?
What makes a good story?

These questions about STORY are deceptively simplistic. After all, I’ve been writing a long time (it seems) and one of the questions I started out with is: “What constitutes a story?” In some ways that was the wrong question to ask. I eventually learned to write a story, but that didn’t automatically make it good. But until I got to where I am now, I didn’t realize how big a deal that was.

The difference between a story and a good story is the difference between unpublished and published, between newbie and pro. And that’s a huge difference.

And I’m still figuring that part out.

Have you found a similar pattern in how you approach your writing?

Wednesday, July 18, 2012

Managing Critique

I’m a firm believer in the benefits of critique—regardless of what shape they take.

Since getting serious about writing, I’ve experienced a wide range of critiquing styles and formats:

Reading Work Aloud – On one end of the spectrum, there’s things like open mic nights where tepid applause or catcalls tells you how well you did. I’ve done this once, and although I didn’t crash and burn, I don’t want to repeat the experience. On the other end, I’ve been in groups where you read a predetermined number of pages aloud and then discuss them. Great for problem scenes or seeing if your story or chapter opener hooks readers.

Exchanging Work – I’ve done where an agreed upon number of pages (up to 10 pages, up to 1 chapter, first 50 etc.) are exchanged in advanced and then discussed in small groups. Great for fostering local connections and looking at stories more in-depth. I’ve also exchanged full and partial manuscripts with critique partners and other trusted readers, marking up the text and making micro and macro level comments. It’s a lot of work but it allows you to evaluate a work as a whole, and as we all know, good readers are priceless.

Contests – There’s a wide variety of these for both short and long form work. Things like Miss Snark’s First Victim provide a forum for novel openers to see if readers are hooked. Query contests also abound on blogs. Plus there are a wide variety of contests sponsored through local and national writing organizations. Contests can provide you with feedback if you are in a place were you don’t have a trusted reader in your corner, but beware contest fees as not all contests are created equal.

Then there’s writing workshops like Taos Toolbox, where a lot of feedback comes your way all at once.

And that can be overwhelming. Strike that. It is overwhelming.


So how do you incorporate it all?

Well, when I have the opportunity to collect feedback from a variety of sources all at once, I like to focus on macro-level issues first.

These are general vibes my CPs and trusted readers get from my story or, in the case of the critiques from Taos, what stands out most in my mind as people went around the table and told me what was wrong with my stories.

Based on those things, I do a revision pass. That way I’m proactively working through what I perceive as problems with my story.

Only after I’ve done my initial revisions do I go back through the more detailed individual crits. That way I find I’m less reactive to individual comments that can often lead to changes in my story that serve the critiquer, not necessarily the manuscript as a whole.

Granted this process won’t work for every project, but I like to use this model whenever I can. Besides, by tackling the “big” issues first, because usually by the time you get to the smaller nits, many of them have already been fixed or eliminated.

There’s also some caveats to critiquing more generally.

As Kristine Kathryn Rusch pointed out in her post Perfection:
Critiquers get the manuscript for free and they’re asked to criticize it. Of course, they will find something wrong with it. In that circumstance, we all will.
So remember, just because someone says there is a problem with your story, figure out if it’s because they’ve been asked to find a problem or if there really is something wrong.

It’s also worth noting that not all critiquing advice is equal. Some people may not understand your vision for your story or be unable to divorce themselves from what they would do in your stead.

Fellow Toolboxer Catherine Scaff-Stump in Technique versus Vision explains:
If you ask me to give you feedback on a story, my job is to talk to you about your technique, but it is not to suggest you move in a different direction. I am not going to ask you to compromise your vision. You know what you want to do.

Worse, why would I pass judgment on your vision? I can say, "Your piece isn't very good." Unpacked, that should mean that you are vague, or your characters are underdeveloped. There should be things I can do to help you with technique. But I shouldn't be thinking that your piece isn't very good because I don't like it. Because it's not my thing. Because it's not my sub-genre. That's besides the point. I should be focusing on your technique, not telling you to like what I like.
Another great resource for figuring out how to incorporate feedback comes from How to Tackle Critique Notes from Writer Unboxed.

What other tips and tricks have you learned from your own critique experiences?

Happy writing!

Wednesday, July 11, 2012

Asking For More

What struck me most about my Taos Toolbox experience, I think, was how straightforward the lectures were. That’s not to say I didn’t learn more in-depth tricks or benefit from discussing different story elements over an intense two weeks—I did and it helped crystallize a lot of concepts for me.

But I do think you reach a certain point with craft, where there’s really nothing more to say. You either know it and use it, or you don’t. We all know we need that balance between character, plot, and emotion. And we have scenes and grammar to fashion our stories. But at a certain point, it simply comes down to doing.

At Taos, I learned that I’m doing many right things in my writing, at a high level. I also learned that I need to be doing more of it. At the individual story level and across stories. As I was told in my consultation at the end of the workshop (paraphrasing), “You can write. You need to stretch yourself and see what hits.” In other words, I know the basics, even beyond, and it’s time to stop being precious about my individual projects and start producing.

Wait, you want more from me?

As guest Daniel Abraham told us, “Publishing is a casino,” and you never hit the jackpot if you aren’t showing up everyday plugging quarters into the slots.

Time for the big girl pants.

That’s a scary thought. I feel a little like Dorothy in that I’ve realized I’ve been able to write all along. But if that were true, I’d like to think I’d be a bit further along in my writing journey. So there must be something else I’m missing, some missing piece of the puzzle.

I do think part of it comes back to output. I’m not a fast writer. I like to stew over my stories ideas and get lost in the different worlds. I’ve gotten faster at writing in the last year and a half, and I’ve been pushing myself to get there, but still other writers can write three short stories in the time it takes me to write one.

I also don’t move onto new projects quickly enough. I like to tinker, I like to figure out how to make my stories the best they can be, and sometimes that means I’m holding onto a sinking ship expecting to be rescued when really I should have taken that life raft and be onto something new. But if I don’t care about my work, how can I expect editors/agents/readers to?

Kristine Kathryn Rusch had a recent post on “Perfection” -- it’s worth a full read, but I want to focus on something she said:
Keep writing, keep learning, keep improving. But for god’s sake, don’t look backwards. Those books are done.

How do you know when a manuscript is done? That’s trickier. I think you should trust the process, fix the nits, and move to the next book. Writing is a subconscious art, not a conscious one. You heard your first story before you could speak, so your subconscious knows a lot more about writing than your conscious brain ever will.

Trust that.

Many writers don’t believe what I just wrote, and that’s fine. You need to define it for yourself. Set a limit on revisions, set a limit on drafts, set a time limit. (My book must be done in August, no matter what.) Then release your book on the unsuspecting public.

The book will never be perfect.
And that’s another hard thing for me. I want to write a perfect story. I want each of my stories to be perfect. And I work hard to revise them, chasing after some nebulous concept of perfection, when maybe I should be sending them out and moving on to the next story.

Of course, an exception to Rusch’s position is Andrew Porter, who wrote “Looking Back” for the latest Glimmer Train bulletin. An extensive revision of one of his older stories has gone onto being his most successful, wining him the Pushcart. He says:
I think most writers have a tendency to discount their early work, especially those pieces that were written when they were first starting out, when they were just figuring out how to write a short story in the first place.

In some cases, we're probably right to discount those early efforts. I know, for me, there's a certain cringe factor involved. Sometimes simply remembering the basic premise of one of those early stories is enough to make me shake my head and vow never to look back. Still, I've recently begun to wonder whether my own tendency to always look forward—to always believe that my best work lies before me, that the fiction I wrote five years ago isn't nearly as good as the fiction I'm writing today—doesn't prevent me from recognizing the potential value in some of those old unpublished stories that are just sitting there on my hard drive or collecting dust in a folder.
So writers should always be moving on to the next project, except when they shouldn’t. Hmm.

So what makes the difference? Fellow Toolboxer Catherine Scaff-Stump may have stumbled upon the answer in her post-workshop post on Technique versus Vision (also worth a full read). In it, she talks about how workshops can teach technique, but they can’t teach vision, and how the critique process can muddy the two.
I'm going to work my ass off regarding technique. And...so what if my vision is different? Different can be the next thing. If I find myself doubting my technique, I should. I can fix that. If I find myself doubting my vision, that's the end of the story. That's the death knoll for my writing, right there.
So maybe it’s not about writing lots just to write lots or revising things to death because you can’t bear to send something out less than perfect. Maybe it’s about finding your vision and finding ways to bring that vision to life. And if your older stories have solid vision, it’s about updating them craft-wise as your skills as a writer develop. That’s not stepping back; that’s bringing them to life.

I like to think I have vision with my stories. Now it’s just about making them come to life.

I guess no one ever said this whole writing thing was easy.

Happy writing!

Monday, July 2, 2012

Recursive Plotting with Guest L. Blankenship

Today I’m pleased to bring you a guest post from L. Blankenship of Notes from the Jovian Frontier. Not only is she an awesome critique partner, but she also contributes to Unicorn Bell and Science in my Fiction. Enjoy!

***
First, a thank-you to Bluestocking, my awesome CP, for letting me guest blog here to promote my Kickstarter project! Details for that at the bottom.

Recursive Plotting:
I've been working on a six-part, gritty fantasy romance for some time now. As popular as multi-volume fantasy stories are, they're not so easy to write. Some of that is because of plotting. A six-book series has all the same plotting problems that a one-shot book does -- only with the added size and weight of a lot more words.


There are many ways to break down plots into stages. Here's the one I use: inciting incident, first plot point, other plot points, climax, resolution. You can further group these into a three-act structure or apply other methods of plotting if you want. For now, I just want to focus on the inciting incident.

The inciting incident is that event which sets off the whole story. It sets things in motion. Some call it the point of no return -- because of this incident, something must be done. Something will happen. Because of the inciting incident, the first plot point happens. Because of that first plot point... and so on, building toward the climax.

The first part of my novel has an inciting incident: my protagonist, Kate, is given an early graduation into the duties of a physician and told to attend to a small party heading into the mountains on a mission that nobody seems to want to explain.

 Something must be done: the authority figures in her life have laid this on her, and being a bright young student she wants to live up to their expectations. The rest of the plot hinges on this one event happening, or Kate would have just stayed home and kept studying.

To step back, this is Part I out of six. and while each individual Part contains a plot structure of its own, the series as a whole also contains a plot structure. Writ large, as it were. The series has an inciting incident, first plot point, other plot points, a climax and a resolution.

Part I is, as a whole, the inciting incident for the other five parts. It sets a larger plot structure in motion and because of this, certain things must happen. Certain things must be resolved by these characters. Part II is, as a whole, the first plot point. This larger plot will build its way up to a climax and resolution in Part VI. Though, as I said, each Part will still contain all the plot stages to support what happens within that Part.

In short, plotting is recursive. (This makes my nerdy little heart smile.)

Shameless Plugging:

I'm running a Kickstarter project to fund the professional editing, proofreading, and cover artwork for my gritty fantasy romance, Disciple, Part I: For Want of a Piglet. There will be six parts in total, published over the course of the next few years.

I'm pre-selling e-books, paperbacks, offering promotional bookmarks, and more at various pledge levels (ranging from $1 - $100). Check out the project page for my book trailer, budget, and production schedule.

Kickstarter.com is a fundraising platform for all sorts of creative projects. Artists post a profile of their project and offer rewards in exchange for pledged money. The pledges are not collected unless the artist's funding goal is reached within a set period of time. If the goal is reached, the artist receives the money, carries out the project and distributes the rewards promised. It's a fascinating site and easy to lose time in!

***
I've had the privilege to read the first three parts of Disciple, and can't wait to see the rest of the series. If you like strong heroines, unique magic systems, and realistic medieval detail, both action and character, these books are for you. 

Be sure to check out the first chapter here

And please consider donating as a little as a dollar to help L. get these books into the world. Thanks, and happy writing!

Related Posts Plugin for WordPress, Blogger...