Review Writing Questions

[DaveMage]

Well, so far I get way more negative feedback when I mention other books in a review to a great extent. In fact, the few times I've done it I never got a postive response to it. And I'm not going to cater reviews to the few people who have a few thousand RPG books like myself since the vast majority of people do not.

But you (and many reviewers) are in a unique position to be more "well-read" than the rest of us. I think you should use that knowledge to recommend the products you found more usable than the one you're reviewing, or tell us why the one you're reviewing is going to see use in your campaign.

Because, basically, with all that you've experienced, if you're using a product it must *really* have stood out for you.

I'm not saying you should base your scoring on this criteria, nor should you focus on this aspect for the whole review. Just take a sentence or two to mention it.

If you're running a campaign that's totally unrelated to the book your reviewing, then you can say something like "if I were to run the type of campaign this product covers, I would definitely include this in my game" or "while I'm not running this type of campaign now, this product made me want to do so immediately". Or to really give a product a thumbs up, you could say that "even though I'm not running this type of game, I'm going to find a way to use this in my game anyway - it's that good."

With some products I've read, there are those that really inspired me to use parts of them in a campaign immediately. There have also been products that when I've read them I know that I'd absolultely never include them in my game.

 

[Crothian]

But you (and many reviewers) are in a unique position to be more "well-read" than the rest of us. I think you should use that knowledge to recommend the products you found more usable than the one you're reviewing, or tell us why the one you're reviewing is going to see use in your campaign.[.quote]

I do, just not in reviews. I do this on the boards, some times in my blog, and in other places. When I review a book, the focus is on that book. I don't want to steal the spotlight with another book.

Because, basically, with all that you've experienced, if you're using a product it must *really* have stood out for you.

Not really. It just means it was useful to me. I'm using the expanded Psionics handbook, not becasue I think it is a great book but becasue it does the job a player needed it to do. Personally, I'm not a fan at all of the book, but it was what we have. Other books I love, but I can't use. Not becasue of lack of trying but I know that ultimately it won't improve my game. Many settings fall in this category.

I'm not saying you should base your scoring on this criteria, nor should you focus on this aspect for the whole review. Just take a sentence or two to mention it.

Sometimes I do mention other books., I don't always think to do that though. It depends on the books, the review, and what else is going on.

 

[DaveMage]

Other books I love, but I can't use. Not becasue of lack of trying but I know that ultimately it won't improve my game. Many settings fall in this category.

Then is it really a good gaming book, or just a good read? (From your perspective of course.) This is what I want to know.


For me, the #1 d20 product ever made is the Battlebox from Fiery Dragon. Why? Not because it's has the best production values (it doesn't, though they are pretty decent), but because I use it almost every round during every combat. It's USEFUL to me.

That's what really helps me judge if a product is worth recommending. How useful will it be in your actual game?

 

[Ghostwind]

Let me step into this and say that comparing a book being reviewed to another product is usually a bad idea. For starters, you are trying to review each book on its own merits and not against another's. Secondly, when comparisons are made, it is a lot easier for the person reading the review to develop misconceptions about the product being reviewed based entirely on the context in which you are using to make the comparison. In other words, he may feel that book X is inferior to book Y because you (the reviewer) have stated that you like Z mechanic better. This can lead to getting your proverbial head thwacked off by fans who think you gave the book an unfair grade or comment.

As far as writing a review itself, here is the text of a document I give to everyone on my review staff to help guide them in review writing.

Writing a Critical Review for Gaming Products
By Steve Creech

This analysis is based upon an article written by Ian Colford for Dalhousie University. The original may be viewed at http://www.library.dal.ca/how/bookrev.htm. Certain parts of this article are taken verbatim from Colford’s original. While this review is intended to serve as a guide for reviewing gaming products, it is general enough to help with reviewing non-gaming products, such as novels.

In order to properly write a review, it is necessary for the reviewer to have not only read the product, but make an attempt to understand not only the purpose of the book, but the intent of the author(s) and how the components of that work contribute to that purpose. The reviewer also needs to have an understanding of the game mechanics required along with a strong familiarity of gaming in general that includes its history in order to form a foundation or standard to base his review upon.

The Minimum Requirements of a Review
1. Description over summation. There should be a sufficient enough description so the reader gains an understanding of the author’s intent and purpose and not just a listing of the book’s contents. This may be interwoven into the critical comments of the book.

2. Brief information (but not a biography) about the author that is both relevant to the work and will enhance the reader’s understanding of the product being reviewed. This includes a short summation of the author’s previous works.

3. An appraisal, or judgment, of the book and its value to gaming. A critical review does represent the opinion of the reviewer but it may also be considered a judgment if it:
· Includes a statement of the reviewer’s understanding of the author’s purpose.
· Summarizes how well the reviewer feels the author’s intent and purpose has been achieved.
· Provides evidence to support the reviewer’s assessment of the product.

