<?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 Kel Smith</title>
    <link>http://www.boxesandarrows.com/person/10808</link>
    <pubDate>Sun, 09 Sep 2007 05:26:37 GMT</pubDate>
    <description>Comments by Kel Smith</description>
    <item>
      <description>&lt;p&gt;Terrific article. Many thanks for providing this information.&lt;/p&gt;

	&lt;p&gt;On the topic of security, I would underscore the importance of calling out (where appropriate) a &amp;#8220;review security policy&amp;#8221; link from every page node. Icons and messages are good reminders that security is a priority to my institution. As a user, I also want to be assured that steps taken to prevent fraud are proactive, authentic and substantive.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/getting-a-forms#content_12112</link>
      <guid>http://www.boxesandarrows.com/view/getting-a-forms#content_12112</guid>
      <pubDate>Sun, 09 Sep 2007 05:26:37 GMT</pubDate>
      <author>Kel Smith</author>
    </item>
    <item>
      <description>&lt;p&gt;I&amp;#8217;ve had success using b/w wireframes within the team rather than as an external deliverable. I would agree most with the approaches endorsed here by Joel and Bo. It&amp;#8217;s very important to set the stage for a client, regardless of output. Otherwise, a feedback session can quickly deteriorate into a game of &amp;#8220;you&amp;#8217;ll understand when you see it.&amp;#8221;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/real_wireframes#content_12384</link>
      <guid>http://www.boxesandarrows.com/view/real_wireframes#content_12384</guid>
      <pubDate>Fri, 14 Sep 2007 12:38:52 GMT</pubDate>
      <author>Kel Smith</author>
    </item>
    <item>
      <description>&lt;p&gt;One of the more inspiring pieces I&amp;#8217;ve read on B&amp;#38;A. What a great series of thumbnail lessons in establishing empathy with our users. Thanks for providing this!&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/our-way-the#content_14421</link>
      <guid>http://www.boxesandarrows.com/view/our-way-the#content_14421</guid>
      <pubDate>Tue, 08 Jan 2008 19:22:05 GMT</pubDate>
      <author>Kel Smith</author>
    </item>
    <item>
      <description>&lt;p&gt;Dotted line or (light) gray. Good idea to include a &amp;#8220;key&amp;#8221; or &amp;#8220;index&amp;#8221; panel someplace, so folks understand fully.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/topics/view/18031#content_18459</link>
      <guid>http://www.boxesandarrows.com/topics/view/18031#content_18459</guid>
      <pubDate>Sat, 12 Apr 2008 15:12:52 GMT</pubDate>
      <author>Kel Smith</author>
    </item>
    <item>
      <description>&lt;p&gt;Great question. I see (hopefully) increased study regarding the utilization of Universal Design principles to digital media. The implied ergonomic value of multi-touch lends well to the creation of barrier-free haptic interfaces.&lt;/p&gt;

	&lt;p&gt;I don&amp;#8217;t foresee the end of the keyboard/mouse model; as alternative forms of input become more widespread, however, there will be a need to accommodate those usages.&lt;/p&gt;

	&lt;p&gt;It will also be interesting to see how commercial software evolves to match this shifting value paradigm, particularly in the business sector. What would Microsoft Word look like if you could control it haptically?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/topics/view/16348#content_18468</link>
      <guid>http://www.boxesandarrows.com/topics/view/16348#content_18468</guid>
      <pubDate>Sat, 12 Apr 2008 16:06:54 GMT</pubDate>
      <author>Kel Smith</author>
    </item>
  </channel>
</rss>
