<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Tips for dealing with CHI rebuttals</title>
	<atom:link href="http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/feed/" rel="self" type="application/rss+xml" />
	<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/</link>
	<description>musings and other goodies</description>
	<lastBuildDate>Fri, 23 Mar 2012 13:47:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Alan Winfield</title>
		<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/comment-page-1/#comment-2762</link>
		<dc:creator>Alan Winfield</dc:creator>
		<pubDate>Sat, 13 Nov 2010 12:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://brynnevans.com/blog/?p=1592#comment-2762</guid>
		<description>Great piece thank you Brynn. It&#039;s fascinating that there is a kind of emergent (and mostly unwritten) etiquette for responding to reviewers comments, and it&#039;s different for journal paper, conference paper and (especially) grant applications.

I blogged about a rejected paper recently, see
http://alanwinfield.blogspot.com/2010/09/darn-conference-paper-soundly-rejected.html</description>
		<content:encoded><![CDATA[<p>Great piece thank you Brynn. It&#8217;s fascinating that there is a kind of emergent (and mostly unwritten) etiquette for responding to reviewers comments, and it&#8217;s different for journal paper, conference paper and (especially) grant applications.</p>
<p>I blogged about a rejected paper recently, see<br />
<a href="http://alanwinfield.blogspot.com/2010/09/darn-conference-paper-soundly-rejected.html" rel="nofollow">http://alanwinfield.blogspot.com/2010/09/darn-conference-paper-soundly-rejected.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry Lieberman</title>
		<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/comment-page-1/#comment-2730</link>
		<dc:creator>Henry Lieberman</dc:creator>
		<pubDate>Wed, 21 Jul 2010 18:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://brynnevans.com/blog/?p=1592#comment-2730</guid>
		<description>Many authors respond to negative reviews by trying to shoot down the criticisms, one by one. 

Remember, the Program Committee are the ones who decide on acceptance, not the reviewers, who merely act as advisors to the PC. The PC doesn&#039;t need to assure that every criticism is met, it needs to understand *the argument for why the paper should be accepted*. I can&#039;t emphasize this enough. 

Many reviews/rebuttals discuss flaws in the paper and whether/how they should be repaired, but lack a good argument for accepting (or rejecting, as the case may be) the paper. 

So, in a rebuttal, help the PC out by giving them the argument for accepting the paper. If the reviewers made the argument, then point it out. If the reviewers missed the point of the paper, spell out the argument for accepting the paper yourself. Examples: This paper introduces a genuinely new and important idea. It solves a problem that nobody else can solve. It gives people a new way to think about an old problem, etc. 

If there are flaws in the paper criticized by the reviewers, by all means repair or rebut them as necessary. If the criticisms are well taken, cop to it. But say why the repaired paper deserves acceptance, or argue that the remaining flaws are inessential to the main point.</description>
		<content:encoded><![CDATA[<p>Many authors respond to negative reviews by trying to shoot down the criticisms, one by one. </p>
<p>Remember, the Program Committee are the ones who decide on acceptance, not the reviewers, who merely act as advisors to the PC. The PC doesn&#8217;t need to assure that every criticism is met, it needs to understand *the argument for why the paper should be accepted*. I can&#8217;t emphasize this enough. </p>
<p>Many reviews/rebuttals discuss flaws in the paper and whether/how they should be repaired, but lack a good argument for accepting (or rejecting, as the case may be) the paper. </p>
<p>So, in a rebuttal, help the PC out by giving them the argument for accepting the paper. If the reviewers made the argument, then point it out. If the reviewers missed the point of the paper, spell out the argument for accepting the paper yourself. Examples: This paper introduces a genuinely new and important idea. It solves a problem that nobody else can solve. It gives people a new way to think about an old problem, etc. </p>
<p>If there are flaws in the paper criticized by the reviewers, by all means repair or rebut them as necessary. If the criticisms are well taken, cop to it. But say why the repaired paper deserves acceptance, or argue that the remaining flaws are inessential to the main point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brynn</title>
		<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/comment-page-1/#comment-2069</link>
		<dc:creator>brynn</dc:creator>
		<pubDate>Tue, 17 Nov 2009 21:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://brynnevans.com/blog/?p=1592#comment-2069</guid>
		<description>And here&#039;s the link to my comic: http://www.scribd.com/doc/22660693/Parallel-Lives</description>
		<content:encoded><![CDATA[<p>And here&#8217;s the link to my comic: <a href="http://www.scribd.com/doc/22660693/Parallel-Lives" rel="nofollow">http://www.scribd.com/doc/22660693/Parallel-Lives</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brynn Marie Evans &#187; &#8220;Parallel Lives&#8221;: A comic about academic publishing</title>
		<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/comment-page-1/#comment-2066</link>
		<dc:creator>Brynn Marie Evans &#187; &#8220;Parallel Lives&#8221;: A comic about academic publishing</dc:creator>
		<pubDate>Tue, 17 Nov 2009 17:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://brynnevans.com/blog/?p=1592#comment-2066</guid>
		<description>[...] In light of the CHI 2010 paper reviews that were due last week, I created a comic strip about the academic research, review, and publishing process. I previously noted that this was one of my tips for &#8220;dealing with the rebuttal process!&#8221; [...]</description>
		<content:encoded><![CDATA[<div style="">
<p>[...] In light of the CHI 2010 paper reviews that were due last week, I created a comic strip about the academic research, review, and publishing process. I previously noted that this was one of my tips for &#8220;dealing with the rebuttal process!&#8221; [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: brynn</title>
		<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/comment-page-1/#comment-2063</link>
		<dc:creator>brynn</dc:creator>
		<pubDate>Fri, 13 Nov 2009 18:19:52 +0000</pubDate>
		<guid isPermaLink="false">http://brynnevans.com/blog/?p=1592#comment-2063</guid>
		<description>Very good additional points, Gene. Thanks!</description>
		<content:encoded><![CDATA[<p>Very good additional points, Gene. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/comment-page-1/#comment-2059</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Thu, 12 Nov 2009 22:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://brynnevans.com/blog/?p=1592#comment-2059</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by brynn: A few tips for dealing with the CHI rebuttal process: http://bit.ly/3VcoPb...</description>
		<content:encoded><![CDATA[<div style="">
<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by brynn: A few tips for dealing with the CHI rebuttal process: <a href="http://bit.ly/3VcoPb" rel="nofollow">http://bit.ly/3VcoPb</a>&#8230;</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gene Golovchinsky</title>
		<link>http://brynnevans.com/blog/2009/11/11/tips-for-dealing-with-chi-rebuttals/comment-page-1/#comment-2058</link>
		<dc:creator>Gene Golovchinsky</dc:creator>
		<pubDate>Thu, 12 Nov 2009 21:24:27 +0000</pubDate>
		<guid isPermaLink="false">http://brynnevans.com/blog/?p=1592#comment-2058</guid>
		<description>Good suggestions all. 

I would also add the following:

Some changes reviewers ask for may well be beyond the scope of the work, and may be contradictory (R1 wants of X, R2 more of Y). You should decide what makes sense given the work you *did*, not the work the reviewer *wanted* you to do.

Being defensive is not going to win reviewers over; being factual may.

Make sure reviewers know what the takeaway from your paper was (particularly if any of them expressed doubts). This is the elevator pitch for your paper, and you should have it nailed. Sometimes reviewers don&#039;t read the paper as carefully as you&#039;d like them to (after all, they may be reading lots of papers, and doing other things as well), so adding a bit of emphasis here may help alert them to what&#039;s important about the work.

Give the meta-reviewer as much evidence as possible that you will make the appropriate changes. If reviewers asked for a particular analysis and you can squeeze it into the rebuttal, do it.</description>
		<content:encoded><![CDATA[<p>Good suggestions all. </p>
<p>I would also add the following:</p>
<p>Some changes reviewers ask for may well be beyond the scope of the work, and may be contradictory (R1 wants of X, R2 more of Y). You should decide what makes sense given the work you *did*, not the work the reviewer *wanted* you to do.</p>
<p>Being defensive is not going to win reviewers over; being factual may.</p>
<p>Make sure reviewers know what the takeaway from your paper was (particularly if any of them expressed doubts). This is the elevator pitch for your paper, and you should have it nailed. Sometimes reviewers don&#8217;t read the paper as carefully as you&#8217;d like them to (after all, they may be reading lots of papers, and doing other things as well), so adding a bit of emphasis here may help alert them to what&#8217;s important about the work.</p>
<p>Give the meta-reviewer as much evidence as possible that you will make the appropriate changes. If reviewers asked for a particular analysis and you can squeeze it into the rebuttal, do it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

