The Key to Being a Better CP

 This Week's Topic: Tips for being a better Beta Reader / CP

Hahaha. OMG. {hangs head in shame}. Lo, I raise my face to the heavens and confess my sins. When I started being a CP I hadn't learned the most important thing about constructive critique:

 Tell 'Em What IS Working and Why. 

As a CP, I'm a stronger developmental reviewer (which is an Alpha Reader/CP thing) than I am a line or copy reviewer. My analytical brain overreacts to Where's the Plot Ball, That Shit Makes No Sense, and Failure to Meet Genre Minimum Expectations, so I bleed Add Comments all over the doc. As an author, receiving dev edits is usually the greatest cause of bourbon binging because fixing developmental issues usually means rewriting whole chapters and/or morphing plot threads throughout multiple arcs. You can bet the author is desperate for at least one (if not a dozen or three dozen) callouts for something that is working well. Big or small. 

As a CP or Alpha Reader, the last thing you want is for the author to change something that moves you or crystallizes a character conflict or plot challenge, etc. Alas, sometimes, to fix the larger issue that Really Awesome Scene has to go. Thus, it's important to say why that moment works for you. If you can articulate what moved you, then the author can either salvage or make a point of hitting that same note in a different way or at a different point. It's not uncommon for one of my comments to be "love this section and these (specific) lines that show them laying bare their heart but it kills pacing; could work better if moved to ChX after the blahblah conflict."

Line edits and copy edits carry less sting, but still need to be balanced by positive comments. Is there a line that made you literally LOL? Add that LOL as a comment. A scene move you to tears? Tell 'em! Dating a new book boyfriend now? Yessss. Say so! Those smexy times get you hot and bothered too? There's no shame in tagging it as hot, hot, hot. Catch an Easter Egg? Teehee. Give 'em props. 

It's too easy to think that as reviewers we only provide value by pointing out what's wrong, when, in truth, highlighting the really good stuff is just as important. 

To my early CPs, I apologize--profusely--for being an asshole. 

Feedback: When is it DNGAF vs Useful

How do I know who to trust with my work, at which stages, and how much weight do I give their input?

~rubs neck~

This is sort of a work-backward topic for me. First question is: do I have a legal obligation to someone? E.g, a publishing contract. If yes, then they get to have input in concept, completed draft, and final edits. There's a legal document that says who gets to have a say, in what, and what the consequence are for ignoring them. Easy answers there.

If I don't have a contract, but I have an agent, I am likely to seek their input on "what's next." Eg. I'm tossing around three concepts, which is the one they feel most able to sell?  To me, an agent is there to help me plan my career short and long term as well as sell my manuscript(s) to publishers. Some people have agents who also provide editorial feedback in addition to career planning and mss sales. If edits are part of the established relationship, then value your agent's opinion or get a different agent.

If I have neither a contract nor an agent and all decisions are mine, then I default to my gut. I'm not a sharer of concepts or incomplete works. I'm the Critique Partner who will hand over a completed draft before I solicit feedback. In reverse, I'm the Critique Partner who is most effective when I have your completed draft. My editorial strengths are in the development of plot and character. If I don't know where your character is headed, I can't really tell you if an explosive action response is the best next step. I have had potential CPs who worked best exchanging chapters so they were receiving near-constant feedback. I wasn't the right fit for them. I didn't like them any less as people, we simply weren't compatible as CPs.

Beyond the CP stage, I trust the professional editors I've paid. I've had one crappy dev editor, and the rest have been amazing. I've learned that I need to tell my editors if I have specific questions or perceived story issues, so they know--that in addition to whatever they find--they need to also acknowledge whether my issues are legit or "just me."

That's my process. While I don't like brainstorming my concepts with other people, I love brainstorming other people's ideas. Yes, it's a double standard.

Dear Readers, if you're questing for sources of feedback, the first question you must ask yourself is "what do I want from the people with whom I'm sharing my ideas/work?" Be honest; otherwise, you're in for a boatload of butthurt on both sides. Some authors need adulation, encouragement, and positive feedback only. They're not emotionally prepared for someone to respond with constructive criticism. Similarly, the "constructive" part of criticism is a skill that requires practice. Tact and tone are hard to convey in "track changes." If you're open to critique, great, but everyone has different thresholds and tolerances for how much and how phrased. Communication is key to fine-tuning any relationship. It's okay to say, "Hey, this [specific example] is a little harsh for me. Next time, it'd be easier for me to hear the feedback couched like [specific example]."

So, the short bitchy answer to this week's question is: I trust people who've proven their value. Everything else is DNGAF.