<?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 Paul Sherman</title>
    <link>http://www.boxesandarrows.com/person/2892</link>
    <pubDate>Thu, 15 Feb 2007 21:25:38 GMT</pubDate>
    <description>Comments by Paul Sherman</description>
    <item>
      <description>&lt;p&gt;Very enjoyable article! I really like your description of the product manager&amp;#8217;s role and responsibilities. I just posted an article at UXMatters that touched on some of the same points, in particular the conflict between product management and user experience. I don&amp;#8217;t want to shill so I won&amp;#8217;t post a link. But here&amp;#8217;s title of the UXMatters article: Connecting Cultures, Changing Organizations: The User Experience Practitioner As Change Agent.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/transitioning-from#content_4866</link>
      <guid>http://www.boxesandarrows.com/view/transitioning-from#content_4866</guid>
      <pubDate>Thu, 15 Feb 2007 21:25:38 GMT</pubDate>
      <author>Paul Sherman</author>
    </item>
    <item>
      <description>&lt;p&gt;Thanks for a good read James. A couple of comments: You said of user needs research:&lt;/p&gt;

	&lt;p&gt;&amp;#8220;Rather than support the design process, this research helps the IA understand the nature of the problem.&amp;#8221;&lt;/p&gt;

	&lt;p&gt;Maybe I&amp;#8217;m picking at semantic nits, but it seems to me that because a &amp;#8220;design&amp;#8221; in our world is a functional description of a problem-solving tool, there is very little &amp;#8211; maybe no &amp;#8211; difference between understanding the nature of the problem and the early stage design process.&lt;/p&gt;

	&lt;p&gt;My last comment is on your &amp;#8220;strategy and scope&amp;#8221; section: for anyone interested in a structured approach to negotiating strategy and scope, &lt;span class="caps"&gt;I HIGHLY&lt;/span&gt; recommend Adam Polansky&amp;#8217;s chapter in &amp;#8220;Usability Success Stories.&amp;#8221; Full disclosure: I edited the book. But I&amp;#8217;m propping Adam, not me.&lt;/p&gt;

	&lt;p&gt;I find I just keep returning to Adam&amp;#8217;s case study for bite-sized nuggets of smartness.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/enterprise-ia#content_6376</link>
      <guid>http://www.boxesandarrows.com/view/enterprise-ia#content_6376</guid>
      <pubDate>Thu, 05 Jul 2007 16:06:00 GMT</pubDate>
      <author>Paul Sherman</author>
    </item>
    <item>
      <description>&lt;p&gt;Good artcle. I&amp;#8217;ve been taking the same perspective myself, and I&amp;#8217;ve also called for UX professionals to see themselves as change agents. (Reference: &lt;a href="http://uxmatters.com/MT/archives/000162.php" rel="nofollow"&gt;http://uxmatters.com/MT/archives/000162.php&lt;/a&gt;)&lt;/p&gt;

	&lt;p&gt;I think your points about organizational resistance are spot-on. My particular take on this is that organizational culture drives most, if not all, organizational inertia.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/the-information#content_12937</link>
      <guid>http://www.boxesandarrows.com/view/the-information#content_12937</guid>
      <pubDate>Fri, 12 Oct 2007 01:20:44 GMT</pubDate>
      <author>Paul Sherman</author>
    </item>
  </channel>
</rss>
