<?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 Eric Swenson</title>
    <link>http://www.boxesandarrows.com/person/14725</link>
    <pubDate>Tue, 08 Apr 2008 13:58:24 GMT</pubDate>
    <description>Comments by Eric Swenson</description>
    <item>
      <description>&lt;p&gt;Great article, thanks. I&amp;#8217;m going to share with some past colleagues and a client &amp;#8211; with context. As a consultant who is often called upon to perform project rescues, I feel that I should point out that I have, indeed, spent considerable time (and watched clients spend a lot of money) fixing projects that have resulted only from surrogate data. These instances have resulted from logic that is similar to the primary driver logic referred to herein (typically, executives who refused to honestly answer the question of what &lt;span class="caps"&gt;NOT&lt;/span&gt; doing proper UX integration would cost in the long run). I have been in the business long enough to be able to empathize and sympathize with the rationale cited for resorting to the Extreme method. I&amp;#8217;m &lt;span class="caps"&gt;NOT&lt;/span&gt; saying its destined for failure. But I want to add my voice to the cautionary ones on this thread.&lt;/p&gt;

	&lt;p&gt;My personal recommendation might be disputed by a statistician, but I would argue for forced dilution across multiple axes vs. taking a purely &amp;#8220;Extreme&amp;#8221; route. In other words, if you can only interview 15 users and 45 surrogates, the 15 end-user samples could result in exponentially more unique insight than otherwise. Also, there is a third axis I&amp;#8217;d like to add here: 1) &amp;#8220;Real&amp;#8221; end user; 2) Surrogate (as cited); 3) (NEW!) Victim Surrogate.  What&amp;#8217;s a Victim Surrogate? A third-string actor affected by the poorly designed system but who is more obscured in the workflow.&lt;/p&gt;

	&lt;p&gt;This invites a deeper conversation than a comment board has room for, but it points to the need for examining the site from the perspective of  public-facing front end; back end (admin interfaces frequented by say, call center personnel); and downstream tangential actors (anyone ranging from high level executives who only care about analytics to warehouse personnel who process printed or electronic order slips; this is always case-specific).&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;m all for radical solutions to radical/extreme problems and think this Extreme approach is well-developed. But for those of us who are teachers, consultants, etc. let&amp;#8217;s make sure our clients/bosses/students don&amp;#8217;t take this lesson home karaoke style for a quick fix out of laziness vs. Extreme need/externally driven desperation. Thanks.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/extreme-user#content_18225</link>
      <guid>http://www.boxesandarrows.com/view/extreme-user#content_18225</guid>
      <pubDate>Tue, 08 Apr 2008 13:58:24 GMT</pubDate>
      <author>Eric Swenson</author>
    </item>
  </channel>
</rss>

