Showing posts with label nuts and bolts. Show all posts
Showing posts with label nuts and bolts. 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, September 11, 2013

How to Survive Your First Worldcon Part Two


Over Labor Day weekend, I attended my first Worldcon in San Antonio, Texas. I had no idea what to expect, and I’ve decided to share what I’ve learned so you’ll be better prepared if you plan to attend an event like this in the future.

Be sure to also check out Part One.

6. Stay in the Conference Hotel


It can cost more money to get a room at the conference hotel, but by staying there you quadruple the opportunities of meeting people. For this con, since I was traveling with my non-con attending husband, we decided to stay in the non-party hotel so he’d get a break from the convention atmosphere. Big mistake.


Our hotel was right next door, so logistically, it wasn’t a big deal. But looking at it in terms of elevator rides, morning coffee lines for the lobby Starbucks, drinks at the hotel bar or dinner in the restaurant—these are all opportunities to see and be seen. And serendipity may smile on you and put you in the path of someone who can help your career.

You know the old adage that publishing is a numbers game? Cons are no exception. Position yourself to best advantage, even if that means putting up with hotel room that backs to a con suite.

7. Panels Are Not Your Primary Objective


This might sound counter-intuitive, but bear with me. I spent my first day at the convention scouring the program and identifying what panels I wanted to see. And that first day, I went from panel to panel like a good little attendee.

There are two problems with this approach. One, you will not be able to maintain this level of focus for ten hours of programming each of the five days. Two, if you are attending panels, you’re learning, but most likely not networking. Granted you could approach panelists at the end of a presentation and if you’re lucky be able to introduce yourself. Or perhaps you find yourself sitting next to someone important. It can happen.


But you should be flexible enough so that if someone, especially if they’re higher up on the writing ladder, says let’s skip the next session and chat/get drinks/food/whatever….that’s what you should do. No matter what panel you planned to see at that time.

8. Be Prepared but Be Prepared to Leave Empty-Handed


We’ve al heard those magical stories of authors who attended a conference and came home with a book deal. And if that happens to you, more power to you.

But for the rest of us, you never know what could happen. You could have pitching opportunities and flub them or maybe no one will give you the chance to talk about your work. That’s okay, because you have to take the long-term view and know that slow and steady wins the race.

Knowing that lightning probably won’t strike though is no excuse not to be prepared to talk about your book (or whatever else you have going on). Think elevator pitch and practice it so you don’t sound like an idiot (I wish I practiced more).


Even if you don’t talk to an agent or an editor, your fellow writers may ask. You have to view these moments as opportunities to gain an advocate of your work if they like what they hear. They could be indifferent or unimpressed by your story pitch—but they’ll still recognize the fact that you are treating yourself and your story professionally.

9. Take Time for Yourself


This is important. Give yourself a break every now and then to recharge. There will be plenty of opportunities to hang out with other writers and meet new people. 

 

But you have to be the best possible version of yourself to make genuine connections. Everyone will be operating on fewer Z’s, and some people might be hung over or have spiking blood sugar. But it’s on you to maintain your body and your well being.

***
That’s it. That’s all I got. Hopefully it will be enough to give you a kick start for your next convention. Happy writing!

Wednesday, September 4, 2013

How to Survive Your First Worldcon, Part One


Over Labor Day weekend, I attended my first Worldcon in San Antonio, Texas. I decided to go for a lot of reasons, but I think the most important one was to slowly increase my visibility in the field by networking with my writing colleagues.

The view from my hotel balcony.

I had no idea what to expect, and I’d like to share what I’ve learned so you’ll be better prepared if you plan to attend an event like this in the future.


1. Never Take Off Your Nametag

This could be my own issue, but I’ve never been a fan of nametags. Whether it was the first day of school, my work as a waitress back in the day, or attending work conferences, my initial impulse was always to whip off the tag as soon as possible.


Do not do this. The whole point of conventions is to meet like-minded people, right? But unless you already know someone’s a writer, it can be tough to spot one out in the wild. At a convention, if you see a nametag, you can be reasonably sure they’re a serious SFF fan or writer or both, whether you are crossing the street between the hotel and the conference space, hunkering down in the hotel lobby for the free internet, or getting a drink or a bite to eat in the hotel lounge. So this is one of the few times where it’s okay to let your freak flag fly.

The nametag also makes introductions easier and seeing a printed name (as opposed to just hearing it) can reinforce retention.

That said….

2. Be Prepared to Reintroduce Yourself A Lot

