Showing posts with label beta readers. Show all posts
Showing posts with label beta readers. Show all posts

Tuesday, January 7, 2020

Going for a Hike

When I read that a writer revised a novel sixty-four or a hundred-and-eleven times, I am not awed. I'm baffled.


Tackling a revision is like going for a hike.


First draft, for those of us who are planners, is like going for a hike to an unknown place but using a map. Pantsters (those who write by the seat of their pants, no outline) are hiking to unknown places without a map. Pantsters have only a vague sense of where they must end, which is some variation of home, be it a mental or emotional state for the main character or the plot coming to a place of equilibrium.


I always work on the first and second draft alone, and it’s the closest I come to hiking without a map. By the second draft I already know the trail (=first draft) but now I must see if this was a good, satisfying hike. Before anyone else’s feedback, I’m not clear how to asses. So I made some standard questions I ask myself as I go.
Theme?
Consistent voice?
Foreshadowing?
End that echoes the beginning?


Now it’s time to have others join me; Beta readers, whose feedback is invaluable. Their specific comments become the trail map for the next outing= the third draft. I find it much easier to revise to specific feedback. It is like hiking with specific places to pass on the way.


Revising is also akin to hiking in that after many rounds you stop seeing much of the road. It just goes by with nary a single detail noted. This is why my process stops at the fifth or sixth draft. For me, there's a point where I no longer see what a reader would, and that's where I'm done. I’m always ready to go back after some time has passed, or an acquired manuscript gets new eyes to guide it. But on my own, it’s a five-six times trek.



Because writing, like hiking, is an effort that should reveal and enhance, not suck the life out of the traveler. 

Tuesday, July 10, 2018

Finding the Light in Revision Cave*

*With apologies to the heroic rescue of the trapped youngsters of the flooded cave in northern Thailand. No concrete comparison is appropriate. But to be honest, this real life wrenching drama inspired this post.


Dealing with revision suggestions can feel like trying to crawl in complete darkness. That is because after catching one’s breath from the gut-punch (akin to someone saying your perfect baby is not so lovely after all L) and then allowing the suggestions to sink in, many a time the writer still can’t see why these suggestions were made.


It's easy, even fun, to make changes when the suggestion make sense. These "Ah-Hah (!)" suggestions make the write's heart grow limbs and do an exhilarating Hopak, which is a Cossacks' leg-kicking dance, in joyous appreciation. It's just that these types of suggestions are the rare ones.


Most editorial suggestions fall into the other camp. Be it by a Beta reader, an Intern, an agent or an editor, the writer feels like telling them they just didn’t get it and the fault lies in their flawed reading, not her writing.


But feelings should have nothing to do with it. Feelings and intuition guided the first draft all the way. Revision is about returning reason to the equation and reminding oneself the feedback came from someone who, just for making the suggestions, is a helpful soul.


So now the writer moves to phase two. To implement the suggested changes, or not to? That is the question.


My answer is that I must try. Not because the reader was right. Not because the reader was wrong. But because it is good for me to try.


This is where it feels like I'm crawling in the dark. How to make changes that don’t resonate? Where, who, and with what?


Take a deeeeep breath. Trust in the muse. She is akin to a miner’s light.


She’ll get you there, and your humanity will be better for it.