<?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 Brian Cassidy</title>
    <link>http://www.boxesandarrows.com/person/9759</link>
    <pubDate>Thu, 09 Aug 2007 15:13:16 GMT</pubDate>
    <description>Comments by Brian Cassidy</description>
    <item>
      <description>&lt;p&gt;I wouldn&#8217;t say that the fold is necessarily a &#8220;myth&#8221;. It is a real barrier albeit one that has been paved over to more of a speed bump because users have become accustomed over the years to using one of the more simple inherent functions of a browser, the scroll bar. Also, we, as in the UI designers, have no one to blame but ourselves for reinforcing the fold. If we have been responsible designers we are probably doing wireframes to scale (or close to scale) and our Visio templates are set to letter or legal in landscape orientation so that we can (and out clients can) print out our deliverables on regular paper. Our designs then tend to conform to this. We need to break away from this constraint.&lt;/p&gt;

	&lt;p&gt;As you suggest, keeping functionality away from the fold and to use visual cues to suggest that there is something worthwhile to scroll to, is the key. Again, as responsible designers, we can and should influence all of the folks that depend upon our deliverables &amp;#8211; the business owners, visual designers and developers &amp;#8211; to remember that the fold is real but not to be afraid of it.&lt;/p&gt;

	&lt;p&gt;Now, how about the right hand fold? Meaning, scrolling from left to right. Now that is a reality. Is that the next barrier to true freedom?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/blasting-the-myth-of#content_10547</link>
      <guid>http://www.boxesandarrows.com/view/blasting-the-myth-of#content_10547</guid>
      <pubDate>Thu, 09 Aug 2007 15:13:16 GMT</pubDate>
      <author>Brian Cassidy</author>
    </item>
    <item>
      <description>&lt;p&gt;Great breakdown of different approaches of obtaining valuable feedback from users. One thing I might add, which you elude to is the quickness of the turnaround of this feedback back to the various stakeholders, as well as gaining agreement of what to do with the feedback. The first point is key to demonstrating the effectiveness of injecting user feedback back into the design process loop but the feedback needs to be reported quickly enough to be considered, especially in an agile methodology. The second point of &amp;#8220;gaining agreement&amp;#8221; is important to getting that commitment to the prototyping process. There&amp;#8217;s nothing worse than building a prototype, recruiting users, conducting the test, creating a report, etc&amp;#8230; only to hear, &amp;#8220;well, we&amp;#8217;ll have to take care of those problems in phase 2,&amp;#8221; when we all know that phase 2 never happens.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/integrating#content_41474</link>
      <guid>http://www.boxesandarrows.com/view/integrating#content_41474</guid>
      <pubDate>Wed, 23 Sep 2009 22:39:04 GMT</pubDate>
      <author>Brian Cassidy</author>
    </item>
  </channel>
</rss>