You will be meeting a lot of people. And just as you will have difficulty keeping everyone straight, the people you meet will also have trouble putting the name to the face. If they don’t remember you, don’t take it personally. Be gracious, and if the opportunity presents itself, remind them that you met them the night before at a party or last year at another event or that you share a TOC together… whatever it is that will help jog their memory and put you into context.

 

You want them to remember your face, your name, and something pleasant about you—not how you gave them a hard time for not remembering who you are from a 15-second introduction. That just makes them feel guilty, and they will then avoid you to avoid experiencing that negative emotion again.

3. Dress to Impress

I’m not talking business casual. Personal hygiene is important to handle (especially in Texas in August). As Mary Robinette Kowal said in a panel on schmoozing, you want to be the best possible version of yourself—whatever that means to you.


For me, that meant wearing clothes that had a consistent feel, styling my hair in a similar way, and wearing the same necklace and bracelet combo across the days at the convention so that people would recognize me, even if they didn’t know my name. Think of it as professional branding.
  
4. Ribbons Ribbons Everywhere

As this was my first con, I didn’t realize there were special “ribbons” you could affix to your nametag. These little pieces of fabric were issued to people who had pub’d in certain magazines or talked to certain con personnel or supported a particular author or whatever. I later found out there was even a ribbon for attending your first Worldcon. Many people (though not everyone) had them. I even saw one kid walking around the convention hall with so many ribbons they dragged along after him.


As with the nametags, the ribbons provide quick visual reinforcement in identifying people in your “tribe” and often served as a source of small talk. Now, I’m not saying I was ignored because I didn’t have any ribbons—I wasn’t. But it did reinforce my newbie status because I had no idea how they worked.

The exception of course were the bright green ribbons identifying the panelists and invited guests to the convention. Which leads me to….

5. Pay Attention to the Social Hierarchy

At the con, I was pretty insignificant compared to the writers further along in their careers and the editors and agents that were there. And the ribbons often reinforced this.

Unlike other cons, there were no pitch appointments offered. The only way to get an agent or editor’s attention was to either get introduced by someone they respected or small talk your way into their hearts.


Both are hard to do and are extremely dependent on luck, your social abilities, and the kindness of your colleagues.

People can sense desperation. If someone powerful has a bad opinion of you, it could haunt you the rest of your career. So don’t be that person who stalks the important people all over the con or the person who turns into a squeeing mess the second you get to talk to your writing hero, dream agent, or whathaveyou.

Instead, be sure to act courteously, and if at all possible be interesting. You may not get an opportunity to talk about you or your work, and that’s okay. Take the long view. You want to leave people with a favorable impression no matter what because who knows what could happen the next time you meet them.

Stay tuned for Part Two next week!

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, June 12, 2013

Best Laid Plans


Writing is a slow process. From idea to draft, from early drafts to later drafts, from query to agent, from contract to publication. That doesn’t mean things can’t move faster, just that they so often don’t.

Patience is a quality you need to cultivate if you are going to survive this field. I understand all this—even if I don’t like it. One thing I like to do is make plans to distract myself from the futility of waiting (I’m type A all the way).


Regardless of whether you’re a plotter or a pantster, I think being able to plan is a crucial act of writing, even if it’s the just-in-time variety pantsters employ. We have to be able to hold large amounts of information in our heads and then turn that information into something that’s not only literate but adheres to a recognizable structure. This ability is explored in part by Maps of the Imagination: The Writer as Cartographerby Peter Turch—a book that’s geared more to thinking about writing than actual writing, if you know what I mean, though in this case that’s not a dig.

Planning, making mental maps, using words to formalize what has only been nebulous or intangible thought… these kinds of activities take a lot of time, and can be the very means to work through the periods of waiting that always seem to crop up.

These activities for me often include:
--Planning out my next project
--Determining what I need to do on the blog
--Prioritizing story drafts across projects, critiquing for my writing groups and CPs, and research time

I also create contingency plans in my head.

Sometimes I create contingencies when I’m plotting out a novel and need my research to corroborate the action. I want X to happen in my story, but if the research doesn’t support X, I’ll need to go with Y. Or Z. Or maybe X will work but another set of conditions need to be considered. By planning out what needs to happen, and what alternatives could also work, I’m able to work through tricky plot issues and stay on target with my story.

Or in the case of submitting, say I have a handful of short stories under consideration at markets. However, most markets have no simultaneous or multiple submissions policies in place. Because of this, I have to consider what is the best order to submit them. Usually factoring in some combination of

