Dear Reviewers, a Word?

9 December 2011, 1556 EST

Everyone gets rejected. And it never stops being painful not matter how successful or how long you have been in the business. Some of this is inevitable; not everyone is above average. But some of it isn’t. I thought that I would offer some ‘dos’ and ‘don’ts’ for reviewers out there to improve the process and save some hurt feelings, when possible. Some are drawn from personal experience; others, more vicariously. I have done some of the “don’ts” myself, but I feel bad about it. Learn from my mistakes.
First, and I can’t stress this enough, READ THE F*CKING PAPER. It is considered impolite by authors to reject a paper by falsely accusing it of doing THE EXACT OPPOSITE of what it does. Granted, some people have less of a way with words than others and are not exactly clear in their argumentation. But if you are illiterate, you owe it to the author to tell the editors when they solicit your review. It is okay – there are very successful remedial programs they can recommend. Don’t be ashamed.

Second, and related to the first, remember the stakes for the author. Let us consider this hypothetical scenario. In a safe estimate, an article in a really top journal will probably merit a 2-3% raise for the author. Say that is somewhere around $2000. Given that salaries (except in the University of California System) tend to either stay the same or increase, for an author who has, say, 20 years left in his/her career, getting that article accepted is worth about $40,000 dollars. And that is conservative. So you owe it more than a quick scan while you are on the can. It might not be good, but make sure. Do your job or don’t accept the assignment in the first place. (Sorry, I don’t usually like scatological humor but I think this is literally the case sometimes.)
Third, the author gets to choose what he/she writes about. Not you. He/she is a big boy/girl. Do not reject papers because they should have been on a different topic, in your estimation. Find fault with the the paper actually under review to justify your rejection.
Fourth, don’t be a b*tch. Articles should be rejected based on faulty theory or fatally flawed empirics not a collection of little cuts. Bitchy grounds include but are not limited to – not citing you, using methods you do not understand but do not bother to learn, lack of generalizability when theory and empirics are otherwise sound. The bitchiness of reviews should be inversely related to the audacity and originality of the manuscript. People trying to do big, new things should be given more leeway to make their case than those reinventing the wheel.
Fifth, don’t be an a**hole. Keep your sarcasm to yourself. Someone worked very hard on this paper, even if he/she might not be very bright. Writing “What a surprise!”, facetiously, is a dick move. Rejections are painful enough. You don’t have to pour salt on the wound. Show some respect.
Sixth, remember that to say anything remotely interesting in 12,000 words is ALMOST IMPOSSIBLE. Therefore the reviewer needs to be sympathetic that the author might be able to fix certain problems where he/she given more space to do so. Not including a counterargument from your 1986 JOP article might not be a fatal oversight; it might have just been an economic decision. If you have other things that you would need to see to accept an otherwise interesting paper, the proper decision is an R&R, not a reject. Save these complaints for your reviews of full-length book manuscripts where they are more justifiable.
Seventh, you are not a film critic. Rejections must be accompanied by something with more intellectual merit than “the paper did not grab me” or “I do not consider this to be of sufficient importance to merit publication in a journal of this quality.” This must be JUSTIFIED. You should explain your judgment, even if it is something to the effect of, “Micronesia is an extremely small place and its military reforms are not of much consequence to the fate of world politics.” Even if it is that obvious, and it never is, you owe an explanation.