Preliminary Mechanical Steps
1. Read the book thoroughly and with care.
2. Make notes that includes appropriate passages for quoting.
3. Allow time to assimilate and process what you have read so the book may be seen in perspective.
4. Keep in mind the need for achieving a single impression, which must be made clear to the reader.

Points to Keep in Mind
· Objectivity: Regardless of whether you've purchased the item or been provided with a free copy, try to always look at it in an objective and non-biased manner. It's easy to look more favorably on a book by a publisher whose work you have really enjoyed in the past, but try to avoid falling into the trap of "It has to be good if it's by ___." Your review should never sound like a press release. If it does, then you have not done your job properly.
· Details: Be certain that your review is giving adequate details about the book. Talk about the content but don't necessarily list off the table of contents. Hit the more important matters with detail and gloss over less important ones. A good review doesn’t necessarily discuss the contents of the book point by point, paragraph by paragraph unless it serves a specific purpose.
· Praise: If there is something you really liked, by all means point it out and tell why. But try to keep the lavish praise to a reasonable level lest your review begin to sound like a press release. Too much praise and your objectivity may come into question.
· Criticisms:
· Do not be afraid to openly address problem areas with a book, but be sure to support it with an example whenever possible. For example, if the CRs of the monsters in a supplement are way off base, cite a specific monster and then show what the proper CR should be.
· If there is something you don't like about a product, say so. But always say why you didn't like it. For example, Bad Axe's Dwarf book was one that I didn't particularly care for because it fed directly into the dwarven stereotype and gave nothing to suggest a dwarf should be played otherwise. In my opinion, this was a fault behind the book.
· Understand that your words will be criticized by others (especially on Internet-based communities). Do not take offense. Criticism serves a usual purpose when applied properly. Any responses should be concise and to the point while being polite and professional at all times.
· Do not worry about offending publishers. They want honest opinions about their products. They will naturally disagree with a bad review but if there are things that are wrong, the publisher needs to know so they can fix or address it in future products. Be truthful but also be tactful. Don't say "it sucks" and leave it at that...

The Review Outline
A review outline allows you to have a good grasp of the overall organization of the review, determine the central point of your review, remove irrelevant comments or unnecessary observations, and fill in any omissions or gaps.

Examine your notes, eliminate those having no relationship to your central thesis, and organize them into groups, and several aspects of the book will emerge: e.g., theme, character, structure, etc. After ordering your topics--determining in what sequence they will be discussed--write down all the major headings of the outline and then fill in the subdivisions. Keep in mind that all parts of the outline should support your central point.

The Draft
The opening paragraph, like the concluding one, sets the tone of the review. The introduction should not only identify the product, but also make a statement about the author’s purpose, the significance of the work, and possibly a brief comparison against other works by the same author or similar products within the same genre.

The main body of the review should be a logical progression based upon your central point as organized by your outline. Changes in the outline may need to be made and transitional paragraphs introduced, but the aim should be toward logical development of the central point. All quoted material should be put in quotation marks, or indented, and properly footnoted.

The concluding paragraph may sum up or restate your point or may make the final judgment regarding the book. No new information or ideas should be introduced in the conclusion other than explanation of the scores the product received. For example, if a book received a mediocre score on Originality because it reinforces tired stereotypes, it should be noted in this section.

Steps in Revision of the Draft
1. Allow at least 24 hours to pass before starting your revision to give yourself a chance to re-read it with fresh eyes.
2. Correct all grammar, punctuation and spelling errors as you find them.
3. Read your paper through again looking for unity, organization and logical development.
4. If necessary, make revisions in your draft regardless of the size and scope.
5. Verify quotations for accuracy and check the format and content of references.
6. Make sure the review is in the proper format including HTML tags.

Factors to Consider When Reviewing (where applicable):

Theme
· What is the major theme?
· Is the theme traditional and familiar or new and original?
· Does the book have a particular focus group or intended audience that is reflected in the theme?

Plot
· How are the various elements of the plot (introduction, suspense, climax, conclusion) handled?
· What are the elements of mystery and suspense?
· Are there factors that complicate the plot?
· Is there a sub-plot and does it tie into the main plot?
· Is the plot primary or secondary to other essential elements of the story (character, setting style, etc.)?

Style
· What are the various qualities of the writing (intellectual, emotional, aesthetic)?
· Is the style consistent throughout the book or does it change frequently making reading difficult?

Setting
· What is the setting and does it play a significant role in the product?
· Is a sense of atmosphere evoked and in what manner?
· What scenic effects are used? Are they important and effective?
· Does the setting interfere with the plot?

Game Mechanics
· Do the mechanics conform to the established ruleset of the gaming system?
· Are the mechanics presented in an appropriate style that is reader friendly?
· Are the mechanics balanced properly and do they avoid the hazards associated with those balance issues?

