<?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 Kenny Allen</title>
    <link>http://www.boxesandarrows.com/person/9360</link>
    <pubDate>Tue, 10 Jul 2007 16:09:14 GMT</pubDate>
    <description>Comments by Kenny Allen</description>
    <item>
      <description>&lt;p&gt;I agree with the benefits of internal usability studies and would like to see it fleshed out into a full article. In my organization, we have an internal group of people from various business units who fit the personas built around our external constituents. They match the demographic data we have on file as well as interests, passion models, etc., and have proved to be a great resource for quick focus group and usability testing.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/9474#content_9737</link>
      <guid>http://www.boxesandarrows.com/idea/view/9474#content_9737</guid>
      <pubDate>Tue, 10 Jul 2007 16:09:14 GMT</pubDate>
      <author>Kenny Allen</author>
    </item>
    <item>
      <description>&lt;p&gt;I think this article would not only be informative for the B&amp;amp;A community but also for key product stakeholders, too. I find in an enterprise setting that this first phase of any project, the definition and documentation of the project which includes, &lt;span class="caps"&gt;IMO&lt;/span&gt;, this persona building step, is often the most difficult to sell to the C-level.  Instead, most companies think they know their constituents better than anyone so why waste time and money on this part of project, just pull out the same old tired demo information and get started on the app.  I&amp;#8217;d like to read this article.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/idea/view/5604#content_9739</link>
      <guid>http://www.boxesandarrows.com/idea/view/5604#content_9739</guid>
      <pubDate>Fri, 07 Jan 2011 19:41:16 GMT</pubDate>
      <author>Kenny Allen</author>
    </item>
  </channel>
</rss>

