<?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 Jason Sack</title>
    <link>http://www.boxesandarrows.com/person/4384</link>
    <pubDate>Sun, 30 Nov 2008 15:01:09 GMT</pubDate>
    <description>Comments by Jason Sack</description>
    <item>
      <description>&lt;p&gt;I would suggest studying cognitive psychology and cultural anthropology before learning about the tactical side of the UX discipline.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/topics/view/30706#content_31211</link>
      <guid>http://www.boxesandarrows.com/topics/view/30706#content_31211</guid>
      <pubDate>Sun, 30 Nov 2008 15:01:09 GMT</pubDate>
      <author>Jason Sack</author>
    </item>
    <item>
      <description>&lt;p&gt;Sounds like a good idea &amp;#8211; can we start an ongoing thread of podcast links with mini-reviews that is persistent?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/topics/view/30212#content_31212</link>
      <guid>http://www.boxesandarrows.com/topics/view/30212#content_31212</guid>
      <pubDate>Sun, 30 Nov 2008 15:03:22 GMT</pubDate>
      <author>Jason Sack</author>
    </item>
    <item>
      <description>&lt;p&gt;Clearly another great way to look at user-centered design. Eliminating anything that compromises a users ability to complete their task or gather their information is a great strategy. In designing user experiences, I have found that the challenge lies in the details &amp;#8211; specifically related to the fact that we are many times designing for multiple audiences with diverse needs and characteristics. In this regard, I often separate this effort into two layers. One is a basic cognitive psychological layer (and even this layer becomes challenged when considering users with disabilities), and the other is the socio-cultural layer. UX design gets interesting in situations where these layers collide, even assuming one has the time, budget, and expertise to uncover the necessary insights about the audiences.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/design-for-emotion#content_31213</link>
      <guid>http://www.boxesandarrows.com/view/design-for-emotion#content_31213</guid>
      <pubDate>Sun, 30 Nov 2008 15:19:58 GMT</pubDate>
      <author>Jason Sack</author>
    </item>
    <item>
      <description>&lt;p&gt;Oh &amp;#8211; sort of like the one that already exists here :) Look forward to digging in to it.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/topics/view/30212#content_31214</link>
      <guid>http://www.boxesandarrows.com/topics/view/30212#content_31214</guid>
      <pubDate>Sun, 30 Nov 2008 16:33:10 GMT</pubDate>
      <author>Jason Sack</author>
    </item>
    <item>
      <description>&lt;p&gt;I have another take. Adhering to research and process are one way to approach design. Not the only way. The thought that UX-driven means focusing on &amp;#8220;what the customer wants&amp;#8221; is a rather narrow way to look at UX design. Many times the customer can&amp;#8217;t articulate what they want. Additionally,  innovation often takes place through the creative process or intuition. And when we talk about analytics data, data can help identify the right questions to ask, but it can&amp;#8217;t shed any insight into that which is unobservable &amp;#8211; that which is occurring in the emotional parts of the brain. And neither qualitative or quantitative methods can tell you anything about that which does not yet exist. To me, UX is as much about letting the creative process unfold as it is about research and process.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/integrating-ux-into#content_113295</link>
      <guid>http://www.boxesandarrows.com/view/integrating-ux-into#content_113295</guid>
      <pubDate>Wed, 08 Feb 2012 23:04:21 GMT</pubDate>
      <author>Jason Sack</author>
    </item>
    <item>
      <description>&lt;p&gt;Hey Jon,&lt;/p&gt;

	&lt;p&gt;In todays&amp;#8217; hyper-speed marketplace, in the time it takes to even put together and execute a research plan &amp;#8211; not to mention implement and enforce any design &amp;#8220;process,&amp;#8221; a good designer could have concepted, designed, and built an execution that could then be tested and responded to. I feel that research driving insights is invaluable, but I have yet to see any UX process that results in deliverables that aren&amp;#8217;t, at best, out-of-date by the time it comes to execute, or, at worst, completely flawed.&lt;/p&gt;

	&lt;p&gt;In my experience, a really good small team &amp;#8211; say a designer, researcher, developer, and writer/content strategist &amp;#8211; can get from point A to point B so quickly that they can then iterate to point C and launch before the &amp;#8220;process&amp;#8221; has even started. I believe that this is one of the reasons that both Facebook and Google have been successful. I&amp;#8217;ve seen personas that spend months in development. If the team is good, they only need a few key points about the audience. Same for business goals.&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;m not into self-flagellation. I&amp;#8217;m into doing good work fast, and I have yet to see any process that isn&amp;#8217;t counter-productive to that approach. Just my perspective.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/integrating-ux-into#content_113377</link>
      <guid>http://www.boxesandarrows.com/view/integrating-ux-into#content_113377</guid>
      <pubDate>Sat, 11 Feb 2012 18:31:58 GMT</pubDate>
      <author>Jason Sack</author>
    </item>
  </channel>
</rss>

