<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Richard August</title>
    <link>http://www.boxesandarrows.com/person/9529</link>
    <pubDate>Sun, 15 Jul 2007 12:23:26 GMT</pubDate>
    <description>Comments by Richard August</description>
    <item>
      <description>&lt;p&gt;Good ideas are coming from your article, Adam. On IT companies I work, where the User Experience approach wasn&amp;#8217;t so welcome, or maybe, was completely unknow, this analysis will help us to increase the importance of our UX team, with a more balanced analysis within all perspectives, removing the chance of doubtful decisions or even plain &amp;#8216;end-user-discrimination&amp;#8217;. Excitement ahead!&lt;/p&gt;

	&lt;p&gt;I don&amp;#8217;t think that giving rates from 1-5 eliminates all subjective or political choices. Maybe it&amp;#8217;s more clear giving importance for product releases and deliverables: &amp;#8220;(-1) not important, (0) neutral, (1) important&amp;#8221;. This give you a list of items rated by importance: the features to build on product version 01, product version 02, and so on, keeping your product development on track. Also, if needed, each team may justify the item importance given based on another document or spec pre-aproved.&lt;/p&gt;

	&lt;p&gt;Do you have a particular experience with that? What do you think?&lt;/p&gt;

	&lt;p&gt;Thanks.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/faceted-feature#content_9964</link>
      <guid>http://www.boxesandarrows.com/view/faceted-feature#content_9964</guid>
      <pubDate>Sun, 15 Jul 2007 12:23:26 GMT</pubDate>
      <author>Richard August</author>
    </item>
  </channel>
</rss>
