Harry Bingham of Jericho Writers had this to say about feedback in last Friday’s email:
“One thing that mildly panics me when I offer advice via Feedback Friday is this: What if my advice is totally wrong? There are some areas where I don’t have those worries. Sometimes, for example, I give specific editorial advice on a particular passage. For example: “Your long second sentence would be better split over two sentences.” “The image of the X in this passage is interesting but currently a bit confused.” “You could lose word count here and still convey what you need to convey.” In all those instances, I’d mostly expect any competent editor to agree with me, or at the very least to understand my concern. Exact strategies for dealing with the concern are legion, of course, but the editorial process is basically the same three steps, repeated endlessly: Figure out if you have a bad feeling; Figure out where that feeling is coming from; Figure out what to do about it. Those three steps are the same whether you’re a paid third-party editor, or a free beta-reader, or just you re-reading and re-editing your own work. Obviously, the editorial process would be a bit pointless without that third and final step, but the first two steps are often the ones that feel transformative. “Oh, gosh, you’re right! Now I know why I felt uneasy and I can already see several different solutions all of which could work.” Likewise, if I’m talking about something very brief and self-contained – an elevator pitch, for example – I feel well-qualified to offer feedback. Coming of age story in the world of Shakespeare’s Macbeth? That’s a wonderful, saleable pitch, and I’d pick that book up in a bookshop. Near-future eco-disaster novel for adults involving mermaids, flying killer robots and a talking rabbit? Um. Maybe not quite so good. Even here, it’s hard to be confident quite what I’m criticising. If I come across a less-than-compelling elevator pitch, is it the pitch that’s at fault (a simple fix)? Or is it that the book itself doesn’t work (a terrifying prospect)? Because of this uncertainty, I try to proceed gently but I do tend to trust my gut feeling about the material in front of me. Other reasonable people might disagree, but I’d expect my views to be echoed by most genuinely competent judges. (Though, having said that, I’m meaner than most. Whenever I’ve given feedback alongside agents, I’m almost always pickier than they are. I’m Simon Cowell, minus the botox.) Then we get to some more delicate areas. In last week’s Feedback Friday, we looked at very brief plot synopses. Thar’s a super-useful exercise for any writer because it forces them to consider the top-level shape of their plot as well as the causal unity of it. (What do I mean by causal unity? Simply that most novels don’t work if it’s one thing, followed by another thing, followed by another disconnected thing. We want the various events to flow, seemingly inevitably, from the one event that incites everything.) In those cases where I was underwhelmed by a synopsis, what exactly should the author deduce? That the synopsis is poor? That the book’s basic plot structure is poor? Or just that Harry didn’t like something, as a matter of his own personal taste? Honestly, in a lot of cases, I think any one of those three explanations are possible. A short synopsis isn’t much to go on and a certain humility is in order from anyone offering advice. Much the same goes for any criticism of a passage where context is significant. So let’s say for example, I’m not that impressed by a passage where Princess Kara faces the dark Lord Mephilo. Suppose I think that Princess K just wouldn’t be likely to say or do X, or that a particular emotional reaction feels awry, or something else of that sort. Well, is that because the passage isn’t convincing? Or because there’s backstory dealt with elsewhere in the book which makes those things explicable? Again, any sane editor just has to approach questions like these with humility. All you can do is note an uneasiness and let the author use that observation in any way that’s helpful. In the end, the responsibility is always yours, the author’s. The issue isn’t really whether you like what I, or some other editor, say. Often enough you won’t. But I want the mermaids! I insist on keeping Pep the Talking Rabbit! And fair enough: this is your book, not mine. The question is always, “Is this comment useful?” Does it illuminate something? Do you the author get an insight that you personally find useful and actionable? Authorial responsibility never changes, no matter how far you go. Comments from me via Feedback Friday? Comments from an editorial buddy or beta reader? Detailed comments from a pro Jericho Writers editor following a read of your entire manuscript? Comments from an agent? From a publishing editor? From a copy editor who’s preparing your manuscript for publication? You must never let go. The manuscript remains yours. I literally don’t let a publisher change a comma without my approval. When I’ve had copy editors who didn’t get my style, I’ve been through a whole 100,000+ word manuscript reversing the changes that have been made. It’s your book and no one else’s. Ever If a comment chimes, use it. If a comment doesn’t, disregard it. If a comment alerts you to a particular issue, but you want to deal with the issue in some way other than the one suggested, then go with your solution. It’s your book.” |