<?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 Tristan Naramore</title>
    <link>http://www.boxesandarrows.com/person/61281</link>
    <pubDate>Fri, 13 Nov 2009 22:07:42 GMT</pubDate>
    <description>Comments by Tristan Naramore</description>
    <item>
      <description>&lt;p&gt;What is it with UX people with film backgrounds? I too studied film (at &lt;span class="caps"&gt;UCSC&lt;/span&gt;) but found my career swept up by the dot.com craze. Follow the money, I guess&amp;#8230;&lt;/p&gt;

	&lt;p&gt;Anyhoo, I thought this article was fantastic and most timely. Yesterday, I had this great &amp;#8220;a-ha!&amp;#8221; moment with my client (a very large bank) when a theme suddenly emerged out of some rather frustrating discussions around a poorly defined product. I kept asking stakeholders, &amp;#8220;So, what is this product actual for and why does it need to exist?&amp;#8221; No clear answer came until a BA working on requirements documentation said to me, &amp;#8220;This is to make your boss&amp;#8217;s boss&amp;#8217;s boss happy.&amp;#8221;&lt;/p&gt;

	&lt;p&gt;Everything fell into place. What had been an ad hoc collection of features suddenly became a clear statement of the product&amp;#8217;s implicit value to its users. I don&amp;#8217;t know yet if I&amp;#8217;ll end up explicitly stating this in a strategy brief, but it&amp;#8217;s mighty tempting.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/experience-themes#content_47274</link>
      <guid>http://www.boxesandarrows.com/view/experience-themes#content_47274</guid>
      <pubDate>Fri, 13 Nov 2009 22:07:42 GMT</pubDate>
      <author>Tristan Naramore</author>
    </item>
  </channel>
</rss>