1. Impact (higher tier/exposure over lesser markets)
2. Response time (quicker over slower)
3. Fit (always hard to judge)
4. Deadlines

For example, let’s say the average response time at a market is a week. And there’s a deadline for stories with a theme similar to my story coming up in two weeks. I would probably submit my story to the market with the 1-week deadline, under the assumption that if it gets selected (great), but more realistically I might get some feedback that would help me to submit to the themed market in time.

I’ve also created contingency plans in my head for what happens if something big and exciting happens. What then? I don’t recommend this last one. For starters, I can make a gazillion plans and all that mental effort goes out the door with one rejection. Sure, a contingency plan will kick in then, and I’ll remain optimistic for another few weeks and then… Well, you can see how this cycle could last forever.

So planning can range from the highly useful (as in the case of story plotting and time management) to busy work (micromanaging story submission orders) to entirely unnecessary (winning the publishing lottery).

But writers write. And in the case of this writer, I plan as well.

Happy writing (and planning)!

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)!

Wednesday, April 3, 2013

Rough Crit


Criticism is hard to take sometimes. But if you are actively seeking it out, there’s no better way to improve and hone your craft in my opinion. It means you take your work seriously and want to grow as a writer.

It also means you are guaranteed a rough crit session from time to time. So here are some tips for how to survive an in-person critique when it seems like your colleagues or fellow workshoppers are out to get you.

During the session:

1) Don’t get defensive

I repeat: Don’t get defensive. Getting defensive leads all too easily to getting angry, which can lead to things being said that cannot be unsaid.

If you find your hackles rising, find a way to channel that feeling into something productive. Me? I’m a notetaker. I write down all the bad things someone raises about my work during critique sessions. Even the things I don’t agree with. Something about the process of notetaking adds a crucial bit of separation between me and what’s being said, allowing me to compartmentalize the negative stuff and move on.

2) Don’t try to justify


We’ve all been in that situation where a writer says something like, “Well, what I was trying to do in that scene…” or “My intentions were…” et cetera. This often leads to a lengthy monologue where the writer explains why the story is the way it is, refuting every issue raised during the session along the way.

This is a waste of everyone’s time. If you try to justify what you wrote—preferring your words to a reader’s honest reactions—you’re basically saying your critiquers’ reactions to your story don’t matter. Which begs the question why you are soliciting critiques in the first place.

Note that this does not mean you can't ask someone for clarification about why they felt the way they did about your work. You can. But be wary if you find yourself protesting too much.

 

3) Don’t take your bad crit out on others


I’ve been in roundtable critique sessions where a writer responds to a harsh crit by being harsh in turn out of spite—not raising legitimate issues with the work under consideration. Don’t be that person.

If you can’t be civil in the aftermath of a rough crit, excuse yourself, take a time out, do whatever it is you need to do to find balance. It may not seem that way when your critiquers are tearing apart your work, but they are trying to help you. Don’t do something that will jeopardize their future good will.

 

After the session:

1) Give yourself some time

If you aren’t ready to dive into the negative feedback, that’s okay. Read a book, work on another project, do whatever it is you need to do to be in the proper headspace for processing feedback.

Taos Toolbox had a very large critique component. I deliberately refrained from looking at what my colleagues had to say about my work until I got home. Why? Because I knew if I looked at the written feedback it would distract me from my main goal of the workshop: making real connections with fellow writers. I didn’t want my interactions tainted by the critiques—that’s the one who got too heavy-handed with their line edits or that’s the one who hated my MC—instead of getting to know them on a more personal level. It also gave me time for their suggestions to sink in, and when I got home, I was more open to making changes.

 

2) Understand who is giving you feedback


In other words, not all critiquers are created equal. Just because someone writes a lot or well doesn’t mean they automatically give good feedback. Similarly, just because someone doesn’t have a lot of publishing credentials doesn’t mean they won’t have any insights into your work.

Some things to ask yourself when weighing feedback:

How much experience does this person have with critiquing?
Do they write in my genre?
Do I like their style/storytelling abilities?
Are they a writerly type to avoid? – Inexperience, ignorance, and ego can all be problematic

 

3) Understand what you are getting feedback on


You’d think this is a no-brainer, but you’d be surprised. Whatever you submit or send in, right? Here’s the thing. You know, consciously or unconsciously, what kinds of questions you have about your story. And whether you ask for specific feedback or not, the issues your critiquers raise can surprise you.

