<?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: Learning In Progress #10: Writing Effective Criticisms</title>
	<atom:link href="http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/</link>
	<description>Jon Jones is an Art Outsourcing Manager in the video game industry.</description>
	<lastBuildDate>Wed, 01 Feb 2012 07:02:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dwight Hayles</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-340272</link>
		<dc:creator>Dwight Hayles</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-340272</guid>
		<description>A large part of my job is critique, qa and reviews. Working on 3d assets I find the best way to portray what I am trying to say is through images. Nothing says &quot;this area needs fixed&quot; better than a still image or render of the asset with either an arrow pointing to the area or a number next to the area.
The number corresponds to the numbered correction that explains the fix needed in detail. 
Sometimes it is hard to explain a correction when a 3d asset is comprised of 200+ mesh components and some of those components are very complex.
I also find it very helpful to have another artist critique the asset before I get a chance to look at it. I ask the QA artist to critique 
the asset as if he were in my position. This really cuts down on those minor corrections that take a long time to explain when there are a lot of them.
Lastly I think it has the added side effect of bringing the team closer together.
I see artists working together fixing problems on assets before I even get a chance to see it. That is very cool to me.</description>
		<content:encoded><![CDATA[<p>A large part of my job is critique, qa and reviews. Working on 3d assets I find the best way to portray what I am trying to say is through images. Nothing says &#8220;this area needs fixed&#8221; better than a still image or render of the asset with either an arrow pointing to the area or a number next to the area.<br />
The number corresponds to the numbered correction that explains the fix needed in detail.<br />
Sometimes it is hard to explain a correction when a 3d asset is comprised of 200+ mesh components and some of those components are very complex.<br />
I also find it very helpful to have another artist critique the asset before I get a chance to look at it. I ask the QA artist to critique<br />
the asset as if he were in my position. This really cuts down on those minor corrections that take a long time to explain when there are a lot of them.<br />
Lastly I think it has the added side effect of bringing the team closer together.<br />
I see artists working together fixing problems on assets before I even get a chance to see it. That is very cool to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Jones</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-249465</link>
		<dc:creator>Jon Jones</dc:creator>
		<pubDate>Sun, 08 Feb 2009 02:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-249465</guid>
		<description>Josh, that&#039;s awesome that it works in person too. I don&#039;t have the benefit of working with my artists in the same building, so that&#039;s really cool that similar principles work in different circumstances.

You also bring up a terrific point about annual reviews... I hadn&#039;t even thought of using feedback structured this way for helping put those together. :) Win!

Thanks for the comment!</description>
		<content:encoded><![CDATA[<p>Josh, that&#8217;s awesome that it works in person too. I don&#8217;t have the benefit of working with my artists in the same building, so that&#8217;s really cool that similar principles work in different circumstances.</p>
<p>You also bring up a terrific point about annual reviews&#8230; I hadn&#8217;t even thought of using feedback structured this way for helping put those together. :) Win!</p>
<p>Thanks for the comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Jones</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-249456</link>
		<dc:creator>Josh Jones</dc:creator>
		<pubDate>Sun, 08 Feb 2009 02:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-249456</guid>
		<description>I&#039;ve been doing something fairly similar for my own team. Even though I can simply verbally provide feedback and bounce tasks around with &quot;make changes as discussed&quot; I find it is much more effective to be anal and provide bulleted comments. It&#039;s a reminder to both me and my colleague. And it is too easy to have a change request slip through the cracks if you don&#039;t have it written down in detail. Lastly, it&#039;s good to have this written record when doing annual reviews and you need to jog your memory about how the workflow of certain animation tasks went over the course of a milestone that you can barely remember.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been doing something fairly similar for my own team. Even though I can simply verbally provide feedback and bounce tasks around with &#8220;make changes as discussed&#8221; I find it is much more effective to be anal and provide bulleted comments. It&#8217;s a reminder to both me and my colleague. And it is too easy to have a change request slip through the cracks if you don&#8217;t have it written down in detail. Lastly, it&#8217;s good to have this written record when doing annual reviews and you need to jog your memory about how the workflow of certain animation tasks went over the course of a milestone that you can barely remember.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Rickard</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-28450</link>
		<dc:creator>Dan Rickard</dc:creator>
		<pubDate>Tue, 14 Aug 2007 12:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-28450</guid>
		<description>Ha ha.. this is too funny... I&#039;ll make sure to watch for this when we get our feedback from you... by the way... where is our feedback?? (notice I used two question marks?) :)</description>
		<content:encoded><![CDATA[<p>Ha ha.. this is too funny&#8230; I&#8217;ll make sure to watch for this when we get our feedback from you&#8230; by the way&#8230; where is our feedback?? (notice I used two question marks?) :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Jones</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-28069</link>
		<dc:creator>Jon Jones</dc:creator>
		<pubDate>Wed, 25 Jul 2007 16:04:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-28069</guid>
		<description>Yeah, I often break out the compliments into a separate paragraph that generalizes everything, or I&#039;ll call out one particular asset as being my favorite in that batch. :)

Something else I do -- particularly for studios -- is write up all my critiques in a text file and put it in a dated drop folder on the FTP in addition to email. That way it helps them store the changes outside of email and it&#039;s in a dated directory they can refer back to. It&#039;s the same way I keep track of it.</description>
		<content:encoded><![CDATA[<p>Yeah, I often break out the compliments into a separate paragraph that generalizes everything, or I&#8217;ll call out one particular asset as being my favorite in that batch. :)</p>
<p>Something else I do &#8212; particularly for studios &#8212; is write up all my critiques in a text file and put it in a dated drop folder on the FTP in addition to email. That way it helps them store the changes outside of email and it&#8217;s in a dated directory they can refer back to. It&#8217;s the same way I keep track of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stahr</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-27863</link>
		<dc:creator>Stahr</dc:creator>
		<pubDate>Sat, 14 Jul 2007 00:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-27863</guid>
		<description>I&#039;ve been following your blog for some time now, and I&#039;ll just be posting a fast comment before bed.
I think it&#039;s good to let the praise to be somewhat constructive, like telling them in what way it is great, like: This really suits the general feeling/idea, especially this(perhaps pointing out what you think made the thing work), please continue with thoose ideas, etc. 
Then you got both praise and the fact that the artist know what he did good, it would have got more meaning than just a general praise. Perhaps you emphasized this enough in your post, pointing at the sense of weight.
but it&#039;s great to keep it short and listed, this makes it so much easier to me as an artist.
and also, getting everything in one mail and not in a dozen ;) that is good also, I mean the artist also do his/her oganizing on the replies he/she gets and have some kind of system for it.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been following your blog for some time now, and I&#8217;ll just be posting a fast comment before bed.<br />
I think it&#8217;s good to let the praise to be somewhat constructive, like telling them in what way it is great, like: This really suits the general feeling/idea, especially this(perhaps pointing out what you think made the thing work), please continue with thoose ideas, etc.<br />
Then you got both praise and the fact that the artist know what he did good, it would have got more meaning than just a general praise. Perhaps you emphasized this enough in your post, pointing at the sense of weight.<br />
but it&#8217;s great to keep it short and listed, this makes it so much easier to me as an artist.<br />
and also, getting everything in one mail and not in a dozen ;) that is good also, I mean the artist also do his/her oganizing on the replies he/she gets and have some kind of system for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Jones</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-27861</link>
		<dc:creator>Jon Jones</dc:creator>
		<pubDate>Fri, 13 Jul 2007 20:17:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-27861</guid>
		<description>Thanks dude! I&#039;d be really interested in hearing how it works out for you.

One additional bonus I forgot to mention is that keeping it in very simple sentences and clearly organized like that helps for the studios I use that don&#039;t speak English as a first language.</description>
		<content:encoded><![CDATA[<p>Thanks dude! I&#8217;d be really interested in hearing how it works out for you.</p>
<p>One additional bonus I forgot to mention is that keeping it in very simple sentences and clearly organized like that helps for the studios I use that don&#8217;t speak English as a first language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: adam crockett</title>
		<link>http://www.jonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/comment-page-1/#comment-27860</link>
		<dc:creator>adam crockett</dc:creator>
		<pubDate>Fri, 13 Jul 2007 20:12:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.thejonjones.com/2007/07/12/learning-in-progress-fuck-knows-what-writing-concise-criticisms/#comment-27860</guid>
		<description>nice suggestions. I&#039;ll probably empliment this technique into critiques of my outsource studio&#039;s animation. I generally use an excel sheet, but this may come in much handier for the contractor to reference.</description>
		<content:encoded><![CDATA[<p>nice suggestions. I&#8217;ll probably empliment this technique into critiques of my outsource studio&#8217;s animation. I generally use an excel sheet, but this may come in much handier for the contractor to reference.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

