<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Comments on Success Stories</title>
    <link>http://www.boxesandarrows.com/view/success-stories</link>
    <pubDate>Fri, 05 Oct 2007 19:20:05 GMT</pubDate>
    <description>How do we learn from designers who have blazed the trail before us? Clifton Evans dives into Bill Moggridge's &lt;i&gt;Designing Interactions&lt;/i&gt; to find out what treasures lie in the stories collected by one of Ideo's founders.</description>
    <item>
      <description>&lt;p&gt;Thanks for this book review. It made me want to go and buy the book as a resource. However, I&#8217;m waiting for the companion volume: &#8220;Failed Projects.&#8221; I&#8217;d write it, but I don&#8217;t have any relevant experience&amp;#8230;&lt;/p&gt;

	&lt;p&gt;Back in the dotcom heyday in the agency world there was a real spirit of openness that I had not experienced in my previous corporate work environments. The &#8220;post mortems&#8221; were brilliantly illuminating, because they were full of information you could really use. Unlike information that will be useful the next time I invent the Ipod&amp;#8230; It&#8217;s what I loved about Guy Kiyosaki&#8217;s book &#8220;Before You Quit Your Job&#8221; (which my wife was unpleasantly surprised to see me reading 4 years after starting my consulting practice). It&#8217;s the failures that make it interesting. I&#8217;m not talking about failures like &#8220;I was too lazy to research new ways to solve this problem&#8221; or &#8220;It was the client&#8217;s fault.&#8221; But reality-show scenarios about ambitious attempts that have resulted in failure, like, &#8220;The project had 6 IA&#8217;s and 10 graphic designers, and the comps were lapping the wireframes, so we ended up having to do rework that cost us 2 weeks we didn&#8217;t have.&#8221; Or, &#8220;We did user testing to improve usability of the prototype, but we should have done in-store ethnography, because the sales associates have a handwritten notebook that nobody told us about that easily trumped the online system, and we ended up with less than 20% user adoption the first 90 days after launch.&#8221; Or &#8220;We decided to implement &lt;span class="caps"&gt;SAP&lt;/span&gt;, Omniture, and Documentum at the same time. We never knew what hit us.&#8221; Stories of pain that teach a lesson, so they don&amp;#8217;t have to be repeated.&lt;/p&gt;

	&lt;p&gt;Of course there are liability issues and very few books have the candor of a closed meeting. Maybe something like a UX version of PostSecret (&lt;a href="http://postsecret.blogspot.com/" rel="nofollow"&gt;http://postsecret.blogspot.com/&lt;/a&gt;) would do the trick. Imagine the postcard secret: &#8220;I was the client partner on a big e-commerce project. I ignored the timelines the track leads gave me. I just filled in the number the client gave me and worked backwards from there.&#8221;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/success-stories#content_12834</link>
      <guid>http://www.boxesandarrows.com/view/success-stories#content_12834</guid>
      <pubDate>Fri, 05 Oct 2007 19:20:05 GMT</pubDate>
      <author>Paul Bryan</author>
    </item>
    <item>
      <description>&lt;p&gt;Thank you for such a review that goes beyond the book&amp;#8217;s content to put the topic in context. I hope to see more reviews like this that strive to become educational vehicles themselves and not just product reports.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/success-stories#content_11931</link>
      <guid>http://www.boxesandarrows.com/view/success-stories#content_11931</guid>
      <pubDate>Sun, 02 Sep 2007 21:13:16 GMT</pubDate>
      <author>Victor Lombardi</author>
    </item>
    <item>
      <description>&lt;p&gt;I&amp;#8217;m glad to see another critical review of Designing Interactions. You&amp;#8217;ve hit on many of the points I made in &lt;a href="http://www.heyotwell.com/heyblog/archives/2006/11/review_designin_1.html" rel="nofollow"&gt;my review of it last November.&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;But frankly, I think you&amp;#8217;re being much too nice. Huge sections of this book are garbage&amp;#8212;the section on Google is just recapitulating the Larry/Sergey PR myths. Much of it is very sloppily edited, and the interview format is a huge crutch to pad out the text. The best that can be said about the book is that it&amp;#8217;s large, and has lots of great pictures.&lt;/p&gt;

	&lt;p&gt;I think Moggridge&amp;#8217;s failure to be crystal clear about his relationship to &lt;span class="caps"&gt;IDEO&lt;/span&gt; and to the many people interviewed in the book is deeply unethical. He doesn&amp;#8217;t mention he *founded &lt;span class="caps"&gt;IDEO&lt;/span&gt;* anywhere in the text, for pete&amp;#8217;s sake! Come on. I&amp;#8217;m ashamed of &lt;span class="caps"&gt;MIT&lt;/span&gt; Press for allowing that to pass.&lt;/p&gt;

	&lt;p&gt;That he works so hard to make everything here seem like the outcome of &amp;#8220;natural&amp;#8221; iterative processes is so biased, so much part of Silicon Valley culture of the 1970&amp;#8217;s-1990&amp;#8217;s that I&amp;#8217;m sure he doesn&amp;#8217;t even notice it. It&amp;#8217;s naked mythologizing, not historical research.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/success-stories#content_11835</link>
      <guid>http://www.boxesandarrows.com/view/success-stories#content_11835</guid>
      <pubDate>Sun, 02 Sep 2007 01:51:01 GMT</pubDate>
      <author>Andrew Otwell</author>
    </item>
  </channel>
</rss>
