Often one feels that one aspect of the product underperformed, while the others were on target, but the reviewers fly off the handle.
Whether a review should be constructive depends on which of these it is.
As a software engineer I can imagine the circumstances around the rushing of the product before the software was finished, and can empathise, but ultimately (pun unintended) nothing will change (and more people will waste their time buying and returning the device) unless the company realises their products are getting worse.
Or, sends a support email and 30 seconds later writes a bad review.
Bad reviews sometimes indicate not a willingness to resolve a problem but wanting to shout and be heard.
I hear this often with restaurant reviews too. Something is wrong with the food but they quietly seethe rather than grabbing their waiter, waiting until the taxis home to write a scathing review. How odd.
So true for many.
One thing I always try to do is go out of my way to make that personal connection. Anonymous hit-and-run reviews are, in my opinion, cowardly. If you're going to scrutinise something publically you should be open to talk to the creator of what you're scrutinizing.
Speaking to these kind of users can be invaluable or it can be an awkward hour of disagreeing.
Either way, putting a human face on it and letting them know where I'm coming from and the impact of their review has yielded good results.
Well, obviously: using one-process-fits-all without appreciating local context is a recipe for disaster, isn't it?
I've been pretty effective in dealing with bad reviews for our app and lots of this method resonates with me.
As I'm systematizing the company a key area is putting in a process and tools for the team to handle bad reviews rather than me. So far however, it seems each situation and personality makes it difficult to pin down an effective process.