Presentation and Layout
· Are maps, illustrations, etc. used and are they relevant to the work?
· Is the selection of fonts adequate and conducive to reading or does the reader have to struggle to make out the individual letters and words?
· Are there a significant number of editorial errors and oversights that distract from reading the book?
· Does the product utilize a significant amount of previously published material or build upon the work of others? Is this properly cited?
· Is the cost of the product fairly proportional to the value it represents to the consumer? Would it be a product that the consumer utilizes on a consistent basis or one that has limited application and potential?

When you've finished writing your review take a moment to re-read it and see if it accurately assesses the book or if it sounds like a glossed over press release filled with few details and lots of praise with no specifics. If you have the opportunity, have someone else read it over and see if it would cause them to form an opinion or at least generate interest about the book. If it does that, then you've done your job properly and responsibly.

 

[Crothian]

Then is it really a good gaming book, or just a good read? (From your perspective of course.) This is what I want to know.

Game of Thrones d20, I'm working on this review right now. It is a good read and it is a good game for those that want to play Game of Throwns. But in my Tellus game, the current campaign I'm running, it is of little use. But I might be able to steal some of the idfeas since it is well written. Rules wise, not so much since I'm in the middle of a campaign and its not a good idea, IMO, to introduce new rules mid stream even if I think thety are better.

For me, the #1 d20 product ever made is the Battlebox from Fiery Dragon. Why? Not because it's has the best production values (it doesn't, though they are pretty decent), but because I use it almost every round during every combat. It's USEFUL to me.

Great product for those that like this stuff. I gave mine away. He never uses it, even though we do use minis and sich. Personally, the cards of rules I found to be the best. The spell templates I perfer the steelqwire stuff to or just drawing it out. It is always easier for me to just do that. But I can see why other people like and use it. Heck, if I had my way I wouldn't be using minis.

That's what really helps me judge if a product is worth recommending. How useful will it be in your actual game?

And as we see in the above exampole, it also helps if the reviewer has similar tastes to you. I perfer no minis, heavy role playing, players thinking, heavy plot, no true good or bad guys type games. But I also have to run the game my players will play, so a lot of that gets curbed. DMing is a complicated things and books are no less simple.

 

[Crothian]

As far as writing a review itself, here is the text of a document I give to everyone on my review staff to help guide them in review writing.

Thanks Steve, I've been looking for this!!

 

[Varianor Abroad]

Steve's got excellent advice there. I recommend when writing a review that you find something positive to say about the book by the end of the review. (When I used to just review products I bought, I wouldn't review stinkers. Now that I'm helping The Review Project I know that someday I'll get handed a dead fish.) Other than that, his guidelines are great. Objectivity and examples are much better to me as a purchaser than "I liked this" with no reason why. Thanks Steve for the sneak peek!

 

[Yair]

I'll just add that I've found it helps if you read the material twice: once, then write the review, then read again and change the review as needed. This, of course, is only viable for small stuff.
For larger stuff, I like writing notes as I go along, then organizing and expanding them into a reivew, and then going back and double checking my points and adding quotes if needed.

Not that I have anywhere near the experience of some folks here, but this works for me.

 

[Shadowslayer]

Just a couple of thoughts:

Bear in mind too the average gamer. What may seem cliche to you may not be for me. We don't all eat, sleep and breathe RPGs, so try and limit the "this is more of the same old same old...nothing really new here" kind of statements. You're probably right. But just remember that generic doesnt necessarily mean useless. In other words, don't write it off just because its pseudo-Tolkein-ish. Lots of folks like that stuff, and many of us haven't played the game SO much that we've become bored with its usual trappings.

My only real pet peeve is reviews that go obsessively into stuff like text density, size of margins, fonts used etc. (even art quality. I'm sure some folks buy stuff for the art, but I think most would say its really just decoration) It has no real bearing on game play.

My 2 cents

 

[Vigilance]

But you (and many reviewers) are in a unique position to be more "well-read" than the rest of us. I think you should use that knowledge to recommend the products you found more usable than the one you're reviewing, or tell us why the one you're reviewing is going to see use in your campaign.

I dunno, as a writer, when I read a review of one of my books, Id like the review to be *about* that book.

A review is a chance for a book to be judged on its own merits, not a billboard to funnel the reader to one product that has a similar goal.

As an example, I wrote a book called Legends of Excalibur that was released about the same time as the Sword and Sorcery Relics and Rituals: Excalibur. From what you're saying every reviewer should decide which was better, and then when he wrote a review of either one point the reader to the one he thought was better.

I dont really think that's necessary. Assuming both books get reviews, then people can READ both reviews and make up their minds from there which suits their needs, or even perhaps buy both.

Chuck