<?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 dustin chambers</title>
    <link>http://www.boxesandarrows.com/person/33728</link>
    <pubDate>Fri, 13 Nov 2009 22:07:34 GMT</pubDate>
    <description>Comments by dustin chambers</description>
    <item>
      <description>&lt;p&gt;Really great read Cindy, thanks. Really useful tips when a project needs some direction or uniformity. I definately agree that an overall project theme is extremely valuable for web design projects, especially when mulitple stakeholders are involved, however I feel like if you follow a traditional &lt;span class="caps"&gt;UCD&lt;/span&gt; approach, your project will already require a (guiding) &amp;#8216;clear and stated objective&amp;#8217;. Whille I admit that a &amp;#8216;site objective&amp;#8217; isn&amp;#8217;t as warm and fuzzy as a &amp;#8216;ux theme&amp;#8217; I argue they are much the same.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/experience-themes#content_47285</link>
      <guid>http://www.boxesandarrows.com/view/experience-themes#content_47285</guid>
      <pubDate>Fri, 13 Nov 2009 22:07:34 GMT</pubDate>
      <author>dustin chambers</author>
    </item>
  </channel>
</rss>

