Monday, 12 November 2012

SIGCHI Rebuttals - Some suggestions to write them

ACM SIGCHI has in it's review process the opportunity for the authors to respond to the comments of the reviewers. I find this a good thing and to me it has two main functions:
  1. The reviewers are usually more careful in what they write as they know they have to face a response for the authors
  2. Authors can clarify points that they did not get across in the first place in the original submission.

We usually write for all submissions with an average score over 2.0 a rebuttal. For lower ranked submissions it may be OK if we think we have a chance to counter some of the arguments, which we believe are wrong or unfair.

For the rebuttal it is most critical to address the meta-review as good as possible. The primary will be in the PC meeting and if the rebuttal wins this person over the job is well done. The other reviews should be addressed, too.

For all the papers where we write a rebuttal I suggest the following steps(a table may be helpful):
  1. read all reviews in detail
  2. copy out all statements that have questions, criticism, suggestions for improvement from each review
  3. for each of these statement make a short version (bullet points, short sentence) in your own words
  4. sort the all the extracted statements by topic
  5. combine all statements that address the same issue
  6. order the combined statements according to priority (highest priority to primary reviewer)
  7. for each combined statement decide if the criticism is justified, misunderstood, or unjustified
  8. make a response for each combined statement
  9. create a rebuttal that addresses as many points as possible, without being short (trade-off in the number of issue to address and detail one can give)
Point 8 is the core...
There are three basic options:
  • if justified: acknowledge that this is an issue and propose how to fix it
  • if misunderstood: explain again and propose you will improve the explanaition in the final version
  • if unjustified: explain that this point may be disputed and provide additional evidence why you think it should be as it is
The unjustified ones are the most tricky ones. We had cases where reviewers stated that the method we used is not appropriate. Here a response could be to cite other work that used this method in the same context. Similarly we had reviewers arguing that the statistical tests we used cannot be used on our data, here we also explained in more details the distribution of the data and why the test is appropriate. Sometimes it may be better to ignore cases where the criticism is unjustified - especially if it is not from the primary.

Some additional points
  • be respectful to the reviewers – they put work in to review the papers
  • if the reviewers did not understand – we probably did not communicate well
  • do not promise unrealistic things in the rebuttal
  • try to answer direct questions with precise and direct answers
  • if you expect that one reviewer did not read the paper – do not directly write this – try to address the points (and perhaps add a hint it is in the paper, e.g. “ANSWER as we outline already in section X)

1 comment:

Anonymous said...

Good post.
http://albrecht-schmidt.blogspot.com/2012/11/sigchi-rebuttals-some-suggestions-to.html
albrecht-schmidt.blogspot.com
crawl=CC-MAIN-2018-39
68182
application/http; msgtype=response
sha1:EC6X76IXJZGDOYYCMMPZ5D24SK2LWMTD
<urn:uuid:111bf99c-41b5-4451-abc0-3db78624b47d>
2018-09-25T12:58:12Z
172.217.7.225
application/xhtml+xml
sha1:3FXH2I7TZREUJGSDC6UDY737NRIH6HWH
<urn:uuid:87b36bab-e0e2-4158-9996-c839e342b788>
http://albrecht-schmidt.blogspot.com/2012/11/sigchi-rebuttals-some-suggestions-to.html
response
<urn:uuid:d0500446-b76d-4440-83f6-b32d8f5f6565>
isPartOf: CC-MAIN-2018-39
publisher: Common Crawl
description: Wide crawl of the web for September 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-123-248-186.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/