Product reviews: a practical guide

The version of this that works is simpler than the version most people imagine. This guide covers what product reviews actually involves, where it usually goes wrong, and how to tell whether yours is in reasonable shape.

Small percentage changes matter here because they apply to every order, every month. Nothing below assumes a large team or a large budget — most of it is a decision somebody has to make and then write down.

What it costs to ignore

Reviews answer the questions your copy avoids. The teams that handle this well are rarely the ones with the biggest budgets. It rarely shows up as a line item, which is exactly why it slips.

For most businesses the question is not whether this matters but how much of it is worth doing right now. That depends on what you are trying to achieve in the next few months, not on best practice in the abstract. The teams that handle this well are rarely the ones with the biggest budgets.

The practical version

A few critical reviews make the positive ones believable. Where this goes wrong is almost never a lack of knowledge. It rarely shows up as a line item, which is exactly why it slips.

Trust does most of the selling online, and trust is built from unglamorous details. The version that works in practice is usually less elaborate than the version described in the guides.

Reply to bad reviews in public, calmly. In practice this is a scheduling problem more than a technical one. Assume whoever inherits this will have half your context and none of your patience.

A working checklist

If you want a quick read on where you stand, work through this. Anything you cannot answer confidently is where to start.

• Reviews answer the questions your copy avoids
• A few critical reviews make the positive ones believable
• Reply to bad reviews in public, calmly
• Someone is named as the owner, not just assumed to be
• There is a date in the calendar to review it again
• The decision and the reasoning behind it are written down somewhere findable
• You could explain the current setup to a new hire in five minutes

Where it usually goes wrong

The most common failure is not doing this badly. It is doing it once, during a launch, and never revisiting it. Circumstances move, the setup does not, and the gap widens quietly until something breaks or somebody notices the numbers.

• It was configured during a launch and has not been touched since
• Different people in the business believe different things are true about it
• There is no way to tell whether the last change helped or hurt
• The only person who understands it has left, or is about to

In e-commerce every friction point has a price attached, and the arithmetic is unusually easy to check. The reasoning matters more than the rule, because the rule has exceptions.

How we approach it

On our projects this gets handled during the build rather than added afterwards, because retrofitting it costs several times more than including it. We write down what was decided and why, so the next person to touch it is not guessing.

If you are working with someone else, the questions worth asking are simple: who owns this, how will we know it is working, and what happens when it needs to change?

What to do next

Pick the single item from the checklist above that would cause the most trouble if it turned out to be wrong. Fix that one, confirm it worked, then move on. The point is not perfection, it is knowing which of these you have consciously chosen to skip.