When someone asks us what our book is about, some of us are hamstrung. Having lived with the book for potentially months, we know the ins and outs of the story. Some of us launch into a massively detailed description of the book, the characters, the plots and sub-plots.
That’s not entirely helpful.
You’ve read a lot of book descriptions. I know I have. They either catch you or they don’t. Well, there’s another thing that can sometimes happen: the book description that tells too much. How irritating are those movie trailers that all but show you the entire film? We are all sophisticated viewers (and readers) so I don’t think we need every single beat of a story told in a description.
The reason I’m talking book descriptions is that I’m preparing my next book for publication. It’s called TREASON AT HANFORD: A HARRY TRUMAN MYSTERY. I’ve been re-reading it and making edits and changes most of the summer. I’ve got a cover concept (well, at least five) and I sent it to some of my fellow graphic designers to get their take. One of them came back: what’s the book about?
So I sent the description.
What’s problematic about a book featuring Harry Truman is that most folks know he was president and probably instantly jump to that conclusion when they think of Truman. But my tale takes place the year before he became vice president and then president. So I needed at least a sentence or two to lay the groundwork that I’m referring to Senator Truman and not President Truman.
After a few attempts, here’s what I wrote:
Before he became vice president in 1945, Senator Harry Truman led a congressional committee dedicated to ferreting out corruption during World War II. The investigators of the Truman Committee adhere to a simple credo: help the country win the war and bring our soldiers home.
In the spring of 1944, Truman receives a series of ominous letters from a lawyer out in Hanford, Washington. His client, a common farmer who lost his land when the government confiscated miles of territory for a secret project, has been drafted to keep him quiet about what he’s seen going on around a local warehouse with direct ties to the giant facility in the area.
Fearing the worst, Truman leads the investigation himself, bringing along Carl Hancock, a former policeman. Soon after they start poking around, Truman and Hancock witness a pair of brutally murdered corpses, a town clouded in secrecy, and the warehouse owner who is ready to pull strings and dismiss the pesky senator.
But the man from Independence, Missouri, is tenacious, and in no time, Truman and Hancock not only find themselves embroiled in the top-secret world of the Manhattan Project but also must confront the worst act of treason in American history since Benedict Arnold.
Analysis:To me, paragraph one sets the stage in the reader’s mind that this is Senator Truman I’m writing about. Paragraph two features the incident that gets Truman’s attention and start the investigation. The third paragraph ups the stakes by throwing in corpses and the world of 1944. And the final paragraph—which could almost be a log line itself—tosses the phrases “Benedict Arnold” and “The Manhattan Project” into the mix, letting the reader know the just how high the stakes are.
I think it’s a good description and should tell potential readers whether or not they’d like the book.
Then there’s the elevator pitch. Maybe it’s the log line, the one-sentence version of the book. Kudos for any creative type who can sum up a work in a sentence. It’s crucial, mind you, but it’s a skill that must be learned if you don’t already have it.
Like I just wrote, the last paragraph of the description could serve as the elevator pitch, but I also have a sentence on the cover: Before Harry Truman dropped the bomb, he had to save it.
I debated whether or not to include ‘A Harry Truman Mystery’ or not as a sub-title and will likely opt not to have it and leave in the cover blurb. Not sure. Still tweaking the cover concept.
What’s the cover look like? Well, you’ll just have to watch a little bit longer.
What are your thoughts on book descriptions? How do you structure them?