When I read brief descriptions of books, I must admit my first reaction is often, “So what?” So what if young Miranda and her cat must save the world from the ultimate evil? So what if Devon Hope has stumbled on a secret that will mean the end of the world if he can’t find a missing artifact before someone kills him. Meh.
The problem here might be failure to engage. For me, and maybe for other readers, it takes more than the bare bones of a dire situation to pique interest, especially when that situation is just another variation on a well-worn theme. Saving the world while escaping death — what’s more dire than that? Except generic peril is as bland as no peril at all.
But it might be something else.
Observing myself while reading book descriptions, I think the reason for “blurb failure” is not always the fault of the person (author or publisher) who wrote it. The real problem is what used to be called an “embarrassment of riches.” There’s a deluge of information coming at us all the time. Posts, tweets, ads, promos, news, views, warnings, tips, tricks, sounds, images, etc., etc. Aaaaargh, I can’t take any more!
When the brain is overloaded and distracted, not even the most artfully created blurb will do the trick. The eye skips, the brain misses, and the conclusion (barely registered by the person who experiences it) is “Sure, okay, seen it before. So what? Next!”
In this environment, it takes more than a well-written blurb to bring a potential reader to “Yes, I’m going to buy this book.” Maybe it’s repetition; if someone sees a cover image and description twenty times or a hundred times, eventually the tipping point is achieved. Maybe if it arrives via a personal recommendation from a trusted friend. Or maybe it’s a totally random conjunction of temperature, air pressure, hormones, and the angle of the light coming through the window.
So what’s an author to do?
Authors sweat blood writing the brief descriptions (“blurbs”) that appear next to their book’s cover image and on the back cover or jacket flap. They have to be short and intriguing. “So what?” is absolutely NOT the reaction a book description should provoke.
And a book description is absolutely necessary, despite the fact that it will be another drop in the flood. When I see book recommendations by bloggers, without even a brief indication of what the book is about, I pass them by.
If nothing else, creating a book description is a good writing exercise. It demands effective word choices constructed into powerful sentences. It’s a distillation of a book’s essence, an enticing whiff that makes the reader want more.
A book description may be field-tested by running different versions past critique partners, blog readers, or even friends and family. Along with the question “Would any of these make you want to read the book?”
Turning the topic over again, when I take the time to read a book description carefully, giving it my full attention, I’m not always inclined to think “So what?” Hmm, how would Miranda’s cat help her save the world? What sort of person is Devon Hope, and what is the crucial artifact he has to find?
Dang! Neither of those books exists; they’re just examples I made up.
How do you read book descriptions? Do you ever get the “So what?” feeling? Do you have any tips for writing an effective blurb?
Featured image by S K from Pixabay.