There’s nothing worse than expecting macro-level feedback and getting your story put through a line editing meat grinder. Or expecting help to polish a final draft, only to have your story premise dissected. That’s not to say those things can’t be helpful—usually they are. But if you aren’t expecting it, those kinds of crits can be devastating.

So double-check your critique expectations. If there’s a large deviation between the feedback you expected and what you actually got, ask yourself the following:

Did I specify my critique expectations? 

Sometimes it is as simple as saying your story is an early or a final draft—often that will cue the critiquer to respond accordingly. Other times, you may need a second opinion on a problematic element (say structure or characterization). You want to make sure you tell your critiquers that. It may not help—they could forget or get distracted by another aspect of your story, but at least you know you tried to get the right kind of feedback for your story.

Did I inadvertently trigger one of my critiquer’s hot-button issues? 

People will respond in unexpected ways to your work. If you hand an atheist a Christian romance, well, that could lead to a very interesting critique. People with different worldviews and life experiences are great to have in a writing group—but those very differences can lead to surprising results in practice as well.

It usually comes down to knowing the people you are exchanging work with. As someone who’s spent a lot of time reading and writing romance, I can be very critical of those scenes. One of my writing friends is an interior designer, and often her comments pick apart descriptions of interior spaces and architecture. Similarly, scientists get cranky when you fudge scientific details or resort to handwaving in speculative works.

So if a critiquer is overly sensitive to an aspect of your story, ask yourself why. Usually it is because they have firsthand knowledge or expertise on a particular subject. Instead of getting defensive, use their knowledge to strengthen your work.

***

I hope this post results in less stressful and more useful critique sessions. For more on this subject, check out 5 Ways to Get Good Revision Notes.

Happy writing!


Wednesday, February 27, 2013

Push or Pull

What kind of writer are you? Someone who needs to be pushed to write? Or someone who would write no matter what, putting themselves out there, pulling themselves up by their bootstraps?


I’ve been both at different stages.

When you need a push to write:

To take the plunge—Maybe you had a teacher who inspired you, or a partner or family member who encouraged you to write. Or maybe you read something that was so amazing you wanted to write too. In any case, someone or something pushed you into the writing world.

To follow through—But writing can be a fickle process. Sometimes we get in funks where we can’t write or lose our confidence in our abilities. That’s when a nudge from a writing friend or taking steps to reinvigorate your creativity helps you keep going when the going gets tough.

To do what’s required—We can all hope we reach the point where contractual obligations and deadlines serve as the push to keep us writing.

When writing pulls you in:

Because you have a story to tell—Often we discover our love of writing because we have a story to tell, something that can only be expressed in words. And by taking that first step, you discover you have even more to say.

Because you’ve found your rhythm—Some days the writing comes easy. Those are good days, and they are earned because you’ve built up momentum in your story. Developing a writing routine can also help by giving your brain a set time when the words can pour forth.

Because you have goals you want to reach—And the only way to reach them is to keep writing. Sometimes that’s the only inspiration you need.

***
So at the end of the day, is your writing pulling you or pushing you?

Wednesday, February 20, 2013

Immaturity in Writing

In January, I started reading slush for Masque Books, a digital imprint of Prime Books. And so far it’s been a fascinating peek behind the publishing curtain.

I’ve seen my fair share of crazy fonts and strange formatting, but not nearly as much as I expected to based on the horror stories of the slush pile that get bandied about. What’s surprised me the most is the overall care that’s gone into the submissions. This doesn’t mean they’ve knocked my socks off, but rather that the average submission is much higher in quality than I expected—they’ve been literate, proofread if not perfect, and largely followed the submission guidelines.

That kind of attention to detail is encouraging to see, which is why it’s so heartbreaking to get to the actual story and know within two paragraphs, sometimes sooner, that it’s a no-go. And more often than not, the culprit is immature writing.


What do I mean by that? Well, it’s a catch-all phrase that I use when I see a manuscript that has either sentence-level issues or a lack of sophistication with elements of craft (or both).

Sentence-Level Issues

This can be as simple as a poor grasp of grammar—improper punctuation, run-on sentences, etc. A mistake or two won’t make or break a submission. But they can add up, and when the errors are egregious, it’s that much harder to take a story seriously.

There are also more subtle signs of sentence-level issues. Things like wordiness, filtering, awkward phrasing. I’ve trained myself to write tight, to weed out inefficiencies in my text, to catch mistakes and edit out the awkwardness. When I see project where these kinds of things aren’t addressed, it makes me wonder just how far along the writer is in their journey. Is this their first project and they haven’t quite figured everything out? Or have they just not taken the time to refine their writing to make it the best it can be? I usually go with the former interpretation, and have to hope they won’t give up when they get their rejection, that they’ll keep writing, keep striving until they get their stories out into the world.

Bottom line, every word in your story subconsciously signals your ability as a storyteller to a reader. Sentence-level issues are the one thing you as a writer can control in a highly capricious business, so there’s no excuse not to learn them. And if you haven’t learned them, when I read your submission I assume that you are too immature a writer to competently tell me a story I’m interested in.

Elements of Craft Lack Sophistication

This is even more subjective, but in some ways more detrimental to a submission. Say an author has great descriptive powers, but cannot orchestrate an action scene to save their life. Or the voice of the protagonist is largely spot on, but infodumps and unrealistic dialogue grounds a story before it even gets started. Essentially, there is some aspect (or aspects) of the writer’s craft that screams inexperience, by virtue of it being poorly handled or weaker relative to other aspects of the work.

This isn’t always a fatal flaw—after all, a good editor will work with a writer to improve all aspects of a story. But the problems with craft must be surmountable. For example, a story where every paragraph tells the reader what to think instead of showing them or a clumsy inner monologue that sidelines action in every scene are too insidious to tackle. Other things like a lack of specificity or an overabundance of specificity could be fixable, but the story would have to be worth the effort.

This is where beta readers and critique partners and groups come in, because writers can be blind to their shortcomings.

Bottom line, you cannot afford to ignore the weaker parts of your craft and hope the rest will be strong enough to carry your story. If I see a big imbalance in your abilities as a writer or if the way you handle certain aspects of craft show your inexperience or lack of awareness of what’s acceptable, then I’m going to assume you haven’t matured as a writer and that your story isn’t ready for publication.

Harsh? Yes. Necessary? Also yes. I’ve only recommended two stories since I’ve started slushing, and those were both with big reservations.

So at the end of the day, remember: Writing stories is hard. Rejecting stories is easy.

It’s all too easy to find a reason to reject a story. You’re goal as a writer is to minimize those reasons for “easy” rejections (following guidelines, fine-tuning your prose, making strides with your craft). You want to make it difficult for me to say no. You want me to keep hoping if I turn the page, it will be worth it.

I want it to be worth it. And you can prove that to me by maturing as a writer. It won’t happen overnight. But if you keep writing, keep working, keep striving, you’ll get there. We all will. One day.

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.

Friday, December 14, 2012

Assumptions, part deux


Last week, I talked about reader assumptions and how the writer can use them to their advantage in their stories. They’re great for worldbuilding shorthand and reveals and revelations, so long as you don’t thoroughly confuse your reader in the process. And I should also say, it can take time to get a bead on what readers think as they progress through a story. Experience will help guide your intuition, along with really awesome trusted readers.

But today, I want to talk about a different kind of assumption. The assumptions we writers make every time we sit down and, well, write.

Think back on when you first started writing. Did you think it would be easy? Did you think if your story had a beginning, middle, and end, it was bound to be good?

As you continued to write, did you assume that if you never stopped, that would somehow translate into success? What about if you wrote a good story/book and assumed it would sell even if there wasn’t a ready market for it? After all, we are told to write the book of our hearts, regardless of what the market demands… Did you ever assume you could get away with breaking the rules because you are you?

Alas, in writing there is no easy button.

Now, some of these assumptions may smack of naiveté now, but I guarantee you those assumptions were helping you to do one of two things: 1) Stay motivated – those dreams of making it big fuel us all at one time or another, and 2) Finish the story – after all, if you don’t make it to the end, it doesn’t matter how well you can write.

In the post Different Stages, Different Questions awhile back, I talked about how writers operate at different stages of writing experience, and the questions that guide their efforts. I also think the assumptions we carry with us at different points in our lives also have a formative effect on our work.

After all, if you don’t know any better, those assumptions are all you have to navigate the writing process. And they can be useful, except when you reach a point where they stop being helpful and start being a hindrance.

I want to point you to a series of posts on The Cockeyed Caravan blog by screenwriter Matt Bird (and if you haven’t visited this blog, you are missing out). In the series, he talks about the more detrimental assumptions we writers make about process, craft, and careers, and discusses the actual reality we face. I know it’s a lot of links to click through, but I think you’ll agree that he’s spot on.



Happy writing! (And retooling your own assumptions about 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!

Related Posts Plugin for WordPress, Blogger...