<?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 mazy burns</title>
    <link>http://www.boxesandarrows.com/person/9199</link>
    <pubDate>Fri, 29 Jun 2007 18:27:00 GMT</pubDate>
    <description>Comments by mazy burns</description>
    <item>
      <description>&lt;p&gt;Great article, again very timely &#8211; this is exactly the position I&#8217;ve been in for the last few months.&lt;/p&gt;

	&lt;p&gt;&#8220;Because you measured the user experience of your original product against the new product your team just built, you can prove how much better the new product is for your users.&#8221;&lt;/p&gt;

	&lt;p&gt;Quick question: How can you &#8216;document wins&#8217; for a new product on which you&#8217;ve been implementing &lt;span class="caps"&gt;UCD&lt;/span&gt; from the start? This is the 1st time the company I&#8217;m consulting for has used this process, when it&#8217;s launched (to great success, I hope!) how can I prove / demonstrate how much of it&#8217;s success is due to taking a user-centred approach, rather than it simply being a great proposition that would&#8217;ve succeeded anyhow?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/pioneering-a-user#content_9501</link>
      <guid>http://www.boxesandarrows.com/view/pioneering-a-user#content_9501</guid>
      <pubDate>Fri, 29 Jun 2007 18:27:00 GMT</pubDate>
      <author>mazy burns</author>
    </item>
  </channel>
</rss>
