<?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 Anita Salem</title>
    <link>http://www.boxesandarrows.com/person/5043</link>
    <pubDate>Mon, 30 Apr 2007 03:21:44 GMT</pubDate>
    <description>Comments by Anita Salem</description>
    <item>
      <description>&lt;p&gt;James, thanks for bringing up the more strategic aspects of the work we do.  I do think that many IA/usability/UCD people can be overly focused on the tactical &amp;#8220;problem solving&amp;#8221; aspect of our work.  Good architects should always be looking for underlying business and user needs to provide value.  Like Ray said, though, we are really not doing structurally anything different than has been traditionally done in product development.  What I think we do very differently is apply design practices (prototyping, iterations for example)to business problems.  We also uncover issues through a bottom up approach (interviewing, field studies, etc.).  The iterative, empirical, user centered processes we use are what differentiate us from the other traditional processes.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/enterprise-ia#content_7041</link>
      <guid>http://www.boxesandarrows.com/view/enterprise-ia#content_7041</guid>
      <pubDate>Mon, 30 Apr 2007 03:21:44 GMT</pubDate>
      <author>Anita Salem</author>
    </item>
  </channel>
</rss>
