How to Write Helpful Reviews

Thursday, January 16th, 2014

Writing Helpful Reviews

Seeing as the purpose of the Table Tennis Database is to give people an understanding of the equipment they might buy, I thought I’d share some personal tips on how to write reviews that will be helpful to all readers. Hopefully this will be a useful guide to increase the quality of the reviews. Okay, let’s go!

Describe characteristics specifically

Instead of using general terms like “good” or “bad”, try describing the specific aspects of performance. “The rubber was highly tacky.” Because general terms don’t give a lot of insight to the reader. What feels “good” to you, may not be the same for others.

Mention your playing style

The dominant style for people using smooth rubbers is a topspin looping style. If you were you using this rubber for a different style like flat hitting, then it’s helpful to mention this fact? Do you play as a defensive chopper? Mentioning how you used a rubber is important, because a reader may be looking to use it for a different playing style.

“Bad fit” is not the same as just “bad.”

Sometimes I see negative reviews where the player’s performance was worsened by this new rubber or blade. However, I think this can be unfair. A player’s performance is heavily affected by the right “fit.” If you’re used to attacking with loop drives which fit your current rubber and blade, and then switch to a new setup (like a blade that is too stiff or too flexible), you need to adjust all your angles to make it work. It takes some time to adjust your strokes to the new equipment.

And in the end, the new setup may not be for you. It doesn’t mean that it’s a bad blade deserving a bad review, it’s just a bad fit for you. You need to figure out which characteristics are a fit for your strokes, and find the right setup for it. Know thyself.

Do you have any more suggestions for writing good reviews?


Facebook Like

Leave a Reply

Learn about the author, .

Share This Page
Facebook Facebook
Twitter Twitter
E-mail this page: