RSS
 

How NOT to Write a Book Review

17 Nov

14450840 Man writerI read a lot, on average three books a week (based on my Goodreads Reading Challenge numbers). I live the maxim that writers must be readers. Because I love writing, I review many of them for one of my three blogs. When Amazon asked me to be a Vine Voice, I was flattered and wanted to understand why my reviews caught their eye. I spent time reading a wide selection of reviews and came away with a framework of what all critics included:

  • a brief plot summary
  • an overview of characters
  • a discussion on the theme/plot/goal and whether it’s well-delivered
  • the reviewer’s evidence-based opinion
  • an appealing voice

Reviews I didn’t like often covered these critical areas, but got lost in the ‘personal history’ weeds.  Unless the reviewer is Michiko Kakutani or James Wood (both listed among the top ten most feared literary critics), I’m ambivalent to a reviewers’ personal opinions.

As a result, I’ve developed a template for what to avoid in my reviews. See if you agree:

Opinionated

Book reviews aren’t opinions; they’re factually-based summaries. Sure, many books include the author’s opinion. A reviewer’s job is not to disagree with the opinion, rather discuss how the author rolls it out. Do they provide evidence? Is their argument well-developed or gratuitous? Do readers find themselves nodding in agreement or fuming in anger? They should feel the reviewer is even-handed, neutral, and an arbiter of the discussion rather than a participant.

Narrow perspective

The author writes from their personal experience. True, the reviewer’s personal fable is as unique–and likely different–as the author’s, but that isn’t what’s being reviewed. Show how motivation/theme/goals connect to a vast swath of readers even as the character/plot/setting are fresh and unique.

writers‘This isn’t my favorite genre’

Not only do I avoid that phrase, I hate hearing it as an excuse why the critic has her/his opinion. In fact, it tells me to ignore everything they’re about to say. If this isn’t the reviewer’s genre, research it. For example, literary fiction delves into characters; thrillers focus on plot. I wouldn’t down-star Ted Bell’s Patriot for the lack of Lord Hawkes’ personal thoughts.

If the reviewer isn’t willing to understand the book’s genre, stick with traditional traits like a compelling voice, developed characters, and well-paced plot.

Takes too long to get to the point

Reviewers should be pithy and laser-focused. Sometimes, they’re neither. Often, that happens because the reviewer isn’t sure of what they’re saying and hopes to throw enough words on the page to hit the bullseye for most people. Long reviews should be stuffed full of meaty information, not fat.

Conclusions without evidence

I love hearing a conclusion I may not agree with because it means I’m about to learn something. I feel cheated when that conclusion lacks evidence. Unless the reviewer is part of my inner circle (people who I tend to accept at face value), please cite sources–multiple sources–and give me linkbacks so I can verify statements.

Superiority

Reviewers aren’t there to judge writers, rather evaluate. A debut novel is  different than the tenth in the series, and a young thriller writer should not be compared to Lee Child. Critics offer advice to inform the reader’s decision on whether they should read more of this author. That’s a weighty responsibility. Approach it with respect and humility.

For more on this topic, check out Adam Kirsch’s article (he’s considered one of the top ten reviewers by some). To see the review of what might be the most famous review ever (on John Keats), click here.

More on critiques:

7 Reasons For and Three Against Critique Groups

25 Take-aways from the Richard Bausch workshop

10 Tips from Toxic Feedback

Writers Tip #52: Join a Writers Groups

BTW: There is the fantastic guide on How to Write a Book on AcademicHelp.net. Read it now!


Jacqui Murray is the author of the popular Building a Midshipman, the story of her daughter’s journey from high school to United States Naval Academy. She is the author/editor of over a hundred books on integrating tech into education, adjunct professor of technology in education, webmaster for four blogs, an Amazon Vine Voice book reviewer,  a columnist for TeachHUB, Editorial Review Board member for Journal for Computing Teachers, monthly contributor to Today’s Author and a freelance journalist on tech ed topics. You can find her book at her publisher’s website, Structured Learning.


Jacqui Murray is the author of the popular Building a Midshipman, the story of her daughter’s journey from high school to United States Naval Academy, and the thriller, To Hunt a Sub. She is also the author/editor of over a hundred books on integrating tech into education, adjunct professor of technology in education, webmaster for four blogs, an Amazon Vine Voice book reviewer, a columnist for TeachHUB, monthly contributor to Today’s Author and a freelance journalist on tech ed topics. You can find her books at her publisher’s website, Structured Learning. The sequel to To Hunt a Sub, Twenty-four Days, will be out this summer. Jacqui Murray has been teaching K-8 technology for 15 years. She is the editor/author of over a hundred tech ed resources including a K-8 technology curriculum, K-8 keyboard curriculum, K-8 Digital Citizenship curriculum. She is an adjunct professor in tech ed, CSG Master Teacher, webmaster for four blogs, an Amazon Vine Voice book reviewer, Editorial Review Board member for Journal for Computing Teachers, CAEP reviewer, CSTA presentation reviewer, freelance journalist on tech ed topics, and a weekly contributor to TeachHUB. You can find her resources at Structured Learning.


 
 

Leave a Reply

 

 
 
%d bloggers like this: