Picture if you will, the valar and maiar gathered around discussing creation.
Reviewee: I have invented a new kind of animal! It lives in the water, has gills to breathe, and flippers that enable it to move. I call it a “fish.”
Critiquer: Yeah, that’s good, but… what if this “fish” lived in trees and had wings to fly with?
Reviewee: Well, the point was to make a thing that lived in the water…
Other Critiquer: Man, I really like this “lives in trees and has wings” idea! You should give your fish brightly-colored feathers and have them sing.
In the FurTheMore writing track, writing groups and critiques — and specifically, how to give good critiques — were a major focus. Having only recently gotten into the world of actually being in a writing group, this discussion was fresh in my mind as I watched and winced at a person in a recent group meeting having their perfectly good kid’s book being twisted into all kinds of weird pretzel shapes. Instead of critiquing the story that she had brought, the discussion kept turning to all sorts of different things the story could have been (or to some of the critiquers’ way of thinking, should have been).
The thing reached a head when one of the critiquers suggested that the entire story could be told in pictures, with none of the reviewee’s words at all, to which the reviewee replied, “So what’s the point of my even doing it?”
Please don’t do this to people.
Giving useful feedback can be difficult, and the thing about writers particularly is that we’re a creative lot. When we see an idea that sparks thoughts and possibilities, we want to spin new stories out of them. It’s as natural as breathing! But in the context of writing critique, it’s as useful as putting a fish in a tree and telling it to fly.
Unless the reviewee is specifically looking to brainstorm new ideas (which can also be a great exercise), your job as a critiquer is to address the text at hand: what works, what doesn’t, and specifically if the writer succeeds at making the text do what it’s supposed to do. “Maybe your fish should have its eyes on the side of its head to more easily spot predators” is useful feedback. “Your fish should be a bird” is not, and worse, it can be actively harmful. I don’t think anyone at the meeting intended to tell the reviewee that she had wasted her time and effort creating a useless story, but that was clearly the message she was receiving.
Giving Good Critique in Three Easy Steps
So, what should you do? Try this…
“Get” the Story
Look for what the writer was trying to accomplish, as well as fairly universal things like “Do the sentences make sense?” and “Are the characters engaging?”
Talk About What Worked, What Didn’t Work, and What Was Great, In That Order
Using the famous “shit sandwich” model (the bad stuff surrounded by good things on either side), give feedback that’s as specific as possible. Remember that the point is to discuss the story that’s actually on the page, not the amazing story you came up with in your own head.
Here’s where you can toss in your own ideas, but keep in mind that the changes should be to address what didn’t work first and foremost. If the reviewee’s fish has given you a great idea for a bird, go ahead and mention it as a possibility for expansion or a new direction if you like. Or maybe go create your own bird. You’re a writer, after all! And the best part is that by doing that, you empower the reviewee to make an even better story, instead of tearing them down and making them wonder what the point of having written